From 100 to 1,000+ deployments a day! [Techorama Edition]
At Techorama Belgium, I presented the story of Coolblue, and more importantly, a few examples of what it took for us to go from 100, to 1,000+ deployments a day; a change in mindset, responsibilities and ownership.
… Apparently we are too much trained to disregard differences in scale, to treat them as “gradual differences that are not essential.” We tell ourselves that what we can do once, we can also do twice and by induction, we fool ourselves into believing that we can do it as many times as needed, but this is just not true! ...
... A one-year old child will crawl on all fours with a speed of, say, one mile per hour. But a speed of a thousand miles per hour is that of a supersonic jet. Considered as objects with moving ability the child and the jet are incomparable, for whatever one can do the other cannot and vice versa. — Edsger Dijkstra, 1969
92 @phermens The “100 to 1,000” checklist Responsibility ⬜ Can I control my deployments? ⬜ Have I removed all bottlenecks? ⬜ Do I have good support systems? ⬜ Am I collaborating with my peers? Autonomy ⬜ Freedom to innovate/improve? ⬜ Am I in control and independent? ⬜ Can I find out what went wrong? ⬜ Do I have the skills to fix it? Ownership ⬜ Agreed interfaces or contracts? ⬜ Out-of-the-box solutions? ⬜ Tooling is 100% automated? ⬜ Local build == “Production” build? Failure ⬜ Monitoring = Alerting = Action ⬜ Take pride in improving ⬜ Small deliverables, quickly ⬜ Non-blocking deployments
pheonix25
sugawani
yutoy
fedepaol
asei
minorun365
kojira
optimisuke
bun913
sansantech
otanet
mtx2s
route06
kneath
zakiwarfel
chrislema
ammeep
edds
62gerente
eitanlees
bermonpainter
frogandcode
tanoku
morganepeng
bluesmoon