Oct 10, 2018 · 59m · y-combinator
Startup Technology - Technical Founder Advice · Y Combinator
Calvin French-Owen · 12m spoken Lillian Chou · 12m spoken Ralph Goody · 11m spoken Diana Hu · 11m spoken Jared Friedman · 4m spoken
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this Y Combinator panel hosted by Jared Friedman, four technical founders share practical advice on building initial product MVPs, balancing shipping velocity with code quality, structuring engineering teams, and aligning technical choices with business growth.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. The partners hold 29.5% of the talking time here. How this is scored →
The partners as informed peer 4.3 Guest teaching 2.7 Guest disagreement 1.1 The partners pushing back 1.3
speaking balance: gold is the partners, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 33:25 Ralph pushes back against test dogmatism
Ralph candidly challenges the orthodox view of unit testing, pointing out that many engineers write useless spaghetti test frameworks in production releases rather than shipping working code.
Hardest push from the partners ▶ 25:48 Jared presses for exact timelinesJared pushes Lillian to clarify exactly how many years after launch their formal engineering controls were introduced rather than accepting vague generalizations.
Biggest teaching moment ▶ 13:30 Calvin recounts Paul Graham's reality checkCalvin explains how Segment burned half a million dollars building an analytics tool before pivoting to an open-source API, illustrating the classic pitfall of building before validating market need.
The partners hold their own ▶ 15:03 Jared reinforces the core takeawayJared seizes on Calvin's narrative to drive home the foundational startup lesson of shipping a minimum viable product in just one week.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The partners as informed peer | Guest teaching | Guest disagreement | The partners pushing back | Why |
|---|---|---|---|---|---|---|
| Founder Introductions and Technical Stacks | 4 | 2 | 1 | 1 | Jared opens with standard introductions and prompts each founder to lay out their tech stacks and infrastructure. The guests provide straightforward overviews of their respective architectures across AWS, GCP, and native mobile stacks in a completely collaborative opening. | |
| Building Version One and Early Iterations | 5 | 3 | 1 | 2 | Jared guides the conversation through the timeline and failures of each founder's V-one product, emphasizing rapid iteration. The founders explain their initial hurdles, notably Calvin detailing Segment's rapid one-week pivot after burning runway and Diana discussing SLAM algorithms. | |
| Engineering Best Practices versus Shipping Speed | 5 | 4 | 2 | 2 | Jared asks the highest-voted audience question on engineering best practices versus shipping speed, pressing on the exact milestones when testing and security became mandatory. Ralph offers a nuanced take contrasting standard advice, emphasizing that construction software demanded day-one stability while warning against bloated mock testing. | |
| Engineering Methodologies and Team Process | 4 | 2 | 1 | 1 | The panel explores engineering methodologies like Agile and OKRs, with all founders agreeing on a pragmatic, 'agile-ish' posture rather than dogmatic adherence. Jared facilitates smoothly as each founder describes their transition from loose startup communication to structured frameworks. | |
| Working with Non-Technical Founders and Deadlines | 4 | 3 | 1 | 1 | Jared introduces the challenge of technical founders collaborating with non-technical peers on deadlines. Ralph provides candid advice on padding deadlines and using non-technical co-founders for testing, while Calvin shares his decentralized estimation method. | |
| Structuring Early Teams, Hiring, and Remote Work | 4 | 3 | 1 | 1 | Jared poses a broad question on early hiring, contractor usage, and remote versus in-person team building. The founders offer practical guidance, with Lillian emphasizing protecting core competencies and Ralph debunking the myth that contractors require zero management overhead. | |
| Live Audience Q&A on Development and CTO Alignment | 4 | 2 | 1 | 1 | Audience members ask about accelerating engineering cycles and bridging technical/business divides on features versus stability. The panel offers rapid, unanimous advice centered on placing engineers directly in front of end users to resolve priority disputes. |
Statements from this episode (21)
French-Owen: Segment runs around 300 microservices primarily written in Go
“Today we're running about 300 different microservices, which are kind of piping together various Kafka topics and reading and writing, transforming this data, getting it to where it needs to go and our backend is primarily written in Go.”
Hu: Writing computer vision algorithms in C++ enables seamless mobile-to-server migration
“It's a lot more efficient for us to write the code and all of the algorithms once, and then cross-compile it across all the architectures for Android or iOS, and even the backend, so that we run some of the CV algorithms, we could prototype it in the phone, an…”
Gootee: PlanGrid built the first mobile blueprint viewer
“Used some off-the-shelf computer graphics knowledge to write the first Blueprint viewer that ever ran on mobile.”
Hu: iPhone 7 matches compute power of 2013 MacBook Pro
“For example, for iPhone seven, has the same computation, actually, as a MacBook Pro from 2013”
Chou: Early startups should use familiar tech until product-market fit
“It's more important in the early days to be able to Iterate quickly, and usually that comes from using the technology that you know the best and building things in a modular way such that once you actually find that product market fit and know what your audien…”
Chou: Speed is paramount because customers won't pay for test coverage
“So speed is paramount. Nobody's gonna pay you for having excellent test coverage.”
Hu: Escher Reality rewrote its entire codebase after joining Niantic
“The only time we started actually having all the best practices is actually once we joined Niantic, because now we have to integrate into the games which, ah, Pokemon Go has hundreds of millions of users, so we're burying ourselves to get a lot of the, we pret…”
French-Owen: 90% of Node shops run code written by TJ Holowaychuk
“I think 90% of node shops run on some part of his code.”
Gootee: PlanGrid is used on most California hospitals and tech campuses
“Plain Grid's used to build all, ah, in California, most, most hospitals, most jails, most heavy civil road work were used on all the tech campuses, all of the different government buildings that go up.”
Gootee: Startups should architect systems one year ahead, not three
“We always try to balance it between engineering, like, a year ahead of time, but not maybe three years ahead of time, which is a trade-off.”
French-Owen: Segment allows individual engineering teams to self-organize without mandated processes
“For us we don't have any set process that teams have to follow at segment kind of individual engineering teams, sort of like what Spotify does are able to self-organize. They're able to run however they want. If they want to do sprints, that's cool. If they wa…”
Gootee: Non-technical co-founders make excellent early QA testers
“If you've got someone that's really non-technical, and I'm not saying my co-founder is really non-technical. I'm sure she can use a computer. But you know, if it's really non-technical, this is an amazing testing opportunity for you. I mean, I remember I would…”
French-Owen: Asking engineers individually in 1-on-1s prevents timeline anchoring
“Kind of the trick that I've started using is in one-on-ones actually asking each person what they think will happen over the next three or four weeks. And what I find asking one to one is that one people don't anchor against each other's answers. So you get a …”
Chou: Gaining traction shifts technical founders from coding to org-building
“There's a pretty big shift that happens once you start gaining traction, where it's less about building a product for a market and finding that fit, and it shifts more into turn, like, building an organization, a company and a system, like this system of human…”
Chou: Outsourcing core IP turns a startup into a marketing company
“What's your IP? You don't want to outsource that at some point. If you do, you're pretty much just a marketing company.”
Hu: Escher Reality contracted candidates for a month before extending offers
“We did contract people as, ah, more of an interview process. So we would work with and contract someone for a month before we gave them an offer.”
French-Owen: Segment hired first 15 remotely, next 70 only locally
“So while we grew remote from about the first, I don't know, 10 or 15 hires, we then only grew locally through about the next 70, and then only recently started opening remote backup.”
Gootee: Managing contractors often requires more founder time than full-time employees
“Management of contractors is significant time for you as a founder. That is not a free hire. It's sometimes is worse. Actually, it's more management time. For a contractor than a full-time employee.”
French-Owen: Founders should build throwaway prototypes to get safe reps before building V1
“I think if I were to start again today, actually I'd build two or three versions, which I just intended to throw away. Maybe this is biased on prior experience, but I think the fact that you can get reps in a very safe manner, where then when you're really rea…”
Gootee: PlanGrid would have built faster by hiring developers earlier instead of self-coding
“Probably the best advice I could give though is I'd stop Coding a little bit earlier, and I would start hiring a little bit earlier, because I think there's a lot of me that wanted to passionately write those features, and if I had instead been passionately hi…”
Gootee: Putting CTOs directly in front of users is the most powerful alignment tool
“Get them in front of the users. Bring them to the meetings. Get them over the phone. Well, then give the questions, you know, kind of set it up a little bit where you're trying to bait the users into giving the feedback that you're looking for, or you won't ge…”