The missing parts of scaling up DevOps are often involving compliance, security, and most importantly, leadership actually changing and getting more hands on themselves. Check out more in this guest column of mine.
LaserWriter II. This is a book about a Mac repair shop in New York in the 90s. I mean, like, it’s just that. It’s great!
I’m almost done reading (well, listening to - the best way for these) the Wooster and Jeeves books. I read Ring for Jeeves recently. It has no Wooster and so is a little odd, plus, a new cast of characters.
“As far as what’s actually written in my diary is this: imagery from dreams, all of my worries, streams of consciousness, fragments of poetry, gratitude, and descriptions of moments I wish I could live in forever.”
“Developers don’t need to be experts in Kubernetes, but they should be proficient in skills that can impact the performance of their applications. Skills such as CI/CD, deployments to production, monitoring, and understanding CPU, memory, and cluster and pod health are vital pieces of the application puzzle.”
Developers don’t actually want to change the batteries. “What you actually want a Kubernetes dev platform to achieve is to enable developers to directly interact with Kubernetes while they do not necessarily have to configure anything. This can be done by providing smart defaults that can be fully customized and adapted. Optimally, developers can then work with Kubernetes without ever having to configure anything but knowing they could if they needed to.”
“Developers don’t care how many replicas of their service are running, or what Roles it has, or whether it’s running via StatefulSets; all they care about is getting an HTTP endpoint up that helps deliver a product. As a result, some operators choose to hide Kubernetes inside the CI/CD pipeline. Devs don’t get bogged down by k8s minutiae; they simply push code to GitHub and the rest is taken care of for them…. Even if developers are fluent in Kubernetes, operators may be reluctant to give them unfettered access to a cluster, since small changes can have outsized ripple effects. (For instance: changes to resource limits for a Pod or Container could cause issues with other deployments that are scheduled to the same nodes.)”
‘But there are also hard data. In mid-October, the U.S. Bureau of Labor Statistics announced that 2.9 percent of the American workforce quit their jobs in August—that’s 4.3 million people. A few weeks before the BLS report, Slack’s Future Forum (a research group inside the company that has dedicated the last year-plus to studying remote work) published their most recent report. They surveyed 10,569 knowledge workers internationally and found that, “more than half of knowledge workers—57%—are open to looking for a new job in the next year. And for those who aren’t satisfied with the level of flexibility they have in their current role, the number is substantially higher (71%).”… The report also highlighted a troubling discrepancy between executives and employees in terms of job satisfaction and post-pandemic workforce policies. “75% of these executives say they want to work from the office three to five days a week, versus only 34% of employees,” the report found.’
Also, I put together a playlist of all my tiny videos. I started making them 18 months ago, which is a crazy time span to think of. It seems longer ago, pandemic and all that. Watch them all, ten times each!