The Cloud Native Diabolical Developer
summary
Argues that modern cloud native stacks and DevOps tooling more often chain developers than free them, naming Docker, Kubernetes, Helm and Terraform as sources of repeated failure and opaque errors; warns of cloud lock‑in and unexpected autoscaling costs after a trivial Hello World microservice overloads; recommends practical moves like defend your monolith, favor clear, well documented code, treat CI/CD complexity skeptically, and only adopt microservices where scale truly demands it.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:05Modern Software Development
- 10:23Software Craftsmanship is an attitude
- 11:15Practical Tips
- 21:49DevOps
- 34:58Containers
- 42:01PACKIT
- 42:37Conclusion
related talks
28mUnleashing Innovation by Unblocking your Developers
44mNine Ways To Fail at Cloud Native
42mCloud Native Applications
59mCloud Native Culture
06mMake Workloads, Not Infrastructure
25mBuilding APIs in a Cloud Native era
35mCloud Native Development Without the Toil
31mCloud native: the cattle the pets and the germs