Core Identity
Building technical products and breaking down the systems behind them.
I build and break down technical products, markets, and systems, especially at the intersection of software, AI, blockchain, and product strategy.
My strongest content shows what I am building, explains the system underneath, and extracts a useful lesson for other builders.
Archetype Structure
Builder
60%Primary archetype and default voice
Here's what I'm building, why I made this decision, and what I learned from it.
- Product updates
- Technical experiments
- Build-in-public posts
- Lessons from shipping
- Failures, pivots, and iterations
Systems Educator
30%Secondary archetype that adds depth
Most people see the output. Here's the system underneath.
- Breakdowns
- Frameworks
- Architecture decisions
- AI, blockchain, and product explainers
Operator
10%Tertiary archetype that adds founder judgment
Here's the decision behind the decision.
- Founder lessons
- Strategic tradeoffs
- Business model thinking
- Hiring and GTM reflections
Voice Formula
Builder -> System -> Lesson
Content Filter
- Does this show I am building?
- Does this explain a system?
- Does this reveal judgment?
- Would a smart technical founder respect this?
- Does this avoid generic startup advice?
Signature Ideas
- Infrastructure should disappear.
- Good products compress complexity.
- Technical products need narrative, not just engineering.
- Markets reward clarity faster than complexity.
- Most builders overbuild before they understand the constraint.
- AI and crypto both suffer from abstraction problems.
- Speed matters, but sequencing matters more.
Signature Phrases
- The constraint is not technical.
- Infrastructure should disappear.
- Complexity is not a moat unless users feel the benefit.
- Most builders solve the wrong layer.
- The interface is the product.
- This is a sequencing problem.
- Good products compress complexity.
- The system underneath matters more than the surface.
Content Pillars
Building in Public
- Built X this week.
- Thought the hard part would be Y.
- It was actually Z.
- The lesson: insight.
Systems Breakdowns
- Everyone explains this as the surface-level reason.
- I think it is actually the deeper system.
- Here's the breakdown.
Technical Product Thinking
- The mistake most technical founders make:
- They expose the system they built instead of the outcome users want.
Founder Operator Lessons
- One thing I learned building technical products:
- The market does not reward technical difficulty.
- It rewards obvious value.
Weekly Cadence
Monday
Systems post: break down a market, product, or technical pattern.
Tuesday
Build update: what shipped, what changed, and what surprised me.
Wednesday
Technical lesson: one product or engineering insight.
Thursday
Opinion post: a clear POV on AI, crypto, software, or founder behavior.
Friday
Operator reflection: a lesson from building, selling, fundraising, or positioning.