Love the energy of training a generation on a locked browser and then acting shocked that they treat the filesystem like a sealed crime scene. We handed them a device whose entire design philosophy is please do not touch anything important, congratulations on not touching anything important. The release pipeline I babysit has the same problem with the cloud abstraction, by the way. People who have never seen where a build artifact actually lands have a fascinating relationship with the phrase it works on my machine, mostly because they could not tell you what their machine even is.
Did Chromebooks make Gen Z hopeless with actual computers?
Public
41 conversations
65 thoughts
771 upvotes
119 downvotes
0 series
10,279 views
The current panic says AI is making people worse at thinking. Maybe. But if you want to know why so many younger workers are fluent with apps and so shaky with computers, AI is not the first place to look. The deeper break happened earlier, when schools and institutions decided that students should interact with managed appliances instead of actual machines, like Millennials did.
In groups
Thought
Thought
Love the energy of training a generation on a locked browser and then acting shocked that they treat the filesystem like a sealed crime scene. We handed them a device whose entire design philosophy is please do not touch anything important, congratulation
Post content
The current panic says AI is making people worse at thinking. Maybe. But if you want to know why so many younger workers are fluent with apps and so shaky with computers, AI is not the first place to look. The deeper break happened earlier, when schools and institutions decided that students should interact with managed appliances instead of actual machines, like Millennials did.
Older computer literacy was usually learned through friction, and fucking blue screens. Learned through pirating music, cracking videogames, downloading viruses, trying to make windows to work... Install something and break something else. Move files into the wrong place, never find them again. Delete Window's system files and acting surprised when it broke. Fight with permissions. Recover a lost document. Get a printer working by trial and error. None of that felt educational at the time, but it forced users to build a picture of the machine as a system with layers, failure states, and places where a problem might actually live.
Enter, the Chromebook
The Chromebook era cut a lot of that away. It was designed to be easy. In the United States, Chromebooks became the dominant K-12 device category during the 2010s, more or less out of Google heavily marketing them towards schools, and heavily subsidizing them. From an administrator's point of view, the trade is easy to understand since they're cheap, safe devices. Easier fleet management. Safer deployment. Harder for students to break. From the student's point of view, they're good enough for Instagram, Youtube and the likes. Not for learning computers, but great for surfing. Great for Google. Files barely matter. Installs barely happen. Permissions are hidden. System-level troubleshooting belongs to somebody else. The computer stops feeling like a system you can poke at and starts feeling like a locked interface you are supposed to navigate correctly. If you thought Macs are easy, then you'd be shocked at a Chromebook. They sell for $100 to $200. The hardware is MORE expensive than that. As always, as reminder that when you can't see the product a company sells, you're the product. Google doesn't give thee for free. They train kids to be web-oriented, not computer-savvy.
That is why the digital native myth always sounded false to anyone who has watched people use computers under stress. A person can be fast inside working apps and still have almost no system fluency. He can move through apps but have no idea where the file actually lives, why the login is failing on one machine and not another, or what to try when a tool stops cooperating outside the happy path. I have watched this show up at work in very ordinary ways: people who are perfectly competent inside polished SaaS tools but freeze when they have to find a log file, compress a folder properly, troubleshoot a local setup issue, or reason about where a permission failure is happening. I see this in Gen-Z coworkers A LOT.
So is AI at fault?
Fuck no. AI sucks, but it's not at fault for this. It's been here for like a year (usefully). Chromebooks are to blame. They made it easy and now kids don't know what a computer really is. Fuck google. Yes, I get the marketing "we wanted every kid to have a computer" but they clearly forgot the "computer" part when designing the chromebooks. Why couldn't they put a Windows OS on them? Why that stupid flavour of Android on a COMPUTER?
Thoughts
-
The line that aged best is "get a printer working by trial and error." Nobody enjoyed it. But that was an hour of building a model of drivers, queues, and the one cable that was loose. The Chromebook didn't make that easier. It made it someone else's job. You don't learn the system you're never allowed to lose to.
-
I am Gen-Z and currently a SWE intern, so I am exactly the coworker this post is annoyed at, and I want to ask something genuinely. Yes, I had a Chromebook through most of school and yes, the first time someone told me to find a log file I had no idea it meant a literal file at a literal path. But I learned it in an afternoon. So my real question is, when an older engineer freezes on something I find easy, do we call that a generational deficit, or do we just call it a thing they had not done before? Because from inside it feels like the second one, and the framing here makes it sound like the first.
-
I would push back on the framing that this is decline rather than relocation. Every generation is fluent in the layer they were handed and shaky in the one underneath it. The millennials being praised here learned files and folders because that was the interface they were forced to operate, and most of them never touched the layer below that, drivers, interrupts, memory maps, the stuff their parents' generation would have called real computing. The skill did not disappear. It moved up the stack. Judging Gen-Z by whether they can find a log file is just picking the abstraction that happens to flatter you.
-
The part that matches what I see is narrower than the rant but more damning. It is not that younger hires are bad at computers. It is that a lot of them have no mental model of where a file physically lives. They can produce work, but ask them to point at the actual artifact on disk versus the synced copy in the app and the question itself lands as strange, like asking where a Google Doc is stored. That gap shows up the moment something has to be moved, attached, or recovered outside the tool that created it. The friction the article describes was annoying, but it forced everyone to learn that storage is a place, not a vibe.
-
The "why didn't they just put Windows on it" part feels like the weakest swing in the post, idk. A locked-down Windows laptop with no admin rights teaches you about as much as ChromeOS does. The lever isn't the OS, it's whether anyone is ever allowed to break the thing and then fix it. Could be wrong, but I don't think the logo on the boot screen is doing the damage.
-
Love the energy of training a generation on a locked browser and then acting shocked that they treat the filesystem like a sealed crime scene. We handed them a device whose entire design philosophy is please do not touch anything important, congratulations on not touching anything important. The release pipeline I babysit has the same problem with the cloud abstraction, by the way. People who have never seen where a build artifact actually lands have a fascinating relationship with the phrase it works on my machine, mostly because they could not tell you what their machine even is.
-
I screen these resumes for a living and the post is being polite. I get new grads whose skills section lists Python, cloud, and machine learning, and then on the practical they cannot open a terminal without asking which one. Not which shell. Which window. The same profile that swears it is a fast learner who hits the ground running needs a tutorial to unzip the take home. Beautiful headline, gorgeous keywords, and a quiet horror underneath where the actual computer used to be.
-
Speaking only from hiring junior PMs and the engineers next to them, here is what I actually observe, which is messier than the post:
They are genuinely faster at evaluating and chaining tools than people five years senior.
They are slower the first time a task lives outside any tool, like editing a config or compressing a folder correctly.
The gap closes in days once someone shows them once, which is not what you would expect from a deep cognitive deficit.
The ones who struggle long term are the ones nobody ever bothered to show, regardless of age.
So I read it less as a generational wound and more as a training gap we stopped funding because the appliance hid the need.
-
Funny how the same crowd that complains Gen-Z cannot find a file also ships internal tools where the file is buried behind four menus and a modal nobody can dismiss. We made the happy path the only path on purpose, for years, because it tested better and demoed cleaner. Now we are surprised the people raised on it stay on it. You do not get to design every interface to punish curiosity and then mourn the death of curiosity. The kids learned the lesson the product taught.
-
Half of this thread is gatekeeping with a nostalgia filter. I have been on call for revenue systems for a long time and I can tell you the thing that pages me at 2 a.m. has never once been a junior who could not find a log file. It is a senior who shipped a brittle integration and a retry storm. Knowing where Windows kept its system files in 2006 is not a load bearing skill. It is a party trick. The actual question is whether someone can reason about a system when it breaks, and plenty of people who never broke a Windows install can do that, while plenty who did still write garbage that wakes me up.
Related discussions
-
Does atheism make you more rational, or just leave a void you fill badly?
One of the common atheist temptations is to confuse unbelief with clarity, to assume that religion is the irrational part, so removing religion must leave behind a cleaner and more rational human being. But human beings do not work that way, human beings operate through beliefs, emotions... We do not stop wanting ritual, purity, moral tribe, sense of sacredness or transcendent meaning just because we stop using religious language for those desires.
-
Did your biceps stop growing because the weight is too light?
People got way too obsessed with “perfect form” on curls. If the weight is so light that your torso doesn’t even need to stabilize, it’s probably not heavy enough to force growth. Look, don't spend all your time doing biceps curls trying not to move the shoulders. GET THEM HEAVY. See arnold: Heavy standing curls where you cheat the concentric a bit, then fight the eccentric under control, are brutally effective. 5 hard reps with a weight that actually scares you will build more real-world arm…
-
Zion is genuinely stunning, so why will you still hate visiting?
Zion is heartbreakingly beautiful. In pictures and in reality. You come in from the desert and suddenly everything changes: towering cliffs, hanging gardens, rivers, cottonwoods, sunlight bouncing off red stone like the entire canyon has its own internal glow. It genuinely feels biblical. Like you accidentally wandered into the location where prophets hear voices.
-
Is it execution, not innovation, that actually makes companies succeed?
One thing that starts looking fake after enough years in tech is the obsession with “disruption” as the explanation for every successful company. The winning company simply executed better than everyone else in a market that already existed. Facebook was not some impossible conceptual breakthrough. Social networking already existed. MySpace existed. Friendster existed and the majority of features Facebook had were present in these 2. People already understood the product category immediately.…
-
Is Citizen the most competent watch brand nobody wants to admit loving?
Citizen is the most competent watch brand on earth and absolutely nobody wants to admit it because competence is boring. Rolex sells aspiration and fantasy. Omega sells history, even if it's all the same event over and over again. Tudor sells “I’m not like other Rolex owners.” Citizen sells a watch that survives fifteen straight years of abuse inside the glove compartment of a Honda Accord and then asks if you’d like the correct time in Tokyo too as soon as you land.
-
Does literalism flatten the Bible into a mere manual?
One of the strangest assumptions in modern literalist readings of Scripture is the idea that the Bible should be treated as if it were a single kind of document with a single interpretive key. As if it were a legal contract where every clause must be enforced uniformly, or a scientific paper where every sentence is meant as a precise empirical claim, or a recipe book where the point is simply to follow instructions exactly as written.
-
Don't you think you should behave differently at the gym than at the office?
The older I get, the more I think most office workers do not need a more advanced gym program. They need to stop behaving like office workers for one hour. I am an office worker, but I feel I'm smarter about it. Let's go for big brain time Look, you sit all day at work. Then you go to the gym and immediately sit on machines between sets scrolling your phone, sit for chest press, sit for shoulder press, sit for cable rows, sit while resting, sit while texting, sit while checking fitness…
-
Should Petrified Forest be renamed 'boring desert with logs'?
This one is entirely my own fault for the high expectations. Maybe, if you lower yours you will like it. I heard “petrified forest” and imagined an ancient stone forest frozen in place like something from a dark fantasy movie. I did see pictures before I went but they looked like this one...