[SamUK96]

Parent comment is why I tell everyone to read Pragmatic Programmer, especially the "broken-window theory" section.

For those unaware, an empty house can go untouched for decades in NYC, but once it develops a broken window, it is ransacked and squatted within hours. Small failures invite large failures.

"Javascript bloat isn't too bad, just another 10KB" turns into (VERY quickly) slow + terrible code that is trash. Small amounts of apathy about code invites other developers to sink to lower (more sh*tty) standards until there is nothing good left.

I'm not saying we should all code in assembly and c and make sure our arrays are memory aligned and pointers efficiently used, etc. etc., but we should also not just stop caring about code quality for "productivity" sake.