Kodus blog
The best insights on software development.
What are you interested in reading about today?
As a company grows, the way engineering and product teams work together begins to wear down. What used to be quick hallway conversations and shared assumptions turn into missed deadlines
This is a transparent write-up of the issues we ran into over the last few weeks while migrating our architecture. The goal here is not to justify decisions or hide
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
FAQ