6 ms·
My fake job in Y2K preparedness
- mlyle 2y ago> Finally, it was a fake job because the problem that the Conglomerate had hired Andersen to solve was not real, I don't really like the whole popular understanding of the y2k thing. Substantial problems with infrastructure were fixed. It wouldn't have been Mad Max, but business operations could have been affected for weeks. Instead, we had almost smooth sailing because there was an appropriate amount of preparation beforehand. (Not to say that there wasn't graft like he describes as part of that preparation).
- magicalhippo 2y agoBack when I was just out of school, I worked as a computer tech guy. Our company got hired to test all the PC+BIOS version combinations a certain department had, to ensure they'd work after y2k. Spent several weekends rigging up computers, and running a battery of tests on them. Did actually find a handful of combos which misbehaved, mostly incorrectly handling the leap year IIRC. None of them had NTP running, so could have been an issue. A few didn't handle the transition well at all. Most got resolved by a BIOS update. I recall thinking after 2000 came and went that sure, a fair share of superfluous work had probably been done, but the reason it seemed like such a nothingburger afterwards was because a lot of work went into ensuring exactly that.
- dgfitz 2y agoI read it as, a real problem wasn’t identified by the management side of the company. Finding typos in spreadsheets and printing corrected versions to slap in a binder was a CYA event, the article says as much.
- RHSeeger 2y ago> The problem was known variously as Y2K, ... I really hate this take some people have (especially people that weren't there at the time) that Y2K wasn't a real problem. It was a real, large problem effecting businesses across the globe. But the thing is, the problem wasn't that "everything was going to fail catastrophically at the turn of the year". It was that "some things could fail catastrophically at the turn of the year, and we didn't know which things would". So a lot of time and money went into figuring out which things actually had a problem, and fixing them. It was entirely possible that, if we didn't fix something, planes _could_ fall out of the air, or energy providers could shut down for long periods of time. So we spent lots of time and money finding out what things needed to be fixed. And "it turns out that not that not that many things did really need to be fixed" is a GREAT result from that time and money; arguably the best possible result. But it doesn't invalidate that the time and money was spent, in the same way that "I didn't get into an accident" doesn't invalidate the fact that wearing your seat belt is a good idea.
- cromulent 2y agoIt's infuriating. I worked on a Y2K project in 98-99 for a major car manufacturer. They tested the ERP system for Y2K (in 1997) and it failed, in a way that would make the business fail. They replaced it via this project and the business continued to be successful without interruption. Another company I know of simply backdated their whole system by 10 years. This worked, but unfortunately the contract cycle renegotation reminders then did not appear, and competitors took many of their contracts over the next year or so. They went out of business in a couple of years. I implemented a new manufacturing and retail system in 1992, and we used 4 digit years. The company owner complained that they were a needless expense and annoyance and that there was plenty of time to deal with Y2K. They continued to use the system well into the 2000s. The space shuttle never flew over New Year's eve/day as they couldn't handle a single year rollover, let alone a century. Some use cases can simply avoid the problem.
- kens 2y agoStrangely enough, a few months ago I came across the bug fix for that Space Shuttle problem. "CR 93160: Year End Roll Over (YERO) Reset. Allows in-flight reset to January 1 without an IPL and complicated procedures while maintaining a good state vector." (IPL is "Initial Program Load", IBM-speak for a reboot.)
- RaftPeople 2y ago> It's infuriating. I worked on a Y2K project in 98-99 for a major car manufacturer. They tested the ERP system for Y2K (in 1997) and it failed, in a way that would make the business fail. They replaced it via this project and the business continued to be successful without interruption. Same. I worked on multiple enterprise projects for Y2K where we advanced the dates on the customer's system and ran it so we could see the magnitude of the problems and prioritize the remediation process. There were some things that were temporarily annoying and there were some things that were critical to the business and could not be worked around manually by throwing people at it, the system needed to be fixed.
- zugi 2y agoPerhaps this line from further down is what was meant by "not real": > The Andersen position was that “Y2K is a documentation problem, not a technology problem.” Sure, there were other people at other companies solving the "real" Y2K problem, but the problem Andersen was solving was not so real.
- iwishiknewlisp 2y ago*she
- shever73 2y agoThe whole article was full of supercilious snark. A lot of it was aimed, rightly, at Andersen, but it does take away from the fact that Y2K was a real issue that affected millions of computers worldwide. I patched hundreds of vulnerable systems, rewrote code for mission-critical software and still ended up with a call-out to halted manufacturing plant on January 1st, 2000. If there hadn’t been a global, coordinated response, things would have been a lot worse. And let’s not forget that there were life-changing effects of the bug beyond the snarky “garage door opener” issue mentioned in the article. [0] [0] https://www.theguardian.com/uk/2001/sep/14/martinwainwright https://www.theguardian.com/uk/2001/sep/14/martinwainwright
- rhdunn 2y agoThe Y2K problem would have manifested as the year 2000 being interpreted as 1900. As such, it could have affected anything around dates (age verification, paynment due dates, morgages, etc.). Other more extream issues (power outages) would have been unlikely but it is impossible to predict all the knock-on effects Y2K would have had. There were several issues that happened as a result of Y2K.
- voiceblue 2y agoMaybe you are being downvoted because this is “obvious”, but as it turns out it is not obvious enough for the TFA itself to not have this error: it prophesied that on January 1, 2000, computers the world over would be unable to process the thousandth-digit change from 19 to 20 as 1999 rolled into 2000 and would crash
- ralferoo 2y agoI came across a reasonable amount of perl code that happily formatted the year 2000 as 19100. The functions that converted from seconds-since-1970 to a "human readable" parts returned a year relative to 1900. Most people would format using sprintf("%d/%d/%d",$d,$m+1,$y+1900) but some code I inherited instead used sprintf("%d/%d/19%d",$d,$m+1,$y). I never did figure out if it was due to stupidity or malice.
- ta1243 2y agoI kept seeing this behaviour on some websites in to the late 00s and possibly even in to the early 10s, your comment mede me realise I haven't seen it recently though :(
- duskwuff 2y agoA big part of that problem was Javascript's terrible Date API, which was practically a carbon copy of the (equally terrible) java.util.Date. For no good reason, its Date.getYear() method returned the number of years since 1900.
- cristoperb 2y agoSee also David Graeber's "On the Phenomenon of Bullshit Jobs": https://strikemag.org/bullshit-jobs/ https://strikemag.org/bullshit-jobs/
- rzimmerman 2y agoI worked for about a year with a consulting firm that handled "Y2K compliance". Unlike this Andersen exercise in legal face-saving, it was a real job. Big companies hired us to do a full inventory of their site equipment (this included manufacturing plants, Pharma stuff) and go line by line with their vendors and figure out which components had known Y2K issues, which had not been tested at all, and which ones were fine/had simple fixes. We helped them replace and fix what needed to be fixed. Y2K was a real problem. The end-of-the-world blackouts + planes falling from the sky was sensationalism, but there were real issues and most of them got fixed. Not trying to take away from this very interesting story of corrupt cronyism, but there were serious people dealing with serious problems out there. "Remember Y2K? Nothing happened!" is a super toxic lesson to take away from a rare success where people came together and fixed something instead of firefighting disasters.
- victor9000 2y agoI've seen this phenomenon play out multiple times in my professional career, where a considerable amount of effort goes into creating a robust system only for the effort to be minimized by management due to its stability. Somehow preventing a plane from crashing is not as valuable as digging through the ashes.
- deepsun 2y agoA lot of jobs are like that. Accounting, legal and security work is only visible when it was bad. Noone is being promoted for doing good job that prevented an unanticipated disaster from happening.
- HPsquared 2y agoThat's why presentation and "sales" type skills can be useful. A bit of doom-mongering internal PR about the problem, then present the solution. Don't just solve it quietly.
- makeitdouble 2y agoIn agreement with your overall point, accounting and legal is different though. For accounting, it's not a simple cost center, and is at the front line to show the numbers. They can say how much it will cost to not comply with a rule, or how much they saved by creativity or ingenuity. Being that close to the money is a tremendous advantage. Legal is more distant, but there's a clear scale of how much is on the line. When you review a contract, it's pretty clear what’s at stake if legal work is botched. That's my main takeaway: if you care about money, you need to be as close to it as possible. At the same skill level, dealing with user security or financial transaction security won't pay the same.
- intellectronica 2y agoSame but 25 years in the future: "How I made millions, enjoyed unlimited prestige and an easy life as a fake AI existential risk researcher"
- gred 2y agoMaybe AI risk is also higher in Asia and South Africa, and for the same reasons.
- PaulKeeble 2y agoI felt a lot of relief on the morning of 1st when everything I had done was working perfectly. All the test showed that had it not been fixed there was a lot of data corruption. I have been through another one of these where one part of a company changed their year entry from 20XX to just XX to save the people entering it time and multiple systems did not defend against this and suddenly started calculating all intervening years from the time of jesus up to the present day! Its was catastrophic, that simple changed caused several days of disaster recovery but months of defensive programming work as well. Date/time errors can be devastating to business.
- ryandrake 2y agoStupefying that after Y2K, a company is willing to deliberately make this mistake to save two keystrokes. They deserve whatever bad will come to them in 2100.
- mlyle 2y agoIf I save a little bit of work now, my life is better. In the unlikely event that the system is still used in 76 years, it will not be my problem. I'm generally against rolling problems to future generations, but taking risks with a minuscule risk of going somewhat badly that may not even be within my children's lifetimes is not a core concern.
- freddydumont 2y agoThe article is less about Y2K itself than it is about the absurdity of work in the corporate consulting world. It’s a good read. I wasn’t there for the play-doh management fad but I sure experienced capital A Agile and honestly can’t tell which is more infantile. In a sense, the corporate environment of constant indefinite emergency described in the article is the same as arbitrary deadlines and non-stop “sprints”.
- throw0101d 2y agoNext up: * https://en.wikipedia.org/wiki/Year_2038_problem https://en.wikipedia.org/wiki/Year_2038_problem
- DennisL123 2y agoFeels very relatable. A couple of years after Y2K I was asked by the employer at the time to join an multi-billion internal project that was run almost exclusively by contractors. I think the task was to convert a Fortran monolith into Java, but after 20+ years it could also been Cobol. The biggest contingent of contractors came from a company of the AA universe that has survived the Enron scandal. My task was to advise on how to interface with a certain internal system. Easy job. The amount of actual code written was minimal and theses folks were big on generating class scaffolding from UML paintings. Funnily, there was a constant rotation of contractors and they didn‘t realize I was internal. So, I was treated by them as one of their own. And it was six weeks of education that you can’t get in university or business school. I learned the art of being billable which is miles away from doing any work. Matter of fact the hour didn’t have 60 minutes but a hundred. And whatever you faked doing, you did it with double digit precision. You documented that you documented someones proposed, ie. documented, code change that day. Two minutes spent, 1.89 hours documented. Yes, Github and stuff would only come the following decade. We are talking word documents here. Being billable meant that people would propose changes and retract the proposal with another one proposal. At least, the amount of side effects was limited. I also learned the art of fake process. The contractors didn‘t necessarily know what they were doing. But they knew of doing things. So, lots of meetings were happening and random „specialists“ and „experts“ were flown around the planet to delight meetings with stuff they knew of. Having these people disseminate some talking points from recycled slide decks was .. uhm .. fashionable. Third was the art of faking yourself. I vividly remember the guy coming in from Tuesday to Thursday who would bring and arrange the same set if golf balls at his desk. I must have asked him if he played or something. In the end it turned out some important dude made him caddy for an offsite golf event of some partners. And he picked up the balls that were lying around the course. Some consider that a big nono. But apparently it gave some status since every thought the guy had played at said offsite. Highlights from the weeks being embedded with the contractors include a contractor-only dinner. No idea anymore how I managed to be there but some partner gave a rousing speech how they were at the fore front of innovation with this project. And that everyone frenetically clapped at the end. Memory has that the red wine was good, the food less so. Another highlight was an educative session by one of the flown in experts on what a FIFO queue was and how that aided in-order processing of arriving events. Frenetic clapping ensued. Now this is all 25‘ish years ago and perhaps memories are more pointy than reality was. What is certain though is that the number of lines shipped into production was zero. Zilch. And that was not because someone realized all of it was fake. It was because the company went out of business eventually and was bought, sold, merged for its customer base and not its systems.
- nycdotnet 2y agoThe 2038 bug is less than 14 years away at this point. There is an astonishingly greater amount of software out there compared with 24 years ago. I don’t want to be a doomsayer but it’s probably time to keep this in mind anytime you implement an epoch going forward.
- marcosdumay 2y agoAlmost all software is 64 bits nowadays, and avoids the problem entirely. But "almost all" is not "all", and won't be until there. It will certainly be interesting, as stuff will fail in a completely different way from Y2K.
- teractiveodular 2y agoThe problem is not so much OS-level support, but all the legacy databases etc storing 32-bit timestamps.
- marcosdumay 2y agoOh, yeah, there are protocols, file formats, old devices, all kinds of interesting things. But more importantly, differently from the last time, they are very different from each other, so much that it's hard to even anticipate what may break. I imagine a couple of days with the internet misbehaving everywhere is a safe bet.
- mrpippy 2y agoEven talking about software running on servers, I think there’s more 32-bit software than you assume. But my real worry is embedded systems, where very little is 64-bit. Almost every embedded Linux system, IoT crapware, Android anything. Almost none of it will be able to keep time after 2038.
- dsv3099i 2y agoOn the other hand, pretty much anything manufactured after the year 2000 only lasts like 5 years...
- aftbit 2y ago>and an industrial blender at a cattle-culling facility in Alberta whose whirl wouldn’t cease even when unplugged from a power source. What? We discovered a perpetual motion machine at Y2K and I never heard of it?
- aj7 2y agoRemarkably, Twitter had fake jobs for most of its history. Any new Stanford graduate in any field could have one.
- some1else 2y agoIt appears that the author was indeed not too closely familiar with the premise of the Y2K bug, as they mention the change "from 19 to 20" ... the Y2K Bug, and it prophesied that on January 1, 2000, computers the world over would be unable to process the thousandth-digit change from 19 to 20 as 1999 rolled into 2000 and would crash ... That wouldn't be problematic, since the numbers don't loop around (like when going from 99 to 00).
- le-mark 2y agoA lot of these systems stored the year as two digits. So 19 to 20 wasn’t the problem. The problem was mainframe based systems are/were almost entirely based on fixed length data representations; cobol copybooks, tape and dasd datasets (ie files). Expanding all those from two bytes to four was a lot of work and risk is some organizations.
- deleted 2y ago[deleted]
- ChrisArchitect 2y agoAs of today: 2038 Epochalypse countdown: 13 years, 4 months, 19 days, 7 minutes, 13 seconds
- ChrisArchitect 2y agoA bit perplexing that the author after all that time thinking/working on Y2K isn't really clear on what the bug was. Nor that under all the spreadsheet filling, meetingnote-taking etc there was some IT deckhands running around updating PC BIOSes and making sure software updates were in place so ppl could keep doing their daily office work when they got back to the office on Jan...3rd.
- SturgeonsLaw 2y agoIt's not surprising at all that some corporate analyst doesn't know shit about the technical domain. I see it all the time in cybersecurity, there are two types: the hackers who understand the different layers of technology, how they interact, how they can be broken and how they can be fixed, and the checklist monkeys who don't even understand the questions they're asking.
- darkwater 2y agoUnfortunately in cyber security the latters vastly outnumber the firsts.
- roca 2y agoThere is a very powerful myth taking hold that the Y2K problem wasn't real, but some kind of false alarm or scam. It's very strange and scary. It's not just isolated people getting it wrong, I see it popping up all over the place. We really need to push back on it.
- istultus 2y agoI can't bring myself to read this monolith because the two premises at the top are wrong: 1. Y2K was a real phenomenon that needed fixing in various aspects, and 2. fraudulence is not a problem of "capitalism" - it's a problem of humanity. Hell, the biggest quote used to explain the Soviet economy was "they pretended to pay us and we pretended to work".
- coding123 2y agoA lot of IT jobs are fake. Moving numbers and data around so that, in the end, someone sees a graph to continue to make bad decisions anyway.
- JSDevOps 2y agoThis is true. IT project managers that don’t know the difference between Jenkins and AWS are the classic examples.
- JoeAltmaier 2y agoCute My sister's department reviewed every line of code in every product for date/time issues, and corrected them. But she was probably anomalous, by all the anecdotes. She ran a tight ship, and did things that actually needed to be done.
- Aurornis 2y ago> My interview consisted of about twelve minutes with a laconic, mustachioed, middle-aged Arthur Andersen manager named Dick. (One of the services Andersen had been asked to provide was to help hire the Conglomerate’s Y2K team.) “On a scale of one to ten, what’s your knowledge of computer software?” he began. I paused for a moment, unsure of whether our interview would include a demonstrative component, as had so many previous interviews for jobs I had not gotten. But his office was empty. I couldn’t see how he would test me. I said eight. On a private forum I'm part of there was an engineer who ascended into upper management at a startup. He had an entire thesis that modern tech interviews were bullshit and could be replaced with short conversations and asking candidates to self-rate their abilities. He posted long and confident writings about how he was going to save his company so much time and attract the best talent by having the shortest interviews and trusting candidates self-ratings of their abilities. He disappeared for a long time until one day he came back and wrote a post-mortem about his hiring experiment. The quality of their new hires had collapsed. It was so bad that some of their previous top employees were quitting because they were tired of all of the unqualified people joining the company. As he learned, if candidates sense that their interviewers aren't going to examine their claims too closely, many of them will inflate their claims as much as they think they can get away with. In hiring, it only takes one candidate grossly exaggerating their experience and abilities to push the truly qualified candidates into 2nd place (aka not getting the job). We all like to think that we can separate the liars from the truth tellers, but when you're trying to do it in extremely short interviews with questions going both ways, there isn't much time to deep dive.
- datavirtue 2y agoYou need to slow the hiring process significantly to slightly decrease the chances of getting burned. When you are trying to scale up this is very painful. Hence, the common discussion about the problems that occur in a company experiencing rapid growth.
- deleted 2y ago[deleted]
- fleeno 2y agoI spent so much time updating IRIX and Ultrix systems for Y2K... And it was not fun, but now I play with those systems for fun. So I guess I'm weird!
- billforsternz 2y agoOccasionally you still see mentions of "Y2K Compliance" on websites (generally low traffic legacy websites for sleepy businesses that still happily tick over in some obscure niche). I get nostalgic every time.
- JSDevOps 2y agoLots of UK contractors absolutely made bank on this, I’m assuming the smart ones will make bank again in 2037 but most will have retired by then!
- andromaton 2y agoLot of things would have broken that didn't because we fixed them before they broke. The ones that we missed, broke, and we had to fix them while down. It was no fun fixing them before 1/1/2000 and even less fun fixing them after.
- theodpHN 2y agoBad as they could be back in the day, what would enterprise-wide Y2K remediation projects have looked like with Agile, Jira, Cloud, DevOps, Open-Source packages/dependencies, and today's compliance/risk/audit requirements?
- 486sx33 2y agoThank you for posting this, I loved it!
- deleted 2y ago[deleted]
- MELEKE 2y ago[dead]