Vic 20 -> C=64 -> few 386/486 units -> AMD K6-2 and a ton of stuff after that. And maybe something in between.
And now I’m writing this in my garage computer which I picked up from a e-waste pile at work few years back and it has more computing power than pretty much all the systems combined I had before being 18 years old. And when we (as a family) got our first “mobile” phone it was hardwired to a car electronics since they took ‘a bit’ more power than the supercomputers we carry in our pockets today (obviously Li-ion batteries were not a thing either, but that old Motorola NMT450 took a crapload of power by todays standards).
It’s been a wild ride so far. My grandparents were on top of the technology when they got the first landline phone around the neighborhood (I’m living in a rural area so it was not a new invention back then by any stretch) and now I can just yell to a entity in my palm to show me pictures from another planet or a high definition live video from Earth orbit.
And still I’m somehow trying to teach basic tehcnology concepts to both my parents and my kids. It’s bizarre to try and explain about benefits of touch typing to a 16 year old who thinks it’s pretty much impossible for anyone to type out an essay at school containing 2000 words in an hour (33wpm)…
I’ve seen some shit. But I’m also old enough to not care. I’m a freaking system administrator, not a surgeon. No one has died if their email is unreacable for an hour or two. Shit happens, then you deal with it and that’s all. Difference between a junior and a seasoned veteran is that old guys with battle scars is that the seasoned guy knows that something will break, shit will hit the fan and everything might turn up into a chaos and plan accordingly. Juniors will either endure and learn along the way or crumble.
When you’ve been in the business for few decades it’s not that big of a deal to cause an outage. You know how to fix your shit, you know how to work with a severely crippled environment and you know how to build the whole circus from the ground up. And you also know that no matter how disappointed or loud the C** suits are, they’ll calm down once you get them out of the hole.
Just today I had a meeting with discussion on what to do if some obscure edge-case ruins our ~5k users and few continents wide AD tree. Sure, if that would happen, it would most definetly suck balls to get back up and it would hurt the company bottom line and it would mean few nights with very little sleep, but no one would still die and our team is up to the task to build the whole crap out of nothing if needed. So, it’s just business as usual. But all of us have been in the business long enough that we know how to avoid the common pitfalls and we trust eachother enough that should the shit hit the fan in the big way we could still recover the whole situation.
And still, even if the whole thing burns up in the flames, I’ve got the experience and skillset under my belt which will be valuable to some other business entity. I just don’t care if the main office building is on literal fire. It’s not my problem to fix immediately and when it is it’s still just work. I put in the hours they pay for me and do whatever I can but when I’m off the clock the employer doesn’t really exist in my world.