The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
To some of my colleagues, it seems to come naturally; it takes them no extra effort.
My answer: No, quite to the contrary. Cleaning up messy, unreadable code (whether deliberately or unintentionally looking like entries to the IOCCC) to make it lucid, readable an maintainable, is far more satisfying. It gives me the same pleasure as the joy it gives me to delete code lines that are no longer needed. Often, those are two sides of the same coin.
No, but I am now responsible for a product that was originally written by an asshat who did. This body of code was the only thing he worked on for 20 years. When they tried to assign him to another product, he took his ball, went home, and retired early. After several layoffs, his product is now in my lap. The code was deliberately written so that only the original author could maintain it. No naming conventions, other than keep them as short as possible. No consistency in block structure or indentation. Basic principles of structured programming like single-entry, single-exit are ignored. Most error returns are ignored. Magic numbers are used wherever possible. Most pointer arguments are specified as void * to avoid typing struct name *. There are so many code smells it's reached the level of aromatic white noise.
I see this f***er every so often out on the bike path. I've had to spend enough time debugging his sh*t over the last few months, he may just have an accident.
if your organization does not review one guys code
I work for a hardware company, whose engineering management consists entirely of hardware engineers. All of our "processes" are based on hardware engineering principles.
The end result is that it's very difficult to get any traction for different practices for software. Our one attempt at a code review was mismanaged from the start, and ended with the engineer concluding the review by saying if they ever tried it again with his code, he'd walk.