Engineering Innovation - why constraints are critical
summary
Argues that enforced limits enable practical innovation by example: encore enforces a single API, cron and pubsub definition so the system can generate architecture diagrams and provision infra automatically; shows how Go 1.10 test caching relies on an internal testlog that records file and env reads so caching is correct; claims adding methods weakens abstractions and that recent generics increase Go complexity; recommends preferring concrete, language-standard constraints over premature, broad abstractions to unlock tooling and UX gains.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:56SOFTWARE INNOVATION
- 7:02BACKEND INNOVATION
- 13:33WEAK ABSTRACTION BAD?
- 16:17ABSTRACTION IS A TOOL.
- 19:21ENCORE CONCEPTS
- 19:50GO TEST CACHING
related talks
34mAdvanced Testing Techniques in Go
26mGo is Boring... And That's Fantastic!
37m"Using Golang for Platform Engineering"
29mThink Pragmatically: Elevating Your Go Development Skills
45mThe Robustness of Go
37mOpening keynote: Clear is better than clever
48mClear Is Better Than Clever - What Makes Go Stand Out
18mA case for microservices