1,606 karma · joined April 3, 2010
I'll test this with my cat named Turing this weekend to see if he gives better results.
Those were interesting times to live through.
It took a lot of reflection and was cause for a lot of growth. But now I'm not only mentally happier, I'm taking better care of my body because it finally feels like it's my own.
We started out on mainframes.
Then things moved to the desktop, with some centralized functionality on servers (shared drives, batch jobs).
The processing moved to centralized web servers via the web, SAAS, and the cloud.
Then more moved into the client through React & similar.
And now things are moving back to the server.
Tick. Tock.
These changes are not just arbitrary whims of fashion, though. They're driven by generational improvements in technology and tooling.
I also chip in toward upkeep on my favorite Mastodon instance.
Let's say you bought a 100-baseT network card in 1995. The features were fixed in metal, and so were the bugs. Even if a new revision of the board or ROM came out, you still had the exact same card. If a flaw was found in one of the chips they used, chances are someone would need to program around it. Settings were probably done once using DIP switches and never touched again. You probably never even knew if a new revision came out.
The wifi card you use today is going to boot up in a pretty dumb state. It'll identify itself on the bus and not much else. Your computer's kernel is going to poll every device on the bus to see who's out there. The wifi card driver is going to match the ID of the wifi card to one it knows and then upload firmware. Then the card will need to briefly reboot into the new firmware and identify itself to the driver again. Then the driver is going to configure it.
It may take a couple of seconds for all this to happen, and it needs to happen for almost everything. Even your CPU which booted the machine in the first place might get patched microcode uploaded when the machine boots.
Nothing is just a device anymore, and nothing is just a device driver.
Until that trans person needs to go to the bathroom.
(Given the quality of the video, I'd be inclined to think 1983 rather than 1993)
[1] https://twitter.com/SalHernandez/status/1264320286733697024?...
To be fair, a lot of Jason Scott's audience is people who might choose to use ancient browsers on obsolete platforms.
Some of my wife's friends wanted to read it, so one of them imported the RSS feed into Livejournal and I discovered it one day. Surprise, there were lots of comments on "my" LJ account and people upset I wasn't answering their questions.
That was a lesson to me that owning the place I publish content isn't as important as being where my audience is, at least if I want people to read it. At the time¸ it was Livejournal. Today, it's social media.
There were a lot of two-digit dates out there which would have led to a lot of bugs. Companies put a lot of effort into addressing them so the worst you heard about was a 101 year old man getting baby formula in the mail.
The media over-hyped it, though. There was a market for books and guest interviews on TV news, and plenty of people were willing to step up and preach doom & gloom for a couple bucks: planes were going to fall out of the sky, ATMs would stop working, all traffic lights were going to fail, that sort of thing. It's like there was a pressure to ratchet things up a notch every day so you looked like you were more aware of the tragic impact of this bug than everyone else.
That's the part of the crisis that wasn't real, and it never was.
They were also more expensive than regular binders and the rings weren't lined up with regular folders, so being in the Trapper Keeper ecosystem was a class symbol in my school.
It makes for a positive, productive work environment. And then I'm expected to model the same behavior I want to see from them, so I mean I kind of have to limit myself to 40 hours. You know, for them.