Optimizing CI/CD as the development team grows
The first sign of trouble is usually the build queue. A few developers join the team, commit frequency goes up,…
The first sign of trouble is usually the build queue. A few developers join the team, commit frequency goes up,…
At the beginning, the idea of a monorepo is quite appealing. Having all the code in one place, centralized dependencies,…
When a team is small, keeping software quality under control feels intuitive. You can review every pull request, you know…
At a certain stage of growth, the codebase stops making intuitive sense. Logic that used to be simple becomes spread…
At a certain point in a company’s growth, you start to notice some strange things happening. Adding more engineers doesn’t…
The product roadmap says six weeks. Deep down, you know it’s ten. Maybe twelve, if that dependency doesn’t land in…
A new feature request lands, and you realize it has to touch the old permissions module. The project planning meeting…
In a fast-growing company, the default state of engineering is reactive. The product roadmap is packed, deadlines are tight, and…
Most engineering teams have some dashboard lying around. Usually it’s full of charts tracking everything from Jira ticket velocity to…