The people in my tech community who talk about community find Twitter so vile that there’s little discussion of the good parts. It was a great place for discovering, building, and “doing” community. And it still is, though mixed in with all the other stuff1. This history of DevOps, cloud stuff, and everything that followed - open source, even! - would be different if Twitter weren’t around. We’d be in…listservs? Blogs?

Early on in the life of a new open source project, some vendors will tell you it’s too complex and unreliable, and wrap their fixes on top of it, often hiding the project. They’re not wrong (early in, most OSS projects are literally not even 1.0 projects yet!), but it’s rhetorically risky strategy. With the early adopters, you have to show how you make it better and are evolving the project without hiding it.

I've proposed an open spaces for DevOpsDays Amsterdam, 2021. The idea is: The DevOps community pushes for people to change how they think and operate. When it comes to working better, we have proven tools, techniques, and even big picture ways of thinking like CALMS. You’re more than likely eager to try these new things, get better, change. However, many more people seem less than eager to change - your co-workers, managers, and the countless “others” in your organization.

Notes: central is thinking about product features, not business. The business funds the product, the customer value - it's the McGuffin that you careful guide to being cash flow. The question here is to find other org.s that have adopted abs adapted the practices successfully, or not. the advice at the end is pretty straightforward - the practices are kind of simple, so applying them just means deciding to do them - just like deciding to diet and exercise.

If you wish to make an apple pie from scratch, you must first invent the universe. Carl Sagan. In most enterprise tech marketing copy, it’s an anti-pattern to do the whole “you must first invent the universe” thing. Buyers and curious people already know that there’s market headwinds, things change faster than ever, new technologies, etc. They want to know exactly how you solve the problem, not that it exists.

For those RSS-nerds of you out there consuming this, I’d like to point out that most of my “blogging” is done in my newsletter now. I send it out once or twice a week as a collection of links, fragments of stuff I’ve written (usually some original, newsletter only content thereof), and otherwise wunderkammer like stuff. Here’s the past three ones if you’re curious: A fake simulacrum. Workaholic. Leading failure.

For those RSS-nerds of you out there consuming this, I’d like to point out that most of my “blogging” is done in my newsletter now. I send it out once or twice a week as a collection of links, fragments of stuff I’ve written (usually some original, newsletter only content thereof), and otherwise wunderkammer like stuff. Here’s the past three ones if you’re curious: A fake simulacrum. Workaholic. Leading failure.

According to the confidential memo, Oracle's routine tactic is to threaten based on incompliance and to maximize potential licensing issues. After that, software licenses and the looming costs of such licenses can be negotiated from such a beaten problem. The result can then be a relatively better than expected amount for the shocked customer, but is not a low amount. Source: ‘Rijksoverheid al 4 jaar in de clinch met Oracle’

According to the confidential memo, Oracle's routine tactic is to threaten based on incompliance and to maximize potential licensing issues. After that, software licenses and the looming costs of such licenses can be negotiated from such a beaten problem. The result can then be a relatively better than expected amount for the shocked customer, but is not a low amount. Source: ‘Rijksoverheid al 4 jaar in de clinch met Oracle’

Published in the Computers in Human Behaviour academic journal, the study enumerates no fewer than 72 actions that people apparently take while managing their work emails. We can count five – delete, mark as spam, forward, reply and read but ignore – and can only imagine that reaching the figure of 72 must include crying and rocking in the corner of the office while reading the full contents of one's inbox.