New blog post: “You're Never Going to Fix Your Technical Debt." https://collindonnell.com/youre-never-going-to-fix-your-technical-debt
You're Never Going to Fix Your Technical Debt

I’ve been thinking this week about how I write code and the quality I want to aim for. I’ve worked some pretty big and successful project...

Collin Donnell
@collin I found a typo: “Your were probably wrong”
@jeff Someone should make a tool that finds these kind of grammatical errors for me.
@collin I feel all of this! Also, there’s a tendency in programming to make data models or classes as generic as possible to be “as reusable as possible” across different scenarios, but I find that’s usually not warranted in the long run and just results in muddying the waters. I find it’s easier to directly solve the problem at hand, and only think ahead to an extent — avoid going overboard with generic-ness/reusability. YAGNI, and if you do, you can always do some refactoring.
@command_tab @collin I think refactoring, abstraction are over-used just like "agile". Generally, if someone keeps saying they have to be done, it's overdone. Only right when we do it quietly.
@collin This is a bit overstated compared to my experience, but I think it still makes a good point - one should leave code in a state one can accept without relying on it being cleaned up “later”.
@henrik I mean, yes. I tend to overstate things in writing to make it a bit more compelling.