I am reading Clean Code again (we're doing it at book-club at work). This stands out more than anything so far: Nothing has a more profound and long-term degrading effect upon a development project than bad code. Bad schedules can be redone, bad requirements can be redefined. Bad team dynamics can be repaired. But bad code rots and ferments, becoming an inexorable weight that drags the team down. Time and time again I have seen teams grind to a crawl because, in their haste, they created a malignant morass [...]

I enjoy the metaphor he mentions near the beginning, "We call it wading. We wade through bad code." I feel that. And smell it.

We all get shitty about/at the crap legacy code we need to work with. We forget that that was "previous us". Maybe not that line of code / that codebase, but the code at yer previous gig etc. We could im to stop working like that.

Bad code is subjective though. The glass is either half full or half empty, either way, the computer sees it as an INT or FLOAT at 50.