Will AI replace you?

Almost everyone is using AI now. Among university students the figure reached 92% this year, up from 66% the year before, and among professional developers it is 84%, with just over half of them reaching for it every single day. So access to AI isn't an advantage anymore, because the person next to you in the interview pool has exactly the same access you do. The only variable left is whether you use it in a way that makes you sharper or a way that quietly makes you worse, and in my opinion that single difference is about to decide who gets hired and who spends a year wondering why they cannot.

So will it actually replace you? No. AI won't replace engineers (at least not yet), but it will replace the people whose only real skill is doing what the model already does for free. If your value is producing the standard solution to a known problem, you are no longer competing with the other candidates, you are competing with a tool that does your one trick instantly and never asks for a salary, and that is a competition you lose by definition. What survives is the part the model cannot do for you: deciding what to build, reasoning through something genuinely unfamiliar, and noticing when the confident answer on the screen is quietly wrong. Training yourself to be a slower version of the thing that is already faster than you is the losing move, and yet it is exactly what most people are now doing.

Watch how people actually use these tools and they sort into three groups of very unequal size. The first and largest treats it as a crutch, so the moment a problem resists them they paste it in, take the answer, and move on feeling productive, having skipped the precise struggle the exercise existed to create. This is the group to worry about, because the damage is now measured: in a controlled study from Anthropic, developers who leaned on AI to learn a new library scored 17% lower on comprehension afterward, 50% against 67% for the people who worked through it themselves, and the gap was widest on debugging, which is the skill interviews lean on hardest. They're eroding the exact ability they showed up to build, and because the code runs, nothing tells them it's happening.

The second group, much smaller, refuses to touch it at all, usually out of some mixture of principle and fear, and I get the instinct, but it's still a mistake. Used well, this is the biggest productivity tool the field has had in a generation, and refusing it outright hands real speed to the people who learned to use it. The third group uses it correctly, and it's small enough to be a rounding error. They never hand it the part that builds the skill, and they lean on it hard for everything else.

Don't assume you're in the third group. METR ran a proper randomized controlled trial in 2025 on experienced open-source developers working inside their own repositories, and the ones allowed to use AI took 19% longer to finish, while believing they had worked 20% faster. Strong developers, on their home ground, were slowed down by the tool and couldn't feel it. If correct use is rare even among experts on familiar territory, it is close to nonexistent among students on unfamiliar territory, which describes most people reading this. AI isn't useless; in the right hands on the right task it's enormous. But feeling fast isn't evidence of being fast, and almost everyone trusts that feeling.

The popular story is that AI lifts everyone equally. It doesn't. People who were already strong are the only ones positioned to extract the leverage, because they can tell when the model is right, discard the eighty percent of its output that is mediocre, and spend the saved time on the parts that are genuinely mechanical, so for them it is a real multiplier sitting on top of a real foundation. People who were already struggling get the inverse, because they cannot evaluate what the model hands them, so they accept its mistakes, ship its confident nonsense, and skip the exact reps that would have closed the distance, which means the tool that was supposed to help them catch up instead pushes them further behind. Developer trust in AI accuracy has fallen to 29% from 40% a year earlier, so even heavy users know its output can't be taken at face value, and checking that output is a skill only the already-skilled have. The tool everyone assumed would level the field is doing the opposite: it pays out in proportion to the skill you already brought to it.

Companies can see all of this, often more clearly than the candidates can, and it is the real reason the interview itself has moved. When every applicant can produce a clean solution to a known LeetCode problem, because a model produced it for them, that round stops telling the company anything at all, so they have shifted the test to where a model in the next tab cannot quietly answer on your behalf. Meta and Google have added AI-assisted rounds with deliberately harder problems, Stripe runs its loop on a real production codebase, and roughly 90% of startups now run at least one round built specifically to resist the tool. Companies aren't being cruel or nostalgic. They're doing what you should be doing: they've stopped measuring the skill the machine already has and gone looking for the one it doesn't.

The rule under all the others: know exactly what these models can and can't do yet. Most people never build that map, so they end up either trusting the tool everywhere or distrusting it everywhere, and both are just different ways of letting it run you. The moment you understand its limits exactly, where it is reliable and where it confidently lies, you become the one controlling it instead of the other way around. Using it more won't teach you that. Doing the work yourself, often enough to recognize when the machine is wrong, will.

So the rule is: never let the model do the part that builds the skill, and lean on it for everything else. When you practice, solve the problem yourself first, until you're actually stuck, and only then bring in the model, and when you do, use it to find the hole in your reasoning rather than to replace the reasoning, asking it where your approach breaks instead of asking it for a finished approach. That is the entire design idea behind the AI on WhiteBox, and it is why it behaves differently from a raw ChatGPT window: Tsuki is built to push you back toward your own thinking instead of dropping the solution in your lap, and White Room remembers what you are weak at and keeps steering you back into it rather than around it. Used that way, AI is a tutor that explains the idea you were missing after you've wrestled with it, not an answer key that lets you skip the wrestling.

92% of students are using these tools, the single most common use is having concepts explained to them rather than working those concepts out, and the measured effect of learning this way is worse comprehension, so the median student is using the tool in exactly the way that hollows out the skill interviews are shifting to reward, and feeling productive the whole time. Don't quit the tool, and don't grind blindly without it. Do the reasoning yourself every time, until you've earned the answer, then let AI sharpen what you already understand. I think the split between the few who hold that discipline and the many who don't is going to decide who gets hired, and which side you land on is still your call, for now.