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):
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:
The "Software Engineering at Google" book is now free to read online: https://t.co/cqX79uZNFK. Great insights on improving code quality & scaling engineering teams.
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.
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
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
Had the pleasure of speaking to "Le Monde" about my career and AoE2. If you don't speak french, translate it and give it a read :)
https://t.co/JxbHtnP1aC
#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 »
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
https://t.co/COPEICTdL9
https://t.co/Cgu8hVizYR
Discovery of the day:
https://t.co/83wM4KqDv3
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.