Starting a side-project: Why you (and most developers) should, and how AI can help.

Business / entrepreneurship takeaways (for developers)

• Purpose of starting a side project: not “get rich quick,” but to improve as a programmer and build a mindset that includes ownership of outcomes (quality, support, revenue impact).
• Audience/eligibility assumptions:
  • Best fit: developers (especially not under an employer contract that assigns all work to them).
  • Recommends starting especially if job security is uncertain or you’re between jobs.

Strategy & operating model

• Core positioning: build a software-based product/service useful to yourself first (risk-managed “dogfooding” approach).
• Recognize architecture reuse: many online SaaS/product systems share core components:
  • Website/UI
  • Database
  • Authentication
  • Payments/billing
  • (Implied: typical web-app service plumbing)
• Expect iterative discovery + pivoting:
  • Ship something, observe what users resonate with, then tweak → change → refocus.
  • Treat early ideas as hypotheses rather than final answers.
• Side-income goal (not full-time quitting):
  • Frame the goal as incremental financial cushion while keeping employment optional.

Go-to-market (GTM) and growth playbook

• Use AI mainly for marketing/sales copy, not core coding (speaker’s view).
• A/B testing as the required growth engine:
  • Generate multiple landing-page/copy variants using AI tools (e.g., GPT/Claude).
  • Randomly assign visitors to variants.
  • Measure conversion/performance and iterate toward winners.
• Traffic strategy tradeoff:
  • Fast but expensive: accelerated development + paid ads + rapid visitor acquisition.
  • Slow but cheaper: organic/patient iteration without heavy ad spend.

“Lean startup” frameworks and process elements (explicit + implied)

• Lean Startup (book referenced): iterate quickly based on market feedback.
• Lean Product Playbook (book referenced): product iteration focus (referenced as a resource).
• A/B testing loop (practical playbook):
  1. Generate variants
  2. Split traffic
  3. Measure
  4. Discard losers
  5. Refine winners
  6. Repeat

Key metrics / KPIs mentioned or implied

• Marketing performance via A/B testing:
  • No specific KPI names given, but the target is which page/copy “performs better” (implicitly conversion rate / signups / purchases).
• Time allocation effectiveness KPI (job hunting, for context):
  • The difference between 2 hours/day vs 16 hours/day job hunting effectiveness is described as “actually pretty small.”
• Financial cushion goal:
  • “Some amount of side income” (no targets or dollar amounts provided).

Concrete examples / actionable recommendations

• Start with a personal pain point: “things in your life that bug you” that a software service could help.
• Build MVP with reusable online-service fundamentals (auth, DB, billing, website).
• Run A/B tests on marketing copy:
  • Use AI to create multiple versions of website text.
  • Split traffic and statistically determine which performs better.
  • Continue refining until you either find something worth selling or conclude it’s not viable.

Leadership / organizational mindset

• Quality and customer empathy through ownership:
  • Contrast between “bad” programmers who avoid responsibility (QA/support/financial consequences) vs “good” programmers who do their own thing or operate in small environments where they “run the whole show.”
• Manager interview indicator (leadership hiring signal):
  • Interview question concept: Given $X and Y months, what would you build?
  • Used as a proxy for whether a person has thought through execution and scoping.

High-level view on AI’s role in business (execution focus)

• AI can accelerate non-technical work (marketing/sales copy, variant generation).
• The speaker is skeptical that AI will fully replace strong developer execution in the technical build phase.
• Main recommendation: developer-led execution + AI-assisted GTM iteration.

Presenters / sources mentioned

• Presenter: Carl (host; “My name is Carl.”)
• Resources / authors referenced:
  • Eric Ries — The Lean Startup
  • Dan Olson — The Lean Product Playbook
  • Patrick aka @patio11 (A/B testing authority; linked article referenced)
• Communities referenced (scam warning included):
  • indiehackers.com
  • microconf.com