TDD only makes sense if you already know the outcome... or does it?
If you don't know what your code should be doing, you have no business writing any code anyway!
The affect of comments in unclear code
Roses are red, violets are blue. Honey is sweet, and clear code is, too.
Help wanted naming this code
Do you have a helpers or utils class or directory in your project? Maybe both? Quit it!
Regular Expressions Are the Best! s/Best/Worst/
Regular Expressions. Ya love 'em or ya hate 'em. But it shouldn't be so black-or-white. Here's when they do, and don't make sense.
Many people don't understand refactoring, and this leads to several anti-patterns.
The Dangers of Fatal Logging
log.Fatal violates the Single Responsibility Principle in insidious ways. Never use it!
Refactoring itself is worthless
Why refactoring doesn't, and shouldn't provide direct business value
Unsure? Browse the archive.
How to get better at story slicing
How do you avoid days-long pull requests? How do you make your changes smaller?
Why "Consider refactoring this" comments are silly
Code is always subject to refactoring when the need arises. Adding a comment to that effect is just noise.
Tiny DevOps episode #26 Parham Doustdar — The Blind Leading the Sighted: What We Can Learn From an Ex-Software Engineer Without Sight
Parham Doustdar, Engineering Manager of Accessibility at Booking.com, joins me to discuss life as a fully blind sofware engineer, and how we can make engineering tools more accessible for everyone, not just those with disabilities.
How can I eliminate technical debt?
You can't eliminate technical debt. Nor should you want to. But where does that leaev us?