Kodus blog
The best insights on software development.
What are you interested in reading about today?
The first sign of trouble is usually the build queue. A few developers join the team, commit frequency goes up, and suddenly the CI/CD pipeline that used to feel fast
At the beginning, the idea of a monorepo is quite appealing. Having all the code in one place, centralized dependencies, and the ability to change multiple parts of the system
When a team is small, keeping software quality under control feels intuitive. You can review every pull request, you know the history of the more “risky” parts of the codebase,
At a certain stage of growth, the codebase stops making intuitive sense. Logic that used to be simple becomes spread across multiple services. A change to the “user profile,” for
At a certain point in a company’s growth, you start to notice some strange things happening. Adding more engineers doesn’t seem to make the team any faster. The first month
As an engineering team grows, the code review process is often one of the first things to show signs of strain. What used to be a quick, collaborative check turns
FAQ