Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
Y2K was fun: I got $1000 just to be on available in case something blew up (and would have gotten double-time had they actually had to call me). Nothing blew up and I got to pocket the $1000 for doing nothing other than staying sober.
Full-time web dev; JS lover since 2002; CSS fanatic. #CSSIsAwesome
I try to stay up with new web platform features. Web feature you don't understand? Tell me! I'll write an article!
He/him
just to be clear on that one, it wasn't that nothing happened, it was that a ton of IT staff all over the world (including my dad) had a mad rush to patch critical systems to prevent the bug
I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
You can see that again in roughly 19 years. The issue caused by the rollover of the 32-bit UNIX time era will however probably not be something that just gets laughed off afterwards. Unlike Y2K, much of the affected code is running in places that quite simply can't be updated even if people wanted to fix them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The Y2K era! It would be fun to see devs expecting a worldwide crash on systems and laugh about it when nothing happened. lol
Loads of people did work to make sure it was ok too.
But yes. One washing machine turned off.I have a sticker somewhere.
Y2K was fun: I got $1000 just to be on available in case something blew up (and would have gotten double-time had they actually had to call me). Nothing blew up and I got to pocket the $1000 for doing nothing other than staying sober.
just to be clear on that one, it wasn't that nothing happened, it was that a ton of IT staff all over the world (including my dad) had a mad rush to patch critical systems to prevent the bug
You can see that again in roughly 19 years. The issue caused by the rollover of the 32-bit UNIX time era will however probably not be something that just gets laughed off afterwards. Unlike Y2K, much of the affected code is running in places that quite simply can't be updated even if people wanted to fix them.