I wrote a really good introduction last week and forgot to include it in the email newsletter. It is still on the site if you’d like to go back and look at it. The three big takeaways are: My traditional end of year blog post is out (as of today): 2021 Learnings, 2022 Expectations. I put a lot of time, effort, and thought into it. I hope it’s coherent enough so that you can plot a course in 2022. DevOps’ish.com has been completely redesigned from the ground up to provide a better reading experience. A sorely missing and incredibly helpful search capability has been added to the site. Honeycomb will be the sole sponsor of DevOps’ish in 2022 and I’m very excited about that. Last week’s issue might have been one of the worst performing ones of the year. The lack of an intro left folks wanting more. Next year (2023), I’ll plan better and not push out newsletters during significant lulls in internet activity. Plus, I can plan to take a break every once in a while (this isn’t a marathon; it’s a newsletter). ...

Happy New Year! 🎉🥳🎊 I wish you the absolute best in 2022. I’m still in the process of writing my annual learnings and expectations blog post. Please keep your eyes peeled for that to drop on ChrisShort.net in the coming days. Feel free to subscribe to the RSS feed if you’d like. Also, if you’re not reading this on the web, check out the new coat of paint applied to DevOps’ish.com. I like the search functionality I implemented which was sorely missing previously. The site is very lightweight and performant now. Let me know if you see any problems. In great news for the newsletter, Honeycomb will be the sole sponsor of DevOps’ish in 2022. Working with Honeycomb has been an absolute joy and their leadership team 100% supports the work being done here. Do me a favor and give Honeycomb serious consideration for your observability and telemetry needs in the future. “Guess less. Know more.” As it is a new year and there are likely many new subscribers unaware, I maintain many what I call “helper sites” designed to get you up to speed and keep you informed (pull requests welcomed). I’ll list them here for your benefit: ...

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. ...