Risk Management

James Phoenix
James Phoenix

You can take asymmetric bets only if the floor is protected.


The Four Dangers

1. Infinite Preparation Risk

“I’m building leverage” can become a story that hides fear of exposure.

Symptoms:

  • Always “almost ready” to ship
  • Perfecting infrastructure nobody uses
  • Avoiding market contact

Mitigation:

  • Hard review dates
  • Forced shipping milestones (see Liquidation Cadence)
  • External reality checks

2. Cognitive Overfitting

Building systems for problems that never arrive.

Symptoms:

  • Abstractions without use-cases
  • Solving hypothetical problems
  • “Future-proofing” that never pays off

Mitigation:

  • Anchor infra to real use-cases
  • Periodically prune abstractions
  • Ask: “What would break if this shipped tomorrow?”

3. Isolation Risk

Few peers operate at this layer.

Symptoms:

  • No external feedback
  • Echo chamber of own ideas
  • Losing touch with market reality

Mitigation:

  • Write doctrines (forces clarity)
  • Seek high-signal conversations
  • Avoid outcome-driven validation loops

4. Runway Erosion

Leverage doesn’t pay bills by itself.

Symptoms:

  • Declining savings without income plan
  • “It’ll work out” thinking
  • Pride preventing backup plans

Mitigation:

  • Maintain baseline income sources
  • Keep job option warm, not active
  • Treat a job as a tool, not an identity

The Barbell Strategy

Protect against both failure modes:

Cashflow Rail (stability)

  • Udemy courses
  • Selective client work
  • Part-time employment if needed

Purpose: Never forced into panic decisions

Leanpub Book

Read The Meta-Engineer

A practical book on building autonomous AI systems with Claude Code, context engineering, verification loops, and production harnesses.

Continuously updated
Claude Code + agentic systems
View Book

Compounding Rail (moat)

  • Software factory
  • Agent harnesses
  • Testing infrastructure
  • OTEL/observability
  • Deployment repeatability

Purpose: Build durable competitive advantage


Downside Management Principles

  1. You must manage downside explicitly now. Your 30s don’t have infinite retries
  2. Keep at least one credible path back to income. Always have an escape hatch
  3. Never let pride remove safety nets. Ego is expensive
  4. Never let safety remove ambition. Comfort is also expensive
  5. Cash flow buys thinking time. And thinking time buys better bets
  6. Desperation kills judgment. Protect your ability to think clearly

The Floor Test

Before any major bet, answer:

If this completely fails, what happens?

Acceptable answers:

  • “I lose 3 months and learn something”
  • “I can return to consulting”
  • “I have savings for 6 more months”

Unacceptable answers:

  • “I don’t know”
  • “I’ll figure it out”
  • “It has to work”

Related

Topics
Asymmetric BetsBusiness StrategyDecision Making FrameworksLiquidation CadenceRisk Management

Newsletter

Become a better AI engineer

Weekly deep dives on production AI systems, context engineering, and the patterns that compound. No fluff, no tutorials. Just what works.

Join 306K+ developers. No spam. Unsubscribe anytime.


More Insights

Cover Image for How to Easily Translate High Fidelity Prototypes into Functional Apps

How to Easily Translate High Fidelity Prototypes into Functional Apps

Vague specs do not converge. Scalar loss functions do. If you can hand the agent a number that says “you are 0.66 wrong,” it will close the gap on its own.

James Phoenix
James Phoenix
Cover Image for The Four-Layer Wall Around Your Library’s Public API

The Four-Layer Wall Around Your Library’s Public API

When an agent loop writes most of your library, the largest risk is not a bug in a feature. It is the loop helpfully exporting an internal helper, an experimental type, or a half-finished module. Once that ships in a minor release, you own it forever. Four package-level layers stop the loop from doing this without anyone having to remember.

James Phoenix
James Phoenix