GoatInTheMachine

@RobertHarvey Even that definition is too narrow - bad choices create tech debt whether or not the authors knew the decision was poor at the time it was made

@jamesqf thats basically an argument to use an IDE in the first place! I do understand your point though.

"IDEs can slow you down if you're a fast programmer." Really? Can you give any examples?

@Blrfl on the other hand, prematurely DRY-ing up code before a good abstraction is clear can really hurt productivity too, as a shared abstraction is a shared dependency. I'm not disagreeing, btw, just pointing out there's definitely a balance to be found.