Linus Torvalds, who reduced AI to "90% marketing" in 2024, has just published eight Linux kernel patches written with Claude Code. The detail that matters lies in his method: he reviews each patch and integrates only what his judgment validates. The same day, Satya Nadella asks that a human be able to interrupt any model at any moment, and a health study cited by the Journal du Net measures the flip side of safety: guardrails reduce a medical model's dangerous decisions, at the cost of more human verifications. Three signals, one direction. The value of an AI tool at work now turns on the skill of the person who reviews, corrects and decides.
We are watching a quiet shift inside organisations. Attention has gone to the ability to phrase a request, to "prompt". The real work is moving elsewhere: knowing how to spot the confident error, the invented source, the false shortcut that a model produces with the same assurance as a correct answer. This skill, critical review, can be learned and measured. It separates the engineer who accepts a patch because they understood it from the one who pastes it because it compiles.
For a French organisation, the move to action is clear. Build review into the workflow, not as an option: who validates, on what criteria, with what trace. Train teams to check an AI output the way you review a fast, gifted colleague, useful as long as an expert eye passes behind. Identify the points where a human catches a real error, and reinvest the time saved elsewhere. The announced productivity gains hold only by that link.
Torvalds kept his judgment at the centre. Claude Code speeds up the typing, leaves him the decision. That is the stance that turns a powerful model into reliable work. The organisations that train their people in this review will capture the gain; the others will inherit faster errors.
The Masteria editorial team