Skip to content

Instantly share code, notes, and snippets.

Speaker 1
00:00 - 05:49
Hi everybody, this is Jordi from Agents at Work and today I have the pleasure to be with Rodrigo. He's an economist, worked for five years into BC land. He was a programmer since he was a teenager so he decided that he was going to try into tech and it was 10 years since then that he has been like into like really deep tech. Hi Rodrigo. Hi, how are you doing? Doing well, thank you. So your story it's already interesting from where you started and how you ended up or now you're in the middle of the story but you know like where you are at now how was that yeah i i took a con in graduation right and then i thought i was going to go into research so from the beginning i always loved theory right and i tried to build my own theories in the first year but by the end of the second year i watched a presentation about venture capital from monash's capital which is a i think it's the foremost fund manager in Brazil for venture capital. And by 2011, they were beginning, right? So that all made s
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

The algorithm

At any given production meeting, whether at Tesla or SpaceX, there is a nontrivial chance that Musk will intone, like a mantra, what he calls “the algorithm.” It was shaped by the lessons he learned during the production hell surges at the Nevada and Fremont factories. His executives sometimes move their lips and mouth the words, like they would chant the liturgy along with their priest. “I became a broken record on the algorithm,” Musk says. “But I think it’s helpful to say it to an annoying degree.” It had five commandments:

  1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so
@kafkasl
kafkasl / sp500_constituents.json
Created March 7, 2019 13:47
List of S&P 500 historical constituents from 2008/01/31 to 2019/02/27. JSON format where each date contains a list of the constituents.
This file has been truncated, but you can view the full file.
{
"2008/01/31":[
"GHC",
"MDP",
"GAS",
"AZO",
"MIL",
"MXA",
"ASH",