Our Mill City
summary
Twin Cities history becomes a systems lesson: at one point 30 sawmills and eight prosthetic factories cluster on Saint Anthony Falls, and a flour mill explosion kills 14 but gets rebuilt in two years, showing resilience. Claim: architectures oscillate between monoliths and microservices and most teams end up with distributed monoliths. Tools and patterns called out: shaft‑drive analogy, district energy, monitoring/observation, and feature flags as the belt that connects product to business. Recommendations: decouple products, design for changeable coupling, accept small fast deploys, and manage technical‑debt like flour dust.
AI-written summary · about
chapters (14)
- 0:00Welcome to Mill City
- 1:14Minneapolis tech hub
- 2:16History of Mill City
- 4:27Flour milling technology
- 8:20Vertical integration lesson
- 10:34What killed factories
- 12:45River still powers city
- 15:55DevOps as belt system
- 17:30Learning from users
- 18:54Technical debt explained
- 21:21Washburn Plant explosion
- 23:41Failure is inevitable
- 25:36Future proofing strategies
- 26:55Key takeaways
related talks
27mDEVOPS DAYS MTL 2018 - Jesse Hurkens
20mModern Organizational Architecture, Are Microservices a Model for Diversity?
39mCommunities are systems: What can systems thinking teach us when it comes to communities?
44m“System of Systems”
38mBringing a multicultural team together
37mBuilding and Scaling Cloud Native Nordics; Tips, Tricks, and Lessons Learned
26mRebuilding Together
45mPanel on Building Communities