Building a world class engineering organization — learning from...
summary
Compares longevity of Brewarrina Aboriginal Fish Traps (40,000 years), White Horse of Uffington (3,000 years) and Stonehenge to software: longevity comes from materials or maintenance. Claims engineering must enforce default branch deployable, run CI on every push, keep tests under five minutes (parallelize with knapsack Pro), prefer Rails/ERB with measured Stimulus/Hotwire, make small PRs, finish migrations, and ship the Hover computer‑vision 3D house models reliably by treating upkeep as first‑class work.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:09Speaker background
- 7:24Company overview
- 9:11Historical maintenance to principles
- 15:55World-class engineering org
- 21:13Tactical engineering principles
- 33:46Rails conventions
- 40:27People and collaboration
- 44:03Call to action
related talks
28mSoftware Engineering - Development in 100 Years Time
43mBuild “boring” engineering orgs
47m‘Engineering' for Software - How to Amplify Creativity
01h 14mDeliberate Architecture
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
40mWhy your best engineers should look after the worst systems
52mSecrets of a Strong Engineering Culture
01h 01mEngineering for Software - How to Amplify Creativity