A core step in Elon Musk's scaling algorithm is to 'Automate Last.' Tesla discovered that automating a process before it's manually optimized is a recipe for disaster. The Model 3 production crisis was only solved when they abandoned the over-automated line and started building cars by hand in a tent.

To enforce its "the best part is no part" philosophy, SpaceX has a rule: if you aren't adding back at least 10% of the requirements you previously deleted, you aren't being aggressive enough. This counter-intuitive metric ensures engineers continuously question and simplify designs.

The culture at X under Elon Musk dismantles historical constraints by ruthlessly questioning every requirement. This environment, while disruptive, trains designers to shed their calloused ways of working within passive constraints and design without barriers.

A key lesson from SpaceX is its aggressive design philosophy of questioning every requirement to delete parts and processes. Every component removed also removes a potential failure mode, simplifies the system, and speeds up assembly. This simple but powerful principle is core to building reliable and efficient hardware.

Before optimizing, Musk's engineering algorithm has two critical preceding steps: question the requirements and then try very hard to delete the part or process. This combats the common engineering pitfall of optimizing something that shouldn't exist.

Simple design is fast and cheap, and it starts with minimal requirements. By aggressively questioning every single requirement, even those that seem obvious, engineering teams can often delete constraints or find opportunities to reuse existing solutions, radically simplifying the design and accelerating the production timeline.

Beyond technology, Tesla's durable advantage is its 'capacity to suffer'—a willingness, driven by Elon Musk, to endure extreme hardship like 'manufacturing hell' to solve problems. This allows the company to pursue innovations that more risk-averse competitors would abandon.

The "SOL" framework at NVIDIA isn't just a top-down executive command to "get the bullshit out." It's a cultural tool used by frontline engineers to challenge assumptions and push for a root-cause, physics-based understanding of timelines and constraints on any project.

Musk's approach is radical de-layering. He avoids the 'compounding lies' of middle management by going to the source of truth: the engineers. He identifies the week's biggest bottleneck and works directly with the relevant engineer to solve it, creating unparalleled problem-solving velocity.