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…
The repository structure that works for a two-person startup almost never works for a fifty-person engineering team. What starts as…
Every planning meeting seems to end up in the same place. Engineering brings up a legacy service that’s getting slower…
A pull request opens, and the review requests go out to the same two or three senior engineers. A day…
When an engineering team grows from five to fifteen, the informal communication channels that once worked perfectly start to break…
The conversation about moving from a monolith to microservices usually starts when things get painful. Builds take forever, a small…
A technical debt does not appear out of nowhere after a bad sprint. It works more like a tax you…
Publishing new code can feel uncertain. You push a change and want confidence that nothing outside the intended scope was…
In many teams, security review only happens at the end of the cycle, sometimes just a week before release after…
Building software is one thing. Building software that people trust, rely on, and don’t want to throw out the window…