The Effort Didn't Disappear — It Changed Shape
AI removed the typing, not the skill. Getting to the first 60% is easy now, so the last 40% is the only part anyone notices.
Zain Wania4 min read
There's a kind of product showing up everywhere now, and you can recognize it before you can say what's wrong with it. The landing page is clean and says nothing. The app works and solves a problem nobody has. The design is polished the way a stock template is polished: technically correct and empty. It was made in a weekend, and you can tell.
AI made it possible to go from an idea to something faster than ever. But something isn't a product, and the distance between the two is growing.
Typing was never the hard part
The misconception I keep running into is that AI removed the need for skill. What it removed was the need for typing.
Knowing the syntax for a React component was never the bottleneck. The work was knowing why state should be split a certain way, when a component is doing too much, and which abstraction will hurt you in six months. The code on screen was just the output of that thinking. AI can produce the code. It can't do the thinking for you.
Design is the same. AI will give you a layout in seconds. Knowing that users will miss your call to action because the visual hierarchy is fighting itself comes from reps: shipping things and watching real people use them.
You don't need six books anymore. You still need to learn.
The old route into building things was a grind: a seven-hour YouTube tutorial, five Udemy courses, three Stack Overflow threads from 2014, and a book that was out of date by the time it was printed. All of that just to get started.
AI really did change this. You can scaffold a project, generate the boilerplate, and get past a syntax error in seconds instead of an afternoon. The barrier to entry dropped, more people can build, and more ideas get made. That's a good thing.
Somewhere along the way, though, "lower barrier" got read as "no barrier." People skipped the learning and went straight to shipping, and what they shipped was functional and forgettable.
The learning was never only about being able to write code. It was how you developed taste and judgment, and a feel for what users need as opposed to what sounds great at 2am. You can shortcut the mechanics. You can't shortcut the judgment.
Experience still compounds
AI multiplies what you already have, and a multiplier is only as good as the number it's multiplying.
Take a senior engineer who understands system design, has been burned by bad abstractions, and knows what simple actually means. Give them AI and they get alarmingly fast without losing quality. They hand off the tedious parts and spend the time they save on architecture, edge cases, and the small decisions that separate software that works from software people love.
Give the same tools to a beginner and they ship faster too, often in the wrong direction. They generate code they can't debug and features they can't extend, and they pile up technical debt at a pace that used to take a whole team months.
The difference between those two outcomes is whether someone did the learning or skipped it.
The last 40% is the product
This part is counterintuitive. AI was supposed to close the gap between idea and product, and in one sense it did. In a more important sense it widened it.
Everyone gets the first 60% now. Scaffolding, boilerplate, and the MVP shell are table stakes. The remaining 40% is where the product lives: the polish, the coherence, and the decisions that make it feel intentional. That 40% still takes what it always took, which is skill, taste, experience, and effort with no shortcut.
More people than ever can get to almost done, and fewer seem to push past it.
The effort changed shape
I'm not arguing against AI. I use it constantly, and it's the best thing to happen to my workflow in years. I use it the way a carpenter uses a nail gun, to go faster at work I already know how to do. You wouldn't hand a nail gun to someone who can't find the studs and expect a house.
Typing every character is worth less now, and that's fine. Knowing which characters to type, why, and how they fit into a system that has to hold together is worth as much as ever, probably more. When anyone can produce output, what sets you apart is whether your output is any good.
The effort didn't disappear. It changed shape. The people who use AI to extend their skills rather than replace them are the ones building things worth using.
Everyone else is just generating.