What DragonBall can teach us about being engineers
summary
Argues concrete engineering lessons through DragonBall analogies: the cloud speeds progress but won’t magically lift legacy mainframes, capsules are literal lessons in Docker containers and ephemeral scaling, recommends Terraform and YAML practice as part of relentless training, and endorses Kubernetes style platform thinking. Advocates shipping an MVP and iterating toward a “golden form,” using targeted monitoring instead of dumping everything into a 7 TB S3, treating failures as recoverable (resurrection), practicing pair programming, and protecting sleep and rest.
AI-written summary · about
related talks
29mHow to Train Your Dragon
37mDungeons, Dragons & Developers
46mWork It Smarter, Dev It Better, Ship It Faster, Test It Stronger
37mDungeons, Dragons and Developers
19mScaling Fast – Engineering Lessons From ~15 Years of Tech Startups
34mThe Return of the Dull Stack Engineer
08mWhat Stan Lee taught me about working in tech
05mClouds, Code, and Confused Grandmas: Building Your DevOps ‘House’ in 5 Minutes