What happens when Unicorns drink coffee?
summary
Argument: enterprise developers spend most time on infrastructure not business logic, with Java shops stuck on Java 11 constrained by customers and teams often owning hundreds of services; complexity explodes over ~15 years while one project scale hit a 200‑person team and caused burnout. Proposes a unicorn approach that reduces plumbing: demoed container/Kubernetes workstreams, recommends OpenShift and odo restores local dev flow as a fix, and claims Quackus injects developer joy by cutting YAML and config drudgery.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:00Java
- 3:35Developer adoption
- 7:35Introduction
- 14:17My kids
- 16:34Horse evolution
- 18:25First internet connection
- 21:41Middle horse
- 24:14The remnant horse
- 29:34The modern horse
- 32:50The modern horse today
- 35:28The evolution of software development
- 38:41How to build solid modern applications
- 39:29Software development life cycle
- 41:07Modern horse
- 46:14Unicorns
related talks
33mThe Unicorn Project And The Five Ideals
31mEnterprise DevOps and Unicorns
46mImproving Software Flow
28mUnleashing Innovation by Unblocking your Developers
47mImproving Software Flow
52mUnicorn's baby steps: what should you know as a 1st-time startup CTO
01h 12mArchitecting and delivering Java applications in the cloud era
49mHypergrowth scaling made simple