It's hard to read because of the lack of structure, but in the end they're complaining that some code golf competition's winner wasn't legible code that's great to maintain.

If your job is to work on code that looks like that, that really sucks and I'm sorry for you, unless you love doing it, in which case cool. But for most of us it's really not and while I often feel close to being broken, I'm 100% convinced that plenty of jobs are much more taxing, and if I reduced my hours, it would be a breeze. But there's features to build and bugs to fix, and I'm going to retire in a year or three in my forties because that's how good tech pays even people like me who can figure stuff out but are by no means geniuses.

"..so many of the programs you depend on are written by dicks and idiots." Man, I've written a lot of programs..

Well don't know if I'm a dick, but my code have proven its author to be an idiot many times :)

Love it.

And a good explanation of why so many devs reach burn out.

But two things can be true.