VSHN.timer #153: When Dev and Ops Collide

Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.

This week we’re going to talk about the various ways in which DevOps can collapse under its own weight, and what teams can do to avoid those traps.

1. Is DevOps really a good idea? This is the question many teams around the world are asking themselves. They realize that developers didn’t want to deal with operations and infrastructure, to begin with. Scott Carey argues that the time has come to rethink how to do DevOps… if at all. (German translation by Computerwoche.de)

https://www.infoworld.com/article/3669477/devs-don-t-want-to-do-ops.html

2. The Harvard Business Review published its first article openly advocating for empathy and understanding between team members and across hierarchies… in 1952. 70. Years. Ago. Are we there yet? This groundbreaking classic deserves to be read (or re-read) by all engineers and managers, Dev and Ops alike.

https://hbr.org/1991/11/barriers-and-gateways-to-communication

A superpower everyone should develop: Copywriting.

Amazon, the second most valuable brand in the world, puts an emphasis on teaching its employees how to write.

Here are the 9 tips to write like an Amazonian:

— Alex Garcia 🔍 (@alexgarcia_atx) August 12, 2022

3. Too many meetings? Too many back-to-back meetings? You’re not alone. And you’re also in trouble, even if you don’t realize it. Teams all over the world are in charge of sensitive systems but not of their own schedules or quality processes. Such a situation is a time bomb waiting to explode, as explained by Tom Lingham.

https://tomlingham.com/articles/why-are-you-so-busy/

4. In the past decade, businesses of all sizes increased their cloud usage dramatically; in many cases, exponentially. But where are the cost reductions promised at the dawn of the Cloud era? Why aren’t companies monitoring their spending with FinOps? David Linthicum, Cloud Strategy Officer at Deloitte, explains the three main reasons why.

https://www.infoworld.com/article/3670851/3-reasons-cloud-computing-doesnt-save-money.html

5. What happened to sysadmins? How do new engineers learn the nuts and bolts of Linux system administration in these days of serverless and DevOps and microservices? Matt Rickard asks the right questions, as usual.

https://matt-rickard.com/the-lost-art-of-systems-administration

Do you do FinOps? Have you adopted DevOps in your organization, or have you found that it doesn’t really work? Would you like to tell us more about how you organize your development and operation teams? Get in touch with us, and see you next week for another edition of VSHN.timer.

PS: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.

PS²: do you prefer reading VSHN.timer in your favorite RSS reader? Subscribe to this feed.

PS³: check out our previous VSHN.timer editions about DevOps: #5, #13, #29, #31, #42, #110, and #133.