The Slow Death of the Power User
hubie writes:
The Slow Death of the Power User:
There's a certain kind of person who's becoming extinct. You've probably met one. Maybe you are one. Someone who actually understood the tools they used. Someone who could sit down at an unfamiliar system, poke at it for twenty minutes, and have a working mental model of what it was doing and why. Someone who read error messages instead of dismissing them. Someone who, when something broke, treated it as a puzzle rather than a betrayal.
That person is dying off. And nobody in the industry seems to care. In fact, most of them are actively celebrating the funeral while billing it as progress.
This isn't an accident. This is the result of two decades of deliberate, calculated effort by the largest technology companies on earth to turn users into consumers, instruments into appliances, and technical literacy into a niche hobby for weirdos. They succeeded beyond their wildest expectations. Congratulations to everyone involved. You've built a generation that can't extract a zip file without a dedicated app and calls it innovation.
The average person who grew up with smartphones has a fundamentally broken mental model of computing. Not broken in the sense that they can't operate their devices - they can, with terrifying efficiency. Broken in the sense that their understanding stops at the glass. They know how to use apps. They do not know what apps are. They know files exist somewhere, in the cloud maybe, or possibly inside the app itself - the distinction isn't clear to them and they've never needed it to be.
[...] Ask a twenty-two-year-old to connect to a remote server via SSH. Ask them to explain what DNS is at a conceptual level. Ask them to tell you the difference between their router's public IP and the local IP of their laptop. Ask them to open a terminal and list the contents of a directory. These are not advanced topics. Twenty years ago these were things you learned in the first week of any serious engagement with computers. Today they're exotic knowledge that even a lot of working software developers don't have, because you can go a long way in modern development without ever leaving the managed abstractions your platform provides.
And that's the real damage. It's not just end users who don't know this stuff. It's developers. People who write software for a living who've never had to think about what happens between their API call and the response. Who've never had to debug something at the network layer. Who've never had to read a full stack trace and understand every frame of it. Because the frameworks handle all of that, and the frameworks are good enough, and figuring out how things actually work is optional.
[...] The smartphone didn't just shift computing to a smaller screen. It replaced a computing paradigm - one built on ownership, modification, and composability - with a consumption paradigm built on managed access, curated experience, and dependency. And it did so with the full, deliberate, enthusiastic participation of every major platform vendor.
[...] All of this was sold as a feature. "It just works." Safety. Privacy. User experience. What it actually was, was control - Apple's control over what you could do with hardware you supposedly bought. And the genius move, the move that should make any serious observer furious, was convincing users that this control was being exercised on their behalf.
[...] Android played the same game with better PR. Google launched Android as an open platform, and for a few years it genuinely was. You could sideload APKs trivially. You could root your device and replace the entire OS. Manufacturers shipped custom builds. The ecosystem was messy and fragmented and occasionally awful and genuinely interesting. Then, gradually, systematically, Google started closing it down.
[...] The users who grew up on these platforms don't know what they're missing. They've never used a system where they were genuinely in control. The idea that you should be able to run arbitrary code on hardware you paid for is foreign to them - not rejected, but simply absent as a concept. They'll defend the restrictions without prompting because they've internalized the vendor's framing so thoroughly that they experience the cage as comfortable. "I don't want to root my phone, that sounds scary." Cool. You've successfully trained yourself to be afraid of ownership. The platform vendors are proud of you.
Technology culture used to celebrate technical competence. Not as gatekeeping, not as elitism - as genuine, infectious enthusiasm for understanding how systems worked. The BBS scene in the eighties ran on self-taught systems operators who understood their hardware and their network protocols well enough to build infrastructure that had never existed before. The early web had a "view source" ethos: you saw something interesting, you looked at how it was built, you learned from it, you made something of your own. [...]
These were not professional circles. You didn't need a CS degree. You needed curiosity and stubbornness and a tolerance for reading things that were too long and trying things that didn't work on the first ten attempts. The culture valued that and passed it down. Kids learned by watching, by lurking in forums, by getting their stupid questions answered by people who then expected them to answer someone else's stupid questions eventually. The knowledge propagated because the culture treated knowledge as worth propagating.
Read more of this story at SoylentNews.