3 ms·
I would argue that lots of useful code is an utter dumpster fire internally. That doesn't mean we shouldn't strive to do better. Useful |
by aaronbrethorst 2y ago
I would argue that lots of useful code is an utter dumpster fire internally. That doesn't mean we shouldn't strive to do better.
Useful
|
|
Bad-------Good
|
|
Not Useful
- eyelidlessness 2y agoThere’s probably a time axis that comes into play, at least for a large number of projects. Bad code which is immediately useful, even indispensable, can decline in utility fairly sharply the parameters which determine its usefulness change faster than it can be adapted to meet those needs or goals.
- aaronbrethorst 2y agoThere's definitely a time axis that comes into play. I'd say that all tech debt should be (but probably isn't always) in that top left quadrant. Like they say, good/fast/cheap - pick two (if you're lucky).
- earnesti 2y agoNot useful code is always bad, because you never had to write it. It is just a waste.
- aaronbrethorst 2y agoRequirements change. projects pivot. Yesterday’s must have feature is tomorrow’s deleted code