AI summary by TwinMind
Tips For Technical Startup Founders | Startup School
Y Combinator
28m 12s
Speaker Introduction
- Diana, Group Partner at YC
- Previously co-founder/CTO of Azure Reality (AR SDK for game developers)
- Sold to Niantic, became Director of Engineering for AR platform
- Experience scaling from idea → prototype → MVP → millions of users
Role of Technical Founder
- Not just "someone to build my app" - requires intense commitment as partner
- Lead product building + talk with users
- CEO vs CTO role depends on product type, industry, team composition
- Early stage = lead developer responsibilities
- Must handle all tech aspects: front-end, back-end, devops, website, UX, IT
- Hardware founders: electrical + mechanical engineering
- Bias toward "good enough" vs perfect architecture
- Comfortable with technical debt, inefficient processes, ugly code, chaos
- Do whatever it takes for company success - no "not my pay grade" mentality
Stage 1: Ideating
Goal: Build prototype ASAP to show/demo to users
- Singular focus: something to demonstrate (doesn't need to work fully)
- CEO co-founder finds users for prototype demos
- Build very quickly (matter of days)
Prototype Examples:
- Software: clickable prototype (Figma, Envision)
- Devtools: simple script launched in terminal
- Hardware: 3D renderings showing product promise
- Remora example: truck carbon capture attachment renderings excited users
Case Studies:
- Optimizely (YC W10): switched from Twitter referral widget idea
- Built visual A/B test editor in days
- JavaScript file on S3, manual Chrome console testing
- Showed to marketers (target users) successfully
- Azure Reality: computer vision algorithms on phones (few weeks)
- AR demo much easier than explaining/hand-waving
Common Mistakes:
- Overbuilding - thinking prototype must show full vision
- Not talking to users soon enough
- Getting too attached to bad ideas based on feedback
Stage 2: Building MVP
Goal: Build working product to launch, get user commitment (ideally payment)
- Timeline: days to weeks (ideally weeks range for software)
- Hardware/deep tech exceptions take longer
Hiring Considerations:
- Generally avoid hiring at this stage - slows launch
- Takes 1+ months to find good people
- Miss key product insights if others build instead of founders
- Exception: Justin.TV/Twitch - 4 founders, 3 technical
- Kyle (video streaming), Emmett (database), Justin (web)
- Post-launch hired "misfits" overlooked by Google
- Amon and Golem became amazing engineers quickly
Building Principles:
1. Do Things That Don't Scale
- Find clever hacks to launch quickly
- Avoid: automatic self-onboarding, scalable back-end, automated scripts
- Use: manual onboarding, editing database directly, custom support
- Stripe example: simple API launch, founders manually processed payments/bank forms
2. Create 90/10 Solution (Paul Buchheit concept)
- First version won't be final, code will be rewritten
- Push features to post-launch
- Good enough quality, not bugs
- Restrict product to limited dimensions: situations, data types, functionality, users, devices, geo
- Startup superpower vs large companies
Case Study: DoorDash
- Originally "Palo Alto Delivery"
- Built in one afternoon
- PDF menus, founder's phone number
- Static HTML/CSS front-end
- Google Forms/Docs back-end
- iPhone "Find My Friends" for driver tracking
- Constrained to Palo Alto only
- Focus on suburbs vs metro cities (vs GrubHub)
- Got unit economics right early
3. Choose Tech for Iteration Speed
- Balance product needs + personal expertise
- Don't choose cool new languages just to learn
- Use familiar, comfortable tech for quick launch
- Leverage third-party frameworks/APIs:
- Auth0 (authentication)
- Stripe (payments)
- React Native (cross-platform)
- AWS/GCP (cloud)
- Webflow (landing pages)
- Lambda/Firebase (serverless)
Tech Philosophy:
- "Noob vs Mid-wit vs Jedi Master" meme
- Noob: uses PHP/JavaScript (simple)
- Mid-wit: overengineers with Kafka, Kubernetes, microservices
- Jedi Master: also chooses PHP/JavaScript but for speed reasons
- Facebook example: PHP → custom HipHop transpiler when needed
- Tech choices don't matter if you get users - can solve scaling later
Case Study: WayUp (YC 2015)
- JJ (CTO) self-taught, chose Django/Python
- Peers recommended Ruby/Rails (10x more popular)
- Simple stack: Postgres, Python, Heroku
- Right choice for iteration speed
Key Point: Only tech choices tied to customer promises matter (API level commitments)
Stage 3: Launch & Iteration
Goal: Iterate toward product-market fit
1. Quickly Iterate with Hard & Soft Data
- Hard data: analytics dashboard tracking main KPIs
- Simple tools: Google Analytics, Amplitude, Mixpanel
- Avoid complex: Logstash, Prometheus (for large companies)
- Soft data: continue talking to users post-launch
- Understand why users stay/churn, discover new problems
Case Study: WePay
- Launched as B2C payments (Venmo-like)
- Analytics showed messaging features unused
- Biggest user: GoFundMe (didn't care about B2C UI)
- Pivoted to API, applied "don't scale" principles
- No technical docs initially, worked directly with GoFundMe
- API version achieved product-market fit
2. Continuously Launch
Case Study: Segment
- Started as classroom analytics, struggled
- Launched stripped backend version (actual Segment)
- First launch: December 2012, high Hacker News engagement
- 5 launches in one month span
- Added features iteratively: Node, PHP, WordPress support
- Became unicorn, sold to Twilio for $3B+
3. Balance Building vs Fixing
- Technical debt is fine - get comfortable with "tech burning"
- Fear right things: focus on product-market fit
- Small bugs may not be critical to fix immediately
- Pokemon Go example: couldn't log in at launch
- Didn't kill company, made $1B+ revenue last year
- Load balancer/nginx TCP termination issues
- Same active users as Twitter (10 years) in 1 month
Common Post-Launch Mistakes:
- "What would Google do?" mentality
- Over-hiring to move quickly
- Focusing too much on refactoring vs building features
- Not staying involved with user insights
- Building only product features, not growth tech
- Best growth hacks: engineers + sales/growth collaboration
Post Product-Market Fit Evolution
- Can finally "put on big engineering pants"
- Identify tech pieces needing scale rebuilding
- Tech will break from demand (good problem)
- Rework/refactor at this stage, not before
- Define engineering culture
- Hiring phase: people you know first
- Role evolution by team size:
- 2-5 engineers: 70% coding time
- 5-10 engineers: <50% coding time
- 10+ engineers: minimal coding time
- Choose architect vs people management role
Summary by Stage
Stage 1 (Ideating): Build prototype ASAP (days) Stage 2 (MVP): Build to launch quickly (weeks) - do things that don't scale, 90/10 solution, choose tech for speed Stage 3 (Launch): Iterate toward product-market fit - hard/soft data, continuous launches, balance building/fixing
Key Takeaway: Startups move quickly
