Link to Post

[Reading time: 2 minutes 13 seconds] Today I had an interesting conversation with a LinkedIn contact, CEO of a company specialising in embedded systems. He echoed a sentiment I encounter very often in embedded systems: “Haha! Applying DevOps to embedded sounds great but 10 years away from now :-) Security, resource requirements, … " I think he made it too easy for himself to dismiss it that easily out of hand, but I suspect he was just trying to bait me into a discussion :-D Read More →

Link to Post

[Reading time: 1 minutes 52 seconds] One of the goals of DevOps is to create autonomous teams. Autonomy comes from being entitled to making your own decisions, and having the necessary tools and knowledge to execute these decisions: not depending on anyone else. The antithesis to this integrated structure is a specialist/function-based department structure: “silos”, in DevOps lingo. To give an example of what I mean: in a siloed organisation you might have separate (say) database, sysadmin, frontend and backend departments, all working together to build a product. Read More →

Link to Post

As I was on a video call today, it dawned on me that we’re stuck in the past’s idea of the future. If you look at futuristic article in a 1950s magazine, it had all the usual trappings: atomic flying cars, smooth bucket seats in living rooms – and video telephone booths. You know, with a regular handset, and a screen, where you could call your aunt to wish her a happy birthday. Read More →

Link to Post

[Reading time: 3 minutes 54 seconds] There’s something that has been brewing in my mind for a while: a different way of looking at software QA. Talking about it is a bit funny, in that it’s subtle. Some of you may read this and find nothing new (and you really might not – I won’t delude myself to imagine I’m the first or only person to have thought of this). Read More →

Link to Post

[Reading time: 1 minutes 36 seconds] Some friends of mine who are doing research similar to mine have independently come to quite similar results: most teams struggle with testing. Be that in nascent fields such as serverless, or old, traditional fields like embedded systems. And I’ve spotted something like that in my DevOps research as well: assuring good software quality it hard. Why is that? Well, part of it is: if you make software quality about testing, you’re doing too little too late. Read More →

Link to Post

[Reading time: 0 minutes 16 seconds] Now that I listened to DevOps practitioners I know even less about DevOps This is a quote from one of the generous people who agreed to an interview for my DevOps research. This may sound disheartening, yet it’s hardly surprising. DevOps is such a wide field, and it’s so ill-defined. It’s not as much problem as it is a warning though: you can’t just look at what others are doing, copy it, and expect great results. Read More →

Link to Post

I’ve been an avid rock climber since before it became cool (disclaimer: the dude in the picture isn’t me. I’m not that cool.) One thing I deeply enjoy about the climbing community is how welcoming they are of beginners. Anyone who’s struggling to make it up a route, regardless of its (perceived) difficulty, will be offered encouragement and helpful advice. Interestingly, newbies struggling to master a particular climb tend to think that they lack the strength to make it to the top. Read More →

Link to Post

DevOps: jetzt mal ehrlich Was ist DevOps? Keiner weiß es. Aber jeder weiß es besser :-) In der Tat rede ich mittlerweile von Rorschach’s DevOps: ich sage “DevOps”, und Du verstehst darunter, was Du willst. Um so interessanter ist es, herauszufinden, was andere auf diese Fläche projizieren. Durch meine Arbeit als DevOps Trainer und Coach habe ich viele Eindrücke und Bauchgefühl dazu gewonnen – aber das geht bestimmt auch noch besser. 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