Maybe. I find myself strangely finding code less and less crappy the more as I've grown as a developer (currently 11 years). Or perhaps, a lot happens to be crap, and it just doesn't bother me anymore like it use to? Somehow I rarely find myself frustrated with coding anymore, whether that's involving other people's code, or my own.<p>I think part of it is just realizing there is no perfect code, as there's a tradeoff with everything. Acknowledging that someone else was wanting to optimize for something (e.g. efficiency, performance, robustness, scalability, time to implement, ease of maintenance, readability, handling a particular problem) and that it came with a cost at one or more of the other categories, and you realize that the strengths of anything can also be its weakness (and vice versa). It's why languages that are easy to understand, are often criticized to be verbose. Why code minifiers can improve performance, at the cost of readability. Additionally, sometimes the problem isn't fully defined when code is getting written, so it's hard to simply blame code for bugs that do crop up. It's simply unfinished code in such scenarios, not necessarily crap code.<p>But that said, there is definitely objectively bad code out there. I'd say if you see code trying to solve a given problem, but doing it a much more complicated way than is necessary (by like orders of magnitude, not just a couple of degrees), then it's clearly crap, as it isn't good at any of the categories mentioned above, let alone at its intended purpose.<p>I'd say I come across undoubtedly bad code less often than not.