Issue #305

tl;dr: Split code management into 2 tasks: Reducing complexity & increasing confidence. (1) Reducing complexity so you have fewer parts and interconnections between them. Develop "concepts with better boundaries." (2) Increase confidence by streamlining. Minimize ways things can be done, make them obvious and make sure they work. Andreas explains light-weight processes to do both. 

tl;dr: Varies on whether the company is early-stage, prioritizing growth or profitability. (1) Early stage: If you reduce your infrastructure costs to $0, and it doesn’t increase your runway by at least two months, it’s not worth focusing on. (2) Growth: "The fundamental question is whether infrastructure’s share of cost of goods sold are increasing as a percentage of revenue?" (3) Profitability: Align with the business on dollars spent on infrastructure overhead per engineer. 

tl;dr: "You’ll hear about the birth of Unix, Ken Thompson’s unique skillset, why Brian thinks C has stood the test of time, his thoughts on modern languages like Go and Rust, what’s changed in 50 years of software, what makes platforms like Unix and the web so powerful, his take as a professor on the trend of programmers skipping the university track, and so much more."

tl;dr: Julien highlights some of the challenges: "Weird" album names, albums without names, confusing names, long tracks up to 23 hours, tracks with different versions and more. Julien also links to the DB schema to show how to "tame this madness."