Archives

Happy Holidays everyone! This is the last DevOps’ish of the year 2021. This month has this year into one that is somehow worse than 2020. I intend to continue the annual tradition of writing down my learnings and expectations for 2021 and 2022. But, looking back, it’s pretty challenging to say what to expect next year. I might land on more upheaval out of necessity. If there is a breakout technology/concept/company you think is about to get big in 2022, hit reply and let me know your thoughts (full credit given; make sure you share a link to your website or social media profile). DevOps’ish for a fresh theme. I’m considering a VERY simplistic version of the website (one designed on this side of the century). It’s a work in progress, but I hope to roll it out over the next week. I want to point out this is in an MVP stage. The final product will look different. But, at its core, I like this theme because it keeps things clean and simple (visually and from a maintainers perspective). Would you mind hitting reply and telling me what you think? ...

For some of us, we need a break. Going at a break neck speed while stretched out mentally and physically is exhausting. I find myself needing a break from at least one of the things I do. Can’t cut out my job; can’t cut out the newsletter. I think until the new year, I’m going to take a break from open source contributions. Expect no open source work from me until 2022 (minus writing because I enjoy that). Log4j dominated the news this week. I was pulling nuggets in for KubeWeekly earlier this week and it literally felt like every other post was about Log4j. I have know lost count of how many CVEs there in Log4j. But, it’s all impactful. Even if your in house systems aren’t based around Java there is likely something in your enterprise that requires log4j and you need to make sure your vanquish this at multiple layers of the stack. People The metaverse has a groping problem already I really hope to avoid the metaverse. ...

Hi all, if you thought last week was terrible, I give you this week. I’m not going to add to the already well-detailed list from last week. Instead, I’d like to celebrate something. Happy Birthday, DevOps’ish DevOps’ish turns five years old today! Max was a year old. I told my wife I was starting a newsletter. Two-hundred forty-seven issues later, we’ve arrived here. This morning, I told Julie, who thought I was nuts at the launch, that DevOps’ish is one of the best things I’ve done for my career. This has paid off on the home front and improved our overall quality of life. I guess this shouldn’t come as a surprise, but the newsletter also enabled MORE charitable giving than before too. Has DevOps’ish been a success? Yes! DevOps’ish at 5 Is the newsletter self-sustaining? Yes. I’ve optimized costs as much as possible. I’ve filled sponsorships as much as I can. The balance sheet is good. The newsletter has pivoted from being a metrics-focused newsletter to being very privacy aware over its five years. I don’t want to know anything about the DevOps’ish readership unless they volunteer it. I don’t track clicks or open rates, and I’m very upfront about that with sponsors. ...

AWS re:Invent was this week. I put a whole section in the notes this week for y’all all about AWS re:Invent. There were a lot of cool announcements this week. There was a scenario where I was going to be there. But, family was getting COVID-19 vaccines the Sunday before, I had doctor’s appointments, and it wasn’t meant to be. Thank the Maker I didn’t end up going. This week has been a nightmare, wrapped in worry, with a big dose of impostor syndrome on top, and I caught a cold too. First, there were multiple family crises. At one point in time my sole focus was on two of my nephews because we needed to watch them at one point with an extra dose of sunshine. Really glad I was here to help and support. Then part of a terror plot unfolded in our front yards. This story is really sad, bad, and preventable. A lot of people failed in their responsibilities and people are dead as a result. It’s a truly horrible situation. Max was home from school for two days this week. Again, glad I was here to help and support. I think everyone in the know was definitely pegged out on the stress meter. Normally, I turn to work to help distract me from stress but, I’m still forming my path. That’s when the impostor syndrome set in (because that’s a totally normal reaction). Thankfully, this video helped with the impostor syndrome. I got the ship righted by Friday. But, wow… This week has been something else. ...

“PLEASE DO NOT ATTEMPT TO SIMPLIFY THIS CODE. KEEP THE SPACE SHUTTLE FLYING.”: This almost 2000 lines of code that make up the persistent volume controller was one of the most popular social media posts this week: 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 // ================================================================== // PLEASE DO NOT ATTEMPT TO SIMPLIFY THIS CODE. // KEEP THE SPACE SHUTTLE FLYING. // ================================================================== // // This controller is intentionally written in a very verbose style. You will // notice: // // 1. Every 'if' statement has a matching 'else' (exception: simple error // checks for a client API call) // 2. Things that may seem obvious are commented explicitly // // We call this style 'space shuttle style'. Space shuttle style is meant to // ensure that every branch and condition is considered and accounted for - // the same way code is written at NASA for applications like the space // shuttle. // Two things struck me about this comment: ...