The Specialist Is Doomed. Leonardo Was Right 500 Years Ago.
Specialization was your advantage for years. Today it's your biggest vulnerability. The 7 principles of Leonardo da Vinci applied to the tech professional in 2026.
TL;DR: Specialization was your advantage for years. Today it's your biggest vulnerability. AI is a better specialist than you — cheaper and without vacation days. What it can't replicate: accumulated judgment, the scars, the ability to connect domains that seem to have nothing to do with each other. Leonardo da Vinci operated exactly this way 500 years ago. In this piece: his 7 principles applied to the tech professional in 2026, a practical resource to multiply your AI outputs, and a data point about humanity you won't be able to shake.
More than 10 years ago I bought a book in Venezuela.
I read it in less than a week, underlined almost everything, kept it, and it's been with me in my personal library ever since. It was one of the few books I brought from my last emigration. A few weeks ago I picked it up again and realized it was never as relevant as it is today.
The book is Think Like Da Vinci by Michael Gelb. And the timing isn't a coincidence.
The Trap We All Fell Into
For years, the system told you one thing: specialize.
Become the SAP expert. The Kubernetes specialist. The Azure architect. The person who knows more about one topic than anyone in the room.
It worked. Specialization was a moat. It protected you.
That was before.
Today AI surpasses the average specialist in almost everything. Writing, analysis, junior code, generic consulting. Not everything, but enough.
AI beats you in accumulated knowledge. It can't beat you in accumulated judgment. The scars that can't be vectorized. And even less in integrating seemingly unrelated domains without historical precedent — what Leonardo did better than anyone.
The specialist who only knows their specialty is the most vulnerable today. Not because they're bad, but because AI is a better specialist — cheaper, faster, and available 24/7.
The question isn't "how do I specialize more?" The question is: "how do I become someone AI can't replace because I integrate what AI can't integrate?"
Leonardo Wasn't a Genius. He Was a System.
Michael Gelb describes Leonardo as someone who perceived the interconnection of all things. His phrase was literal: "everything connects to everything else."
It wasn't magic. It was method.
Da Vinci combined rigorous critical thinking with boundless creativity. He refused to accept knowledge from the "authorities" of his time without empirically testing it — his anatomical dissections are the most radical example of this. He was a painter, engineer, anatomist, hydrologist, musician, cartographer. Not because he had infinite time, but because he understood those disciplines were expressions of the same underlying system.
Da Vinci structured his days with periods of intense work followed by rest to allow new ideas to emerge. He advocated for the balance between effort and recovery.
That should sound familiar to anyone who runs or trains seriously.
Running marathons taught me something that years of code hadn't: recovery isn't inactivity — it's part of the work. Kilometer 35 hurts for everyone. The difference between those who finish and those who don't is what they did in the months before, not in the last five kilometers.
A system, not a sprint.
The 7 Principles of Leonardo and Why They Matter Now More Than Ever
Gelb's book organizes Da Vinci's thinking into seven principles. I reread them today and see they're not Renaissance self-help advice. They're the exact description of what makes a professional impossible to replace in 2026.
1. Curiosità — Do You Ask Questions or Execute?
Gelb recommends always carrying a notebook. Leonardo filled thousands of pages with observations, sketches, and questions — not answers.
AI is the best answer machine that exists. But it only executes on the question you give it. If your question is mediocre, the output is mediocre. The one who knows what to ask orchestrates. The one who doesn't is executed.
Start today: write one genuine question per day about your work. Not a task — a real question you don't know the answer to yet. If you don't want to use a notebook, use Obsidian.
2. Dimostrazione — Judgment Is Built With Scars, Not Courses
Da Vinci rejected secondhand knowledge. He verified everything through direct experience.
In tech this means: it's not enough to know about code (which is nearly free today). You have to have seen the error, debugged it, broken the system in QA, and explained why it happened. That can't be vectorized. That's what AI doesn't have.
Start today: the next time you use AI to solve a problem, force yourself to understand why the solution works. Don't copy the output. Dissect it.
3. Sensazione — You Sharpen Your Senses or You Delegate Them
Da Vinci emphasized sharpening the senses through nature, music, and varied experiences — not as a hobby but as cognitive training.
Going running isn't just cardio. It's the only moment of the day when your neocortex shuts off and your intuition processes without interference. My best decisions came while running, not in front of a screen.
Start today: a walk without headphones, without a podcast, without your phone. Just observe.
4. Sfumato — Can You Tolerate Ambiguity or Do You Need Certainty?
Sfumato is Leonardo's principle for operating in uncertainty without becoming paralyzed. The geniuses knew they couldn't control most things and learned to make decisions anyway.
In tech projects nobody has all the answers from day one. Those who need complete certainty before acting never move forward. Those who make good decisions with incomplete information are the ones who lead.
Start today: identify a decision you've been postponing because "more information is needed." Make it with the 70% you have.
5. Arte/Scienza — Do You Integrate or Fragment?
Da Vinci synthesized logic and imagination in pursuit of "truth, beauty, and goodness." He never separated art from science — he considered them expressions of the same process.
I'm an engineer who writes. A technician who runs marathons. A systems architect who reads philosophy before bed. These aren't separate things — they're the same system looking at itself from different angles. That integration is my moat.
Start today: take something from your technical work and explain it to someone non-technical. If you can't, you don't fully understand it.
6. Corporalità — The Hardware Matters
Da Vinci maintained that the body is the intellect's instrument, not its antagonist. Corporalità was his principle for sustaining the mind with a trained body.
Nineteen marathons aren't a hobby. They're the hardest proof of work I have to falsify. In a world where AI generates code, documents, and analysis in seconds, physical pain is the only thing that can't be faked. The body is the only asset AI can't replicate.
Start today: 30 minutes of real movement — not steps, not a standing desk. Real sweat. It'll change your head.
7. Connessione — Everything Connects, or You Live in Silos
This is the integrating principle. Da Vinci saw the interconnection of everything. Systemic thinking was what separated him from the other geniuses of his era.
SAP connects to the business that connects to the people that connect to the processes. The marathon connects to discipline that connects to pain tolerance that connects to how you handle a migration going sideways. The person who sees those connections leads. The one who lives in their silo executes.
Start today: write three non-obvious connections between your work and something completely different you do in your life. You'll find it leads somewhere.
The Practical Part: How to Improve Your AI Outputs Before You Finish Reading This
Everything above is philosophy. This is action.
The most common problem I see — and that I had myself — is that we ask AI the same thing we used to ask Google: a direct answer to a mediocre question. The output reflects exactly that.
There's a method that Anthropic's own engineers use internally to fix this. It's called "the-interviewer" and it turns Claude into a strategic planner before executing.
The usual flow:
Short prompt → Claude guesses → Output 70% good → You edit for an hour
The flow with the-interviewer:
Prompt → Claude expands into full plan → Asks you 2-3 key questions → You answer → Output 95% ready
Two minutes of planning at the start eliminate an hour of editing at the end. And most importantly: it forces you to think about what you want before executing. That's Dimostrazione applied to AI.
It's not a trick. It's the difference between using AI as copy-paste and using it as you actually orchestrate it.
A Data Point That Left Me Speechless This Week
I saw a graphic on LinkedIn with 2,500 dots. Each dot represents 3.2 million people — nearly the population of Uruguay — all of humanity on a grid. Data from February 2026.
84% of the dots are gray. 6.8 billion people who have never used AI. Not once.
The green ones are the 16% that tried a chatbot at least once. The yellows, barely visible, are the 0.3% that pays $20 a month for an AI tool. And the reds, almost imperceptible: the 0.04% that uses AI for programming.
Your LinkedIn feed makes you believe that everyone shipped an AI agent last Tuesday. That's not the world. That's a bubble of ten thousand people talking among themselves.
The real world is mostly gray.
And here's the data point that matters most to me: if you're a Tech Lead aged 35-50, in a corporation, using AI every day with your own judgment — you're in the 0.04% of humanity. Not because you're a genius. Because you paid attention and acted.
That's exactly what Da Vinci did that his contemporaries didn't: he observed what everyone saw, and drew conclusions nobody else drew.
The seven principles of Leonardo aren't museum philosophy. They're the operating system of the 0.04% that doesn't wait for the wave to arrive — they surf it before it forms.
We're genuinely early. Gray still dominates the chart.
Take advantage of it. Don't fall asleep.
Shall we begin?
Newsletter
In Production
Every Tuesday: what is actually happening with AI inside large enterprises, written by someone implementing it there.