I guess this probably isn't as bad now with actual privilege separation (non-admin accounts) in Windows and Macs these days, but some memories are hard to forget.
There's something to be said for a box which is going to be just fine if you power-cycle it.
Presuming a Windows environment, have you ever tried DeepFreeze? Every school environment I've worked IT for that hasn't gone diskless seems to have started using it in the last decade. A lot of demo computers on display in stores, too (I think my local Apple Store is now using the OSX version; not sure how widespread that is.)
If you're running a Linux setup, of course, you can just do the equivalent with a tmpfs overlay on /.
Fortunately I only had to witness it and never had to run a whole fleet of Windows boxes.
As someone who started programming when I was 21, I sometimes feel like I don't stand a chance.
I'd argue if you're willing to embrace a complex new skill in adulthood, you're probably going to be more willing to learn new stuff as your career progresses. This will give you an edge when your peers start getting set in their ways.
Another thing: I learned to code when I was 13, and was fortunate enough to have some friends in grades 7-12 who did the same, but ultimately the stuff we did was simplistic and hacky. It was totally undisciplined, and wasn't exactly production quality stuff. We were juvenile, and our code was juvenile. In a good way.
And in reality years of coding doesn't matter. Learning to code early doesn't matter. What matters is with how many people you've collaborated. And how many releases of different products you've shipped.
You can code you whole life, but if it is the same damn piece of code, you wouldn't learn a thing. And if you don't actually release stuff, you also wouldn't learn a thing.
Last point (releasing stuff) is very important. If a kid 'learns' to code, but doesn't release his stuff - it is not real. Most of that learning is far from reality and wasted.
But that's fine. Use your cross-functional skills to your advantage... whatever you did from ages 8-21 when combined with the coding you did from 21-present is likely just as (if not more) valuable than the skills a person who's been coding since childhood.
It all comes down to your ability for self inflection, a strong desire to always be better and, of course, a love of programming.
If you have the same passion, then starting late shouldn't hold you back that much.
Having said that, I am one of the lucky ones who started young.
I really think, more than anything, this is why we should be teaching kids to code and so on in school. Most of the good coders I know have been doing it from a young age, and I think a lot of it comes from the fearlessness of youth.
Personally, I know I owe a lot to this. I "broke" the computer more times than I can count, by just experimenting, playing and otherwise doing stuff that I now know to be "reckless". There was a guy in the IT department and my dad's work who gave me an absurd number of hours of free tech support and teaching, because I couldn't figure out how to undo some of those mistakes, and would patiently walk me through getting things put right before my folks came home from work. (In retrospect, I don't think they would have minded, but I didn't want to get in trouble for breaking the expensive toy!)