> You bought a laptop or desktop with an operating system, and it did what it said on the tin: it ran programs and stored files.

I feel like people may be viewing the past with rose colored glasses. Computing in the 90s meant hitting ctrl-s every 5 seconds because you never knew when the application you were using was going to crash. Most things didn't "just work", but required extensive tweaking to configure your ram, sound card... to work at all.

I remember when the computer crashed and the user hadn't saved recently, we blamed the user.

This is not just the past. I still have headaches configuring my video card to work with the right CUDA drivers, etc.

The tower of abstractions we're building has reached a height that actually makes everything more fragile, even if the individual pieces are more robust.

> Computing in the 90s meant hitting ctrl-s every 5 seconds because you never knew when the application you were using was going to crash.

That was in the Windows world. Maybe in the Mac world too?

No so much in the *nix world.

Windows seems to have improved its (crash) reliability since then though, which I suppose is nice. :)

Manually editing config files thanks to an obscure thread so that your printer can actually be recognized by the OS

Wait, I literally still hit Ctrl-S constantly, usually a few times in a row.

Have people outgrown this unnecessary habit? Haha

And then having to learn ctrl-q the minute you started working in the shell..

Muscle memory is a bitch!

lol be honest that lunacy was unique to Microsoft, never had to do that with FrameMaker on SunOS

Still though -- once you got a workflow, no matter how terrible, it strongly tended to continue to work that way, and it was still much easier to diagnose, fix, and just generally not have unexpected behavior.

This is the issue; agents introduce more unexpected behavior, at least for now.

My gut is that always on "agents who can do things unexpectedly" are a dead-end, but what AI can do is get you to a nice AND predictable "workflow" easier.

e.g. for now I don't like AI for dealing with my info, but I love AI helping me make more and better bash scripts, that deal with my info.

I don't know what computers you were using.

I had occasional crashes, sure, but unless you had some very dodgy computers, it seems like you're overcorrecting for those supposed rose-colored glasses.

I never knew anyone in the '90s who was constantly living in fear of their programs crashing and losing their work.

alot of software engineering, especially in complex systems, is still just tweaking retries, alarms, edge cases etc. it might take 3 days to even figure out what went wrong

Hmm ... no?

I used computers back then and many things just worked fine. I found Windows XP way more predictable and stable than any of its successors.

Quality issues are a different vertical within the space of software/user misalignment. The sort of issue the author talks about is more like the malware of the 90-00s era: the software deliberately does something to screw the user.

> Computing in the 90s meant hitting ctrl-s every 5 seconds because you never knew when the application you were using was going to crash.

THIS.

I lost so much work in the 90s and 00s. I was a kid, so I had patience and it didn't cost me any money. I can't imagine people losing actual work presentations or projects.

Every piece of software was like this. It was either the app crashing or Windows crashing. I lost Flash projects, websites, PHP code.

Sometimes software would write a blank buffer to file too, so you needed copies.

Version control was one of my favorite discoveries. I clung to SVN for the few years after I found it.

My final major loss was when Open Office on Ubuntu deleted my 30 page undergrad biochem thesis I'd spent a month on. I've never used it since.