Link to Post

[Reading time: 2 minutes 21 seconds] Bullshit. “The law of conservation of bullshit” Call me childish, but it’s all I can do not to cackle with glee at that expression. It’s kind of what’s behind many rules or observations about organisation and team size. If you’re just a handful of engineers, sharing information is not so difficult. Everybody gets together and communicates naturally. Information flows as though on its own. Everybody knows everything that’s going on. Read More →

Link to Post

[Reading time: 2 minutes 1 second] A few days ago, I wrote to you about how everything is connected in DevOps. Remember this picture? +--------------+ +--------------+ | | | | | Culture | <--------> | Technology | | | | | +-------------++ ++-------------+ ^ ^ ^ | | ^ | +--------------+ | v | | v v v +-------------++ ++-------------+ | | | | | Practices | <--------> | Goals | | | | | +--------------+ +--------------+ Let’s take a look at one of its juicier aspects today: Culture vs Technology. Read More →

Link to Post

[Reading time: 56 seconds] I’m really proud of my newest metaphor: the DevOps Ratchet. Let me tell you about it :-) Today, I was conversing with an engineering manager about how to introduce DevOps to an organisation. We discussed several typical pitfalls I had observed, and also approaches that I found to work well. As I’ve mentioned before, my preferred approach is to burn the candle from both ends: introduce new tools and technologies, and at the same time establish a conversation about culture and the changes to it that may be necessary. Read More →

Link to Post

[Reading time: 2 minutes 33 seconds] Among climbers, there’s a thing called Crux of a route. It’s the make-or-break section of that route: the hardest part, whose conquest decides whether you send the route, or end up catching air. As I’m creating a new workshop on DevOps for seasoned Agile practitioners, I’ve been forced to think about the shape of this thing I call DevOps. I can see something emerging in my mind, but I can’t quite tell yet what that shape will be. Read More →

Link to Post

[Reading time: 1 minute 14 seconds] I’m talking of DevOps adoption of course. There are many smart books about it, such as the famous DevOps Handbook or the excellent Accelerate. They are supremely good, powerful books. They tell you everything you need to know. …except they don’t, do they? I think one of the more insidious problem these books have is that they’re too good. Things that you intuitively know to be hard, they make sound simple. Read More →

Link to Post

[Reading time: 2 minutes 3 seconds] Imagine you said this to somebody: “All you’ve done over the last decade was completely wrong”. …whoa, hold up. How dare you say that to an accomplished professional? That’s a pretty harsh thing to say, isn’t it? And it’s so harsh, it’s actually rude. You know what: I’ve had people think I said that to them. I’ll be honest: I’m far too bad at confrontation to say such a thing, even if I meant it. Read More →

Link to Post

[Reading time: 1 minutes 41 seconds] No two organisations are alike of course – but here’s a playbook that has worked well for me. Fundamentally, there are two things you need to balance: the need to offer clarity on the philosophical underpinnnings of DevOps: what the fundamental considerations and goals are the need to take concrete steps, actually build something, get your fingers dirty, collect immediate experience The second – concrete steps – is important because engineers are an impatient bunch. Read More →

Link to Post

[Reading time: 1 minute, 48 seconds] Predictability is important, OK we get it. But how do you achieve it? Amusingly, many people seem to start with step 2: doing something about it. How about we start with step 1 instead: figuring out what makes predictability. What makes you feel safe, confident, protected? There are many sources of predictability, or unpredictability: your coworkers your processes the technology that drives the processes your organisation …and: yourself But all of these elements can be subsumed under the process itself: because what is a process but an agreement to transform something into something else. Read More →

Let's Get In Touch!


Do you have a question? A project proposal? Something special in mind? Contact me, and let’s talk about how I can make your team, your products, and your life better