Leadership
How to manage technical debt in a fast growing environment
When you are scaling fast, the pressure to ship new features is constant. At first, it feels like everything is…
Leadership
Code Review
Balancing delivery speed and code quality in scaling startups
In a fast-growing startup, the default mode is almost always to ship as quickly as possible. There is a feature…
Leadership
Monorepo vs. multiple repositories: what’s the best strategy for a growing codebase?
The repository structure that works for a two-person startup almost never works for a fifty-person engineering team. What starts as…
Leadership
Technical debt vs. new features: how to set priorities
Every planning meeting seems to end up in the same place. Engineering brings up a legacy service that’s getting slower…
Code Review
How to scale code review in a growing team
A pull request opens, and the review requests go out to the same two or three senior engineers. A day…
Leadership
Avoiding knowledge silos in growing engineering teams
When an engineering team grows from five to fifteen, the informal communication channels that once worked perfectly start to break…
Leadership
When to break up a monolith: a guide to adopting microservices
The conversation about moving from a monolith to microservices almost always starts when the system stops feeling comfortable. The build…
Leadership
How to reduce technical debt in every pull request
A technical debt does not appear out of nowhere after a bad sprint. It works more like a tax you…
Leadership
How to Write Software Test Cases
Publishing new code can feel uncertain. You push a change and want confidence that nothing outside the intended scope was…