"Simplicity: The Key to Software Success"
summary
The central claim is that simplicity reduces failure: an architecture is reworked by removing roughly 80% of picked AWS services to convert a sprawling pipeline into a clear flow that ingests public data, applies an ML sentiment model, and renders a dashboard, delivered within three weeks and processing millions of records per day. A practical guideline is the rule of one (add one new thing at a time). Measured goals include shortening onboarding so new hires can clone and run in 30 minutes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:14Picking tech without purpose
- 6:32Complexity causes failure
- 9:23Rule of one for new tech
- 10:45Real-time requirements
- 12:30Case study: Simplifying a system
- 16:09What scalability means
- 19:39Case study: Slow onboarding
- 23:10Documentation rules
- 27:25Case study: Secure onboarding
- 29:10Software as a tool
- 30:14Q&A
related talks
23mDay 1 Welcome Keynote - Simplifying Software Delivery
01h 02mTools for simplified large scale systems
18mTackling tech debt
44mBest Simple System for Now
42mSpeeding Up Innovation
16mFrom Complexity to Clarity
27mGetting traction on your digital transformation
34mMLOPS 101: Tips, Tricks and Best Practices