There's a myth in modern education and career advice: you must finish what you start. You must go deep. You must become an expert.
But what if the real magic happens at 85%?
The Curse of Completion
I've built dozens of projects. Learned half a dozen programming languages. Started blogs, YouTube channels, podcasts. Read hundreds of books—finished maybe half.
The productivity gurus call this "shiny object syndrome." The career advisors call it "lack of focus." My inner critic calls it failure.
I call it research.
The 85% Sweet Spot
Here's what I've learned about that 85% mark:
You've mastered the fundamentals (the first 20% that gives you 80% of the value)
You've hit the interesting problems (where real learning happens)
You've built something tangible (proof of concept, working prototype, published draft)
You understand the domain (enough to have informed opinions)
You can teach it (to someone at 50%)
But you haven't yet hit:
The tedious polish phase
The diminishing returns of micro-optimization
The opportunity cost of not exploring the next thing
Why Polymaths Choose 85%
The polymath isn't afraid of depth. They're strategic about depth.
Going from 85% → 100% in one domain often takes as much time as going from 0% → 85% in three new domains.
The math is simple:
- Path A: 100% in one skill = mastery, narrow applicability
- Path B: 85% in three skills = competence, combinatorial creativity
Which has more creative potential? Which leads to more interesting intersections?
The Specialization Trap
Modern society worships the specialist. The doctor who only does knees. The developer who only writes Rust. The writer who only does noir detective fiction.
And yes, specialists are valuable. But they're not the only valuable archetype.
History's most interesting contributors were generalists:
- Leonardo da Vinci (artist, engineer, anatomist)
- Benjamin Franklin (writer, scientist, diplomat)
- Richard Feynman (physicist, safe-cracker, bongo player)
They didn't master every field to 100%. They went deep enough to see connections others missed.
Building in Public at 85%
This site exists because I'm tired of pretending I'm an expert.
I'm not. I'm a perpetual 85-percenter.
And that's not a bug—it's the feature.
Every post here is:
- A snapshot of my understanding right now
- Subject to revision as I learn more
- An invitation to fellow travelers
- A breadcrumb for future me
The Ambitious Polymath's Creed
Finish enough to learn, not to perfect
Document the journey, not just the destination
Value questions over answers
Celebrate the half-built
Ship at 85%
Technical Deep Dive
How I Actually Work at 85%
The 85% approach isn't about abandoning projects randomly. It's a systematic process:
classPolymathProject:def__init__(self,idea):self.idea=ideaself.progress=0self.learning_rate="high"defshould_continue(self):"""Decide if we keep going or pivot"""return(self.progress<85orself.learning_rate=="high"orself.has_external_deadline())defcheckpoint(self):"""Save state before moving on"""self.document_learnings()self.create_public_artifact()self.identify_future_paths()
Decision Framework:
Stage
Completion
Action
0-20%
Foundation
Speed through, use existing tools
20-50%
Core Building
This is where the magic happens
50-85%
Feature Complete
Working prototype, publishable
85-95%
Polish
Only if external deadline/commitment
95-100%
Perfection
Rarely worth the opportunity cost
Tools I Use:
- Obsidian: Permanent notes, knowledge graph
- GitHub: Public repos, even for "unfinished" work
- This blog: Living documentation
- Mind maps: Visual connections between projects
The Archive System:
Every project gets:
1. A README with "What I learned"
2. Links to related projects
3. "If I returned to this, I'd..." notes
4. Public deployment (even if rough)
This way, 85% projects become building blocks for future work.
Bard's Notes
Why This Post Exists
I wrote this because I needed to hear it.
Every time I start a new project, there's that voice: "You never finish anything."
But looking back at my "unfinished" projects:
- A blog that ran for 6 months taught me web development
- A half-built Discord bot taught me Python
- An abandoned YouTube channel taught me video editing
- This site (currently at 85%?) is teaching me static site generators
They weren't failures. They were tuition.
The Tension
Here's the honest part: I do sometimes wonder if I'm rationalizing procrastination.
Is the 85% rule wisdom or excuse?
The answer: both, and that's okay.
Some projects deserve 100%. Books I write for publication. Promises to collaborators. Work I'm paid for.
But for personal projects? Learning experiments? Creative exploration?
85% is shipping. 100% is perfectionism.
For Fellow Polymaths
If you're reading this and recognizing yourself:
You're not broken. You're not unfocused. You're not failing.
You're exploring in a world that demands exploitation.
You're building breadth in an age of depth.
You're choosing curiosity over credentials.
That's not a bug. That's your superpower.
The world needs specialists to go deep. But it also needs polymaths to connect the dots, see the patterns, bridge the silos.
So keep building your 85% projects.
Keep documenting the journey.
Keep shipping the half-baked.
The archipelago of your unfinished work is more interesting than any single polished island.
Updates & Revisions
This post is a living document. It will evolve as I learn more about sustainable creativity.
2025-10-28: Initial draft published at 87% (meta, right?)
Future me: Add case studies of successful 85-percenters
Future me: Link to project autopsy posts
Discussion
What's your relationship with "unfinished" work? Are you a finisher or an explorer?