Future [Java] Developer
summary
Argues that the key skill is shipping software frequently — cut release cadence from yearly to monthly to daily to reduce bugs — and that containers make that practical by packaging app plus infra so operations treat deployments like moving boxes. Names tools and patterns: continuous delivery, containers, Flyway for DB migrations, Chef (infrastructure as code), Packer to build images and Docker/Vagrant to run them; notes AWS and Google container services and claims this stack makes shipping repeatable and less risky.
AI-written summary · about
chapters (15)
- 0:00Introduction and thanks
- 1:50Future Java developers matter
- 3:36My journey as Java developer
- 11:47From perfectionism to open source
- 17:45Ideas vs execution in development
- 22:23Companies as software companies
- 27:03Stop being perfectionists
- 30:19Continuous delivery explained
- 35:20Practice like a rock star
- 37:28Community and open source
- 44:34Keep learning and innovating
- 47:06Cloud computing and containers
- 55:48Container revolution in software
- 1:00:51Focus on delivery over perfection
- 1:01:59Q&A on continuous delivery
related talks
41mDevOps for Java Developers (or maybe against them?!)
35mDocker, microservices, functional programming (...)
35mJava Developer’s Journey in Kubernetes
46mDevOps for Java Developers (or maybe against them?!)
34mDevOps Tools for Java Developers
53mSuperman or Ironman Can Everyone be a 10x Developer?
51mJava applications containerized and deployed, make your buildpack edition
03h 08mDay 1