4 ms·
Yeah, there were a couple of real gems in that "article": > It’s possibly a coincidence, but Twitter has just welcomed two new members to its API team today. I
by thaumaturgy 17y ago
Yeah, there were a couple of real gems in that "article":
> It’s possibly a coincidence, but Twitter has just welcomed two new members to its API team today. Is Twitter manning up for the battle?
Right, because as a company, what you really want to do if a big hammer is about to fall on you is immediately hire a couple of new programmers who aren't familiar with your internals at all.
> It’s now past 2 PM and no reports of massive failures yet. Perhaps this really is just like Y2K.
Yep, because there's no such thing as a bunch of programmers who spent a lot of hours fixing code _before_ it broke. (I was one of them.)
- larrywright 17y agoIt always irritates me when people say "Y2K was such a non-event". It was a non-event because a whole lot of people fixed and tested a whole lot of code. If they hadn't, the world would have been a pretty miserable place on 1/1/2000.
- eru 17y agoPerhaps not really miserable, but a lot of things in administration (etc) would not have continued to work. (My grandfather was also one of those fixers.)
- larrywright 17y agoDepends... the code that runs an insurance company is one thing. The embedded computers would likely have been the biggest problem - things that dispense medicine, control the power grid, etc.
- eru 17y agoFew embedded systems depend on the date, do they?
- deleted 17y ago[deleted]
- larrywright 17y agoI don't have first hand experience, but from what I understood, yes. Particularly in monitoring devices: "Shut this off if you haven't received a signal in x minutes". That sort of thing.
- eru 17y agoThanks. Though I imagine that those watchdogs might have more problems with the year 2038.