Just do IT @ Justid - The Subtle Art of Just Giving a ...
summary
This talk describes practical cultural and collaboration changes used at Justid to improve DevOps work across a government organization: using feedback to learn, modernizing a Jenkins pipeline, increasing deployment frequency from monthly to many times per day (examples include 28 deploys in a few hours), resolving a bug live during a user meeting and questioning branch-heavy workflows (rejecting develop/main branching). It emphasizes that behavioral changes—asking better questions, caring about colleagues, and pushing beyond “that’s not allowed”—can enable faster delivery and better cross-team collaboration even where formal DevOps culture is weak.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:48Main message and psychology
- 9:51Starting at Rabobank
- 12:44Switch to Just IT
- 21:52Pipelines and automation
- 29:17Collaborating with KAP
- 36:04Reducing mental load
- 39:40Purpose and inspiration
- 47:36Tips for autonomy
- 51:27Q&A
related talks
31mNot Actually a DevOps Talk, or, Beyond “Survival is Not Mandatory”
34mYou only have to change one thing to do the DevOps
11mTDD - Trust Driven Development
14mDevOps Speakeasy
54mDay 2 Ask the Speaker
31mThe Continuous Culture
01h 02mWe have DevOps. No one was fired. But what to do?!
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?