tl;dr:Code is "big ball of mud" at growth stage companies. Will describes a new approach to untangle it. "List all the beliefs you'd need to have to be confident in modifying your software" and see how they move up the behavior & property ladder, which he describes in detail.
tl;dr:Will focuses his career on growth and engagement, not equity & IPOs. He looks at it from a 40 year perspective, and how to maximize factors important to him - pace, people, prestige, profit and learning.
tl;dr:Larson shares his system for gauging size and state of engineering teams - ratios and frameworks to structuring team size, combining and spinning up teams, and assessing and accelerating team progress.
tl;dr:The following are explained in detail (1) measure what you hope to improve (2) size the org against peers, goals and performance (3) structure into smaller teams (4) project growth (5) rest in between changes to master the current structure.