Engineering You

on YouTube ↗48m

" summary

Argues that engineering practices beat alchemy: testing must be interlaced with design (Alan Perlis, 1968), iterative work and doing the hard problems up front shorten feedback cycles, small teams outperform teams >20, and CI is non‑negotiable. Cites surprising scale: modern cars reach 350 million lines of code and humans struggle beyond more than 10,000 lines is hard to hold in the head. Finds concrete fixes: design fundamentals (coupling/cohesion), clear protocols, delete dead code, and unit tests catch ~70% of avoidable outages while 25% stem from ignored errors.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 27:02Decomposition & Abstraction
3. 34:21Reading Code
4. 38:03Measure

" related talks

• 35mCraft, Engineering, and the Essence of ProgrammingGlenn Vanderburg · RailsConf 2011
• 01h 00mEngineering SoftwareKevlin Henney · Jfokus 2018
• 48mA Personal Philosophy of Excellent EngineeringAndrew Russell · GCAP 2022: Ambition
• 42mwhy software development is an engineering disciplineGlenn Vanderburg · O'Reilly Software Architecture Conference 2015
• 41mComputer Science, Software Engineering, and the Scientific MethodAlex Gaynor · PyCon Australia 2013
• 45mTaking Back "Software Engineering"Dave Farley · GOTO Oslo 2020
• 17mThe Soul of Engineering: How to be the SolutionRobert Altinger · Techsylvania 2018
• 27m'The Art of Software Development'Sander Mak · J-Fall 2023