Someone 25+ years ago had a predilection for "single return from every function", which left their code with 10+ levels of indentation, which very quickly got out of hand with 8-character tabs and 80 character screens.

Someone else used to believe that fixed size arrays of 256 were okay because surely no-one would ever use that many things, ever (HAHA production rendering SNORT). A few of those 256s persist in the code, like Cthulhu slumbering gently in the depths..

(5/10)

Former coworker wrote very efficient code but spelling was not their forte, which was problematic when it came to the two L's in tessellation and related classes..

Someone on my team now is very adept with modern C++ and uses all the latest features I can't keep straight in my head. All their loops that can be range based for loops are. They can probably write a lambda correctly on the first try. There are lambdas in their code. This is probably a feature.



(6/10)

Someone else on my team now uses a Mac, and every now and then some Unicode hyphen character makes its way into comments and my Linux box displays a mysterious character when I page through the code that always catches me off guard.


I could go on and on about all of our recognizable quirks, but living in a code base with that history is like living in a Berkeley Craftsman home. 



(7/10)

It's old, it's creaky, okay, it's missing AC and you're probably going to die when it hits 100 in the summer (which happens all too often these days), but dammit, it's charming and it's artsy and you will die defending the seventeen layers of paint that have accrued in the living room (or you're just too scared to sand it because of lead paint). It's lived in and it's comfortable.

Whereas if you've looked at Claude generated code, like I've had to for the past six months, it's...


(8/10)