mean rant to flesh that thought out
when I read shitty code I try pretty hard to give the benefit of the doubt to whoever wrote it; it's rarely their fault that is sucks, and there were probably a bunch of weird circumstances at the time that I'm not aware of.
But every codebase seems to have its own "usual suspect," where you stumble upon some new terrible thing, go to straighten it out, and when you look at the history to get some context for why it's there, there's that fucking name again!
@devlaf I had a friend describe maintaining a codebase written by someone who was clearly new to the language. "Ah, here's where they learned function composition, and here's where they learned about exceptions, and..."
I'm sure they eventually got good at the language, but the output in the meantime—untempered by code reviews—was regrettable.
small, relaxed instance for friends