Paolo Escobar (@hubesco) header
Paolo Escobar (@hubesco) profile picture

Software Engineer. Ship stuff.

London, England
Joined January 2017
Photo by Paolo Escobar (@hubesco)Photo by Paolo Escobar (@hubesco)Photo by Paolo Escobar (@hubesco)Photo by Paolo Escobar (@hubesco)Photo by Paolo Escobar (@hubesco)Photo by Paolo Escobar (@hubesco)Photo by Paolo Escobar (@hubesco)Photo by Paolo Escobar (@hubesco)Photo by Paolo Escobar (@hubesco)Photo by Paolo Escobar (@hubesco)
If you think that big tec uses testing/staging envs… think again. Shipping to production is the new “staging”… BUT with plenty of guardrails. Facebook, Uber, and Twitter all work like that. With tenancies, feature flags, staged rollout. Wrote more about it (cont’d):
I find this incredibly hard to believe from the so called “twitter whistleblower”: “Twitter doesn’t have a development, testing, or staging environments… just has the production environment and engineers use it for testing & development — all on live data.”
23
92
23
801
Paolo Escobar retweeted
19 money rules everyone should learn by 25: 1. Pay yourself first. As soon as you get paid, put money into savings. Automating this is even better.
291
5,505
213
22,702
Paolo Escobar retweeted
Five low-code / no-code tools that will change the way you do web development (free):
116
569
16
2,481
Paolo Escobar retweeted
built a quick app that uses gpt-3 to convert from English to RegEx so you don't have to waste time on stackoverflow: autoregex.xyz
391
4,085
1,026
28,362
Shipping to production: how do different types of companies typically approach this? Here's an attempt to visualize the differences: - Startups usually do few quality checks & move fast - Traditional companies tend to rely heavier on QAs - Large tech companies invest in infra:
25
137
9
890
Paolo Escobar retweeted
The "Software Engineering at Google" book is now free to read online: https://nitter.gq/t.co/cqX79uZNFK. Great insights on improving code quality & scaling engineering teams.
68
1,920
118
7,189
Paolo Escobar retweeted
1/ Today, Dedicate 1 hour to review your upcoming week's calendar. optimize it. • Target pruning 20% of the meetings • Move mtgs fwd or bwd based on priority - go through your list and add “next action” for each • Do a project round-up and ping your team for updates.
13
14
6
398
Paolo Escobar retweeted
Remote != working from home Remote = working wherever you work best, that could be in an office, a cafe, a coworking space, your bed, a ski resort cabin etc. Keep seeing this mistake everywhere
unavailable
48
1,136
45
2,916
How many times do you allow yourself to duplicate code before generalising it ? (utils, commons, abstraction, shared component) For me it’s three times. Duplication is fine. No need to over complicate. Generalise only when needed. #coding
2
1
Paolo Escobar retweeted
Life-changing mindset shift: “This won’t work for me because X.” Becomes "X is true. So, how can I make this work for my situation?”
2
20
2
124
#Productivity tools or apps should not ask to check in (ie log into the app and perform the action) They should be integrated with other everyday tools (like slack) to remind people to do something and do it directly from the other tool « Don’t call us, we will call you »
1
Pull requests should always be prioritised above coding as they are closer to deliver value. If they are not cleared fast, they get bigger as there’s less opportunity to ship code. You might think they break your flow but not reviewing them blocks another engineer flow!
Testing pyramid has been made with the assumption that end to end tests are slow, difficult to write, unstable. We have e2e tests that run against live api for each frontend PR. No flakiness, under 5 mins. They are the best tests as they are the closest to what users do
Test Driven Development is possible for React using Jest and React Testing Library. I code the entire behaviour of my component without any styling. And then I apply styling. It's a great way to decouple test and implementation jestjs.io/ testing-library.com/docs/rea…
Easy pdf generation in #reactjs with html2canvas.hertzen.com/ and github.com/MrRio/jsPDF html > canvas > image > pdf Example:
1
Discovery of the day: sonarlint.org/intellij Easy way to spot code issues while coding. Always better to spot issues when coding instead of waiting for a PR to be raised and analysis by sonarqube to be done. This plugin can also be paired with SonarQube server.
I recommend using nodejs or python for AWS Lambda. I tested java for lambda and it had two issues: - Cold start is quite long (7 seconds to initialise Firebase and Sendgrid SDKs - Need more CPU and memory so more expensive
1
1
Some links that helped me to use java: - aws.amazon.com/blogs/develop… - blog.ippon.tech/lambda-execu… - docs.aws.amazon.com/sdk-for-… It's too much effort compared to use another language that is more suitable.
1