~/talk

What It Really Means to Be an Effective Engineer

links:none on file
slides:none on file

Reports findings from interviews at Google Facebook Dropbox Airbnb Stripe Instagram and more and a 2015 book that reframes effectiveness as maximizing leverage the ROI on engineer time rather than hours worked. Gives concrete data points: Instagram sells to Facebook with 13 engineers supporting 40 million users so each engineer covers ~8 million users and ~$77M in value. Recommends concrete practices and tools: do the simple thing first, invest in debugging monitoring and iteration speed, and use design the alliance and share assumptions to build trust fast.

AI-written summary · about

  1. 0:00Intro
  2. 2:35You should be ready to make this startup the primary focus of your life.
  3. 6:39Impact Produced Hours Spent
  4. 7:27Effective engineers focus on high-leverage activities
  5. 7:46What are the high-leverage activities for engineers?
  6. 11:00What's the costliest mistake your team's made in the past year?
  7. 11:12Effective engineers build the simple version first
  8. 12:34Effective engineers validate their ideas early and often.
  9. 18:03Effective engineers build infrastructure for their relationships.
  10. 18:21What are the best practices for building good infrastructure for our relationships?
  11. 20:23RELATIONSHIP INFRASTRUCTURE Effective engineers explicitly design their alliances.
  12. 21:38Effective engineers explicitly share their assumptions
  13. 22:40Effective engineers build trust by making the implicit things explicit
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.