Ryan Rhodes
84 posts




My conversation with @EricJorgenson, author of The Book of Elon (@elonmusk). 0:00 Book Reveal 0:39 Build Useful Things 2:19 Engineering Talent Edge 4:26 Wired for War 6:47 Tip of the Spear 8:47 Burn the Boats 13:13 Facing Fear 15:16 Origin Story Myths 18:19 Know Business A to Z 22:17 Simplify and Fail Fast 25:35 Reality and Physics 28:18 The Algorithm Begins 30:34 Delete and Simplify 34:25 Starlink War Room 36:52 Repetition as OS 38:18 Step Three Simplify Optimize 38:43 Question Every Requirement 39:13 Tesla Battery Pack Delete 40:43 Repetition Installs Ideas 42:02 Step Four Accelerate 43:26 Design Org for Speed 46:06 Step Five Automate 46:29 Control and Clean Sheet 48:54 Vertical Integration and Costs 50:47 SpaceX Incentives and Mars 57:11 Frontier Unlocks Starlink 1:00:26 Time as True Currency 1:03:58 Speed Triage and Bottlenecks 1:10:11 Internalized Responsibility 1:12:56 Avoid Serialized Dependencies 1:14:31 Aligning the Team 1:15:07 Time Is the Constraint 1:16:00 One Metric Focus 1:18:03 Directional Predictions 1:19:06 We Must Make Stuff 1:25:39 Manufacturing as Moat 1:26:23 Speed and Direct to Customer 1:28:41 SpaceX Feasibility Study 1:33:07 Edge of Sanity Leadership 1:37:10 Bottlenecks and Integration 1:40:01 Design and Simplify 1:45:15 Catch the Rocket 1:48:14 Capitalism and Closing Includes paid partnerships.











my entire career strategy hangs on a strong belief that we are not going to see fully automated software generation in my lifetime. but we are going to see an end to the ralph-loop, spec-driven-one-shot-dream, and the "end of white collar work" hype. we're already seeing some high profile players in software development start to set their coarse along the same path i've been following these past few years. it starts with "wow" then "i can use my skills to fully automate this" and then it proceeds to "fast but no cognitive ownership" then disappointment, confusion, frustration, and ends with "hey, this isn't going to work guys, we need to be more disciplined and look at the code, keep our cognitive ownership, and just use the tools to improve our outcomes. these are not our replacement, these are our accelerators. it's the same story, different tooling". i'm already there. if a company were to come to me today and say "we tried all the trendy stuff but it just made everything worse, we're losing control of our code base, we need to either ditch these things or make them a power-up" then i am ready for that. if i am wrong, then so be it. my career is over anyway because i have zero interest in giving up cognitive ownership and responsibility (the ability to respond), while remaining accountable. i'd rather wash dishes or stack shelves than submit myself to the horrors of remaining accountable without cognitive ownership, agency, and responsibility.




Agent harnesses aren't the black magic many of y'all seem to think they are. To prove it, I built one.








