Kodus blog
The best insights on software development.
What are you interested in reading about today?
The moment something starts to slip rarely shows up as a big event. It is usually a pull request that sits for days because no one is sure who should
When you are scaling fast, the pressure to ship new features is constant. At first, it feels like everything is moving at an incredible pace. Then, almost without you noticing,
In a fast-growing startup, the default mode is to ship as fast as possible. A new feature needs to go out for a critical demo, a bug fix is blocking
The repository structure that works for a two-person startup almost never works for a fifty-person engineering team. What starts as a simple, clean codebase eventually develops friction points as more
Every planning meeting seems to end up in the same place. Engineering brings up a legacy service that’s getting slower and harder to deploy, while product has a new feature
A pull request opens, and the review requests go out to the same two or three senior engineers. A day passes. Then another. Eventually, feedback trickles in, but in the
FAQ