As a solo technical founder, how much time should I really spend understanding the job before writing any code?
The short answer
Enough to talk to ten or fifteen people, which is days, not months, and far less than the time you'll waste building the wrong thing. The technical founder's specific risk is retreating into code because building feels productive while interviews feel awkward. As a starting point, cap the research at a week or two, but don't let "I'm an engineer" be the excuse for skipping it entirely.
Go deeper, your way
3 hand-picked resources, 3 link-checked. Pick how you want to dig in.
▶️ Video
✓ Link checkedFreeBeginner
Why we picked it
When you are new to a space, your instinct is to explain your idea and hope people nod, which teaches you nothing. This YC talk is a concrete guide to running discovery interviews the right way: extract data from the person instead of pitching, and use a small set of questions that work in any industry, including one you are still learning. It pairs well with The Mom Test as the applied version you can watch before your next call.
Why we picked it
The canonical primary source on the mindset shift before you start up, Graham's Stanford lecture directly addresses whether you need startup expertise and why the leap is more counterintuitive than it looks. Essential reading before you quit anything.
Why we picked it
The single best thing ever written on customer conversations. It teaches you to ask about the customer's life and past behaviour, not your idea, so you can't be lied to. If a founder reads one thing before talking to a single customer, it's this.
