DevOps’ish is back.
What did the hiatus look like? Why did it need to happen at all?
Like fixing an airplane while it’s in-flight, It’s hard assessing a problem while you’re in the middle of creating it. COVID-19 is just the sort of thing that the world turned upside down enough that I needed to take a break to reassess how to do the newsletter, in general. Meanwhile, sponsorships wholly dried up (for five weeks).
Read more →“We should take comfort that while we may have more still to endure, better days will return. We will be with our friends again. We will be with our families again. We will meet again. But for now, I send my thanks and warmest good wishes to you all.” -Queen Elizabeth II
As mentioned last week, the newsletter is going on a hiatus. I’m not sure for how long, but it will be a while.
Read more →Next week’s DevOps’ish (177) will be the last DevOps’ish for a while. I’m going to be putting DevOps’ish on a COVID-19 hiatus. A large part of making this newsletter is reading the news every day. Even with very heavy-handed filtering, the amount of data I read about the ongoing pandemic is far higher than one should be consuming. I’m pausing DevOps’ish because the news is hard to read these days.
Read more →I was going to make a list of things you could learn this week but, the tech world got a notable call to arms this week. We need more COBOL developers in the US. The glut of unemployment claims has crippled mainframe systems designed to run in a satisfactory government manner under normal conditions. “The governor of New Jersey just put out the call on live TV that he is desperate for Cobol programmers right now.
Read more →There was some discussion in the DevOps’ish Telegram about what the topic of this intro should be this week. One suggestion was excellent; I’m probably going to run with it next week. But, I understand that there are some of you looking for something to learn while we’re in this odd time. I wrote this week’s newsletter with that in mind. If you don’t know git, now is the time to learn for sure.
Read more →The impact of the coronavirus hit the tech events industry hard this week. In a shocking move on Tuesday, O’Reilly announced it has immediately ceased all in-person events. To add insult to injury, O’Reilly laid off their entire events staff during a pandemic. To make matters worse, under US law, they’ll get only a week of health insurance benefits, meager support for COBRA (super expensive health insurance), and any severance is based solely on tenure.
Read more →There is a line in Saving Private Ryan about griping. There’s a chain of command in the military and leadership voices its concerns up the chain, never down it. This week, I’ve been reaching up my chain of command in government to make sure that the people that are supposed to be leading right now are. I would encourage you to do the same. Some good news this week is that after announcing an initiative to harness a global computer network to contribute work towards pharmaceutical drugs to combat COVID-19, Folding@Home has seen a 1200% increase in computers actively contributing to the project.
Read more →In dark times, there are typically rays of light that can be found to give us hope. I read an article last weekend that I thought would be worth mentioning here this week. Will the coronavirus crisis, like Sars, give birth to the next big thing in China tech? looks at how the Chinese e-commerce giants Alibaba and JD.com got their start during the SARS crisis of 2002-2003. The coronavirus caused markets to tank this week.
Read more →Everything is canceled, postponed, or going virtual. Coronavirus (COVID-19) has already made drastic impacts across the planet. Particularly this week, when several companies restricted travel forcing conferences to do something if they hadn’t already. KubeCon EU is getting pushed back to July or August. I canceled my plans earlier in the week because, with everything up in the air, there’s no telling I’ll be available to participate whenever it does eventually get rescheduled.
Read more →The first CNCF Air Gapped Working Group meeting happened this week. I was fortunate enough to be able to attend. Air gapped or disconnected environments have a few variants. But, the air gaps I’m most familiar with are those between unclassified and classified US government systems (TEMPEST, EMSEC, COMSEC, etc.). Also, given the attendance, there is a lot of interest from folks across the public and private sectors. If you’re interested in getting involved, we’re figuring out what the cadence of the meetings will be.
Read more →