> Building the wrong thing fast is about as useful as not building anything at all. SAY IT LOUDER Fully agree. Plus, you may be faster in the short term but y

> Building the wrong thing fast is about as useful as not building anything at all. SAY IT LOUDER Fully agree. Plus, you may be faster in the short term but you won't in the long run. The effects of both good code and bad code compound. "Tech debt" is just a fancy term for "compounding shit". And it is true, all code is shit, but it isn't binary; there is a big difference between being stepping in shit and being waist deep in shit. I can predict some of the responses Premature optimization is the root of all evil There's a grave misunderstanding in this adage[0], and I think many interpret it as "don't worry about efficiency, worry about output." But the context is that you shouldn't optimize without first profiling the code, not that you shouldn't optimize![1] I find it also funny revisiting this quote, because it seems like it is written by a stranger in a strange land, where programmers are overly concerned with optimizing their code. These days, I hear very little about optimization (except when I work with HPC people) except when people are saying to not optimize. Explains why everything is so sluggish... [0] https://softwareengineering.stackexchange.com/a/80092 https://softwareengineering.stackexchange.com/a/80092 [1] Understanding the limitations of big O analysis really helps in understanding why this point matters. Usually when n is small, you can have worse big O and still be faster. But the constants we drop off often aren't a rounding error. https://csweb.wooster.edu/dbyrnes/cs200/htmlNotes/qsort3.htm https://csweb.wooster.edu/dbyrnes/cs200/htmlNotes/qsort3.htm