💡

InsightHunt

Hunt the Insights

F

Farhan Thawar

Vice President and Head of Engineering

Shopify

🚀 Career & Leadership (1) Execution (1)🎯 Product Strategy (1)👥 Team & Culture (1)

Key Takeaways

  • 1.Optimize for 'kilojoules per hour' rather than hours worked; increasing intensity often yields better results than increasing duration.
  • 2.When faced with multiple options, default to the harder path; even if you fail, the skills acquired and the talent you work with will be superior.
  • 3.Implement 'Meetingageddon': annually delete all recurring meetings with 3+ people to force teams to justify their time and prevent inertia.
  • 4.Use pair programming not just for code quality, but as a forcing function against multitasking and distraction.
  • 5.Hire for 'slope' rather than 'intercept' by utilizing job trials and internships; interviews are poor predictors of performance compared to actual work samples.
  • 6.Adopt a 'Platform-First' mindset: instead of building a feature in 2 weeks, spend 2 months building the infrastructure that allows anyone to build that feature in 1 hour.
  • 7.Prioritize deleting code as a strategic objective to maintain velocity; simplicity enables reliability and speed.
  • 8.Use the 'Life Story' interview format to understand the 'why' behind career transitions, rather than just the 'what' of skills.

Methodologies(4)

The Hard Path Heuristic

by Farhan Thawar

🚀 Career & Leadership

A decision-making framework where, when presented with multiple options, one defaults to the option that presents the highest difficulty. The logic is that the 'easy path' offers no learning if it fails, whereas the 'hard path' guarantees skill acquisition and access to high-caliber talent regardless of the outcome.

Core Principles

  • 1.The Learning Hedge: If you fail on the hard path, you still win because you acquired complex skills.
  • 2.Talent Density: Smart, ambitious people naturally cluster around hard problems; choosing the hard path puts you in the same room as them.
  • 3.Embrace 'Looking Stupid': Actively seek situations where you are the least knowledgeable person in the room to accelerate growth.
  • +1 more...

"If you do the hard path and it doesn't work, actually you still win because you've now done something hard."

#heuristic#career#leadership
View Deep Dive →
Execution

An operating system designed to maximize energy output per minute rather than simply increasing working hours. It relies on tight feedback loops, pair work to prevent distraction, and aggressive removal of process drag (meetings/code).

Core Principles

  • 1.Pairing as Focus: Use pair programming (or pair product work) to eliminate multitasking and force immediate decision-making.
  • 2.High-Fidelity Demos: Replace status reports with live demos or 'Spin' environments (beta flags) to force truth and quick iteration.
  • 3.6-Week Cycles: Utilize a 6-week cadence for shipping and reviewing work to create natural urgency and check-points.
  • +1 more...

"Everyone says, 'Oh yeah, work hard and do more hours...' I'm like, 'What if you just did more per minute?'"

#'kilojoules'#intensity#execution
View Deep Dive →
🎯 Product Strategy

A product development philosophy championed by Tobi Lütke where teams are challenged to build the underlying infrastructure that makes a feature trivial to implement, rather than just hacking together the feature itself.

Core Principles

  • 1.The 'One Hour' Test: Don't ask how long it takes to build X; ask what needs to be true so that X can be built in one hour.
  • 2.Speculative API Design: Write the client code against an API that doesn't exist yet to define the ideal developer experience, then build the backend to match.
  • 3.Gas in the Tank: Categorize work as 'Experiment', 'Feature', or 'Infrastructure'. Prioritize Infra to fuel future velocity.
  • +1 more...

"He goes, 'How long would it take to build a platform layer which exposes APIs so anyone could build NFT gating in one hour?'"

#api-first#infrastructure#mandate
View Deep Dive →
The Job Trial Protocol

by Farhan Thawar

👥 Team & Culture

A hiring strategy that prioritizes work samples and probationary periods over resume screening and theoretical questions. It acknowledges that the only way to know if someone is a good race car driver is to put them in the car.

Core Principles

  • 1.The 90-Day Interview: Treat the first 3 months of employment as the final stage of the interview process; expect and plan for attrition here.
  • 2.Internships as Pipelines: Use massive internship cohorts (1,000+ people) not as charity, but as a filtered funnel for full-time talent.
  • 3.The 'Life Story' Screen: Use interviews to uncover the 'why' behind career moves to assess curiosity and range, rather than skills checklists.
  • +1 more...

"If I told you, 'Hey, I want to go hire the best race car driver,' there's not really that many questions you could ask them except for put them in the car."

#trial#protocol#team
View Deep Dive →