Kodus blog
The best insights on software development.
What are you interested in reading about today?
In many teams, security review only happens at the end of the cycle, sometimes just a week before release after months of development. The result is almost always the same:
Who hasn’t been there? You open a file to fix a simple bug and run into a block of tangled JavaScript, with no comments and full of improvised solutions. Just
We’ve all been there. You join a new team, clone the repo, and stare at a file that’s 2,000 lines long. Or you’re asked to add a “simple” feature to
Building software is one thing. Building software that people trust, rely on, and don’t want to throw out the window is another thing entirely. The gap between those two realities
Let’s be clear. Almost everyone has been through this: you inherit a project, open the codebase, and find chaos. Inconsistent names, functions hundreds of lines long, and no tests. The
Let’s be honest: most internal documents are where good intentions go to die. And at the top of that list, right next to “onboarding checklists,” are the official software testing