The sad thing is that he -should- be the norm, not the exception.
I have been working for about 10 years since graduation and I have met about 5 coders of that caliber, the rest is more or less pure crap that only creates the fastest possible fix. Since "everyone" also moves on to another position/workplace so often, its almost always some other poor soul that gets to fix the fuckups of previous coders. Problem is that it's a way too big shortage of coders so that ppl that should not be coding still are.

Where I live, large it-consult-firms have 3 months long "Learn to code and be a consultant" "educations", and then floods the market with crappy coders that dont know shit.

I get 2 hours instead of 2 days and it should have been in production by yesterday 😂I just need to get myself a time machine :)

Haha well, test is luxuary most us doesn't have. I spend at least 40% of my time cleaning up after all the idi*ts where I work. Recently spent 10 days cleaning up our data warehouse after The analysets did a 'minor change' to a production system, ninja commit + deploy style, a Friday at 16:55 :) Problem is that without good company-wide reporting/followup, the cost of puttning out fires gets hidden and the madness continues :) Combine that with the technical debt collected during the last 7-10 yrs (you know the 'this is just a hacky pilot/PoC' that then got into production, todo's and 'will fix later'....). Also all legacysystems that needs TLC on a weekly basis, I would say my team spends less than 10% on new features. Today was thursday and we have only fixed broken things so far this week :D

Start dreming about gigabit? :D