Renaissance polymath — artist, inventor, scientist — and an enduring inspiration for curiosity and cross-disciplinary thinking.
Leonardo da Vinci was a 15th-century Florentine artist, scientist, engineer, and anatomist whose curiosity refused to stay inside any single discipline. He is the closest thing history has to a proof of concept for what a human mind can achieve when it treats every field as connected.
I keep returning to Leonardo not for the myth — the genius, the Mona Lisa, the flying machines — but for the method. He didn't pick a lane. He saw painting as applied physics, anatomy as applied philosophy, engineering as applied art. That synthesis is the thing.
Leonardo left roughly 7,000 pages of notes across dozens of notebooks. On a single page you might find studies of water turbulence next to sketches of facial expressions next to calculations for a siege engine. He wasn't scattered — he was tracing the same underlying patterns across different domains.
This is what I find most useful about him as a model: not that he was good at many things, but that he believed understanding one domain deeply illuminates every other domain. Physics informs composition. Anatomy informs architecture. The skill compounds.
As a software engineer, I work at the intersection of multiple fields constantly — product thinking, systems design, visual interfaces, human psychology. The engineers I most respect aren't specialists who happen to code; they're people who bring something from outside the discipline into it.
Leonardo is the archetype for that. His paintings are accurate because he understood light as physics. His inventions were elegant because he studied proportion as art. Cross-disciplinary thinking wasn't a hobby for him — it was his competitive advantage.
I try to apply the same logic. My interest in transhumanism, cognitive science, and emerging interfaces isn't separate from my engineering work — it feeds directly into how I design systems.
A few things stand out in how Leonardo actually operated day to day:
That last point is a productive tension for me. I practice kaizen — continuous, incremental improvement — but Leonardo reminds me that some work requires depth over velocity.
What actually transfers from a 15th-century Florentine to modern software engineering? More than you'd think:
Leonardo died with most of his scientific writings unpublished and many projects incomplete. For a long time this was framed as failure — the distracted genius who couldn't finish things.
I read it differently. He was mapping territory faster than he could build on it. The notebooks weren't abandoned projects; they were infrastructure for the future. Centuries later, engineers found his designs for helicopters, solar power concentrators, and armored vehicles — and built them.
That's a version of long-term thinking I find genuinely inspiring: doing work whose value isn't fully realized in your own lifetime. My work in emerging technology and deep work feels like that sometimes — building foundations whose payoff is years or decades away.
The question Leonardo leaves me with: What are you curious enough about to explore for its own sake, regardless of whether it ever produces a finished product?