Type. Context.
summary
Shows concrete fixes rather than slogans: demonstrates adding forced error handling to a Faraday GET by requiring success and failure procs so callers must handle timeouts; shows using gRPC to compile RPC contracts and eliminate fragile JSON key guesswork; explains Go’s context object for carrying request IDs through logs; notes Google hires thousands of fresh grads which shapes those choices; argues Rails scaffolds work for small teams but require different patterns at scale and points to a real DigitalOcean controller that was mostly scaffolded.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:29Founding a startup is hard
- 0:46tomcat configuration is a nightmare
- 2:28context changes
- 8:44The ideal rails application is a well factored monolith
- 9:52We implicitly created a great ecosystem for those teams
- 13:09Forced error handling
- 13:55Any operation that performs IO can fail at any time for any reason
- 19:18Your codebase reflects your organisation
