Why Legacy Systems Are Worth Your Time
I know. When you hear legacy, you think , , weird edge cases, and “what the hell just broke now.” Every moment feels frustrating. You don’t know what the next change will trigge...
Software Judgment Series
Technical decision-making under real constraints: when to refactor, how to manage technical debt, designing better APIs, and avoiding fake progress.
Refactoring Untested Code
Most teams realize they are dealing with a legacy repo only when a tiny change turns into an operation. A oneline fix suddenly needs three people, two days of manual checks, and...
Addressing Technical Debt
Tech debt occurs when we solve a software problem with our limited understanding of the business at the time. We start building a solution to get feedback as early as possible....
Good APIs Age Slowly
I have noticed that APIs are a bit like abstractions in general. APIs that impress people quickly are very often the ones that cause the most trouble later. I do not mean this a...
Compatibility Is a Feature
A system only reveals what it's made of when it starts changing. At first, they often look better than they are because the code is still new. The data is still fairly clean. Th...
How Teams Choose Language
Choosing a programming language is one of the most defining decisions in software development. It shapes how a team writes, maintains, and reasons about their system. Today, the...
Hype in Software Development
We live in a time when every month brings a new framework, library, or architectural pattern that promises to change everything. Increasingly often, we come across a new technol...
Why Over-Engineering Happens
If you’ve worked in software long enough, you’ve probably seen it: a CRUD app serving a handful of users, deployed on a Kubernetes cluster with half the CNCF landscape stitched...
Smaller is Faster
“Smaller is faster” is a wellknown hardware design principle, as you might already know it. Generally speaking, smaller pieces of hardware will be faster than larger ones becaus...
Most of What We Call Progress
Most of what we call progress in software is just motion. New tools, new frameworks, same problems. Maybe fancier logos. Our industry always has this collective thrill that a ne...
Who needs an Architect?
An architect? According to Wikipedia, an architect is a person who plans, designs, and oversees the construction of buildings. So, we obviously have derived the role from civil...