Six desks, six time zones, and one shared love of good lighting. The hardest problems on an engineering team are rarely technical. This post is about the habits and small agreements that let a group of people ship good work without burning out.
Around the team
We changed one thing at a time and wrote down why. That record turned out to be the most useful part, because six months later nobody remembered the original problem.
What we would change next time
If you try this on your own project, start with one page or one service rather than the whole codebase. A small experiment gives you real numbers to argue with, and it is easy to roll back if the idea does not fit.
- Agree on what code review is for.
- Write decisions down where people will find them.
- Automate style arguments away.
- Pair new people with a named mentor.
Would love a follow-up on how you test this in CI.
The renaming spree is a rite of passage.
Bookmarked. The code sample alone saved me an afternoon.
We run this in production at a fairly large scale and can confirm the caveats are real.
Solid write-up. The warning about caching bit us hard last year.