3 ms·

This is a great excuse to write terrible code that "works" until it goes out and breaks. Then it doesn't work because you saved a little bit of time by cutting

This is a great excuse to write terrible code that "works" until it goes out and breaks. Then it doesn't work because you saved a little bit of time by cutting corners. What is the cost of it breaking? $0? $1,000? $10,000? What is the cost to fix the broken code? What is the cost to maintain it? How much developer time do you waste down the line because they have to fix the "working" code? I say these things because I've seen this attitude expressed in a large codebase and it sucks a lot to work with and has wasted many hours of developers' lives. Technical debt is almost never paid back. Just know that going in to whatever you are building.

mrweasel 13y ago
>How much developer time do you waste down the line because they have to fix the "working" code? That is absolutely spot on. One of the hardest thing is explaining to management that the code your co-worker wrote in a "flash" three years ago is still eating up developer time today. We have a few ill-conceived or badly written systems that seems to eat up time and constantly interfere with new projects. The problems are pretty much invisible to management, because the developers spend a few hours here and there proppring up the badly written systems. Over time you end up having to spend all your time just putting out fires rather than helping the business moving forward.
- randomflavor 13y ago
  O-TI makes money fixing broken shit.