Listen to the original at Lenny’s Podcast ↗lennysnewsletter.com
By Lenny Rachitsky · with Farhan Thawar · lennysnewsletter.com · @lennysan on X · YouTube · LinkedIn
Farhan Thawar, VP and Head of Engineering at Shopify, discusses how Shopify builds a high-intensity, fast-moving engineering culture. The conversation covers choosing the harder path, pair programming, operating rhythms like six-week reviews and meeting resets, hiring through internships and job trials, and lessons from his career and failures.
01Key learnings
- Choose the harder path when options are close: even if it fails, you gain skills and work with stronger people, whereas the easy path often teaches little.
- Write down a personal framework of what you care about in a job, and use it to filter opportunities and decide when to leave a role that violates it.
- Build intensity by producing more output per minute rather than adding hours; a focused hour with strong people can outpace a long, distracted day.
- Use pair programming for hard or uncertain problems; Farhan argues it improves throughput, knowledge transfer, and design quality more than it costs in lines written.
- Treat code as a liability: regularly delete and rewrite, and run cleanup efforts like delete-code clubs to keep the codebase simple and fast to change.
- Build infrastructure that lets many people build quickly on top of it, rather than only shipping one-off features, so future work becomes an hour instead of weeks.
- Cut recurring meetings periodically and move announcements off chat, so individual contributors get more uninterrupted flow time.
- Use hiring work trials and internships to observe real work over months, since interview performance poorly predicts on-the-job success.
“If you do the hard path and it doesn't work, actually you still win because you've now done something hard.”Farhan Thawar · Lenny’s Podcast · 00:00:00
“I'm like, what if you just did more per minute?”Farhan Thawar · Lenny’s Podcast · 00:00:29
“Code is a liability and the right solution, the usually shorter lines, more elegant solution tends to appear after you've done a bunch of pathfinding.”Farhan Thawar · Lenny’s Podcast · 00:24:33
02Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.