Optimize for recovery time, not defect count
Even if we reduce defects to, one per year, if repar takes days, any gain is lost.
Why do you estimate?
Estimates or no estimates? Unless or until you know why you want an estimate, even a "perfect" estimate is wasted.
The proper way to arrange cutlery
How I learned to stop caring about the orderly arrangement of my cutlery rack.
Skip the take-home assessment
Next time you're asked to do a take-home coding assignment for a job application, push back a little.
Subscribe to the Daily Commit
Every day I write about improving software delivery at small companies like yours. Don't miss out! I will respect your inbox, and honor my privacy policy.Unsure? Browse the archive.
Tiny DevOps episode #4 Peter Morlion — Working with technical debt
In this episode, I talk with Peter Morlion about his love for fixing and improving legacy code, what legacy code is, how we can detect it, and what to do about it when we're faced with it.
Why I don't like the "Tech Lead" role
The "Tech Lead" title is too often (ab)used as a way to "lord it over" people who are "less technically capable".
Software development is so much more than writing code
Most education focuses on how to code, but this is only a small part of becoming a productive software developer.
What problem are you trying to solve?
I hear people ask seemlingy good questions, but they often miss a fundamental part: What problem are you trying to solve?
Things that don't scale well
Some things that don't scale well: Databases. Dev teams. Monoliths. Microservices.
Diseconomies of Scale
We've all heard of economies of scale. Some things have diseconomies of scale.