Here’s two things of mine to check out:

What we do at my work

We broadcast our updated Tanzu overview yesterday. I MC it and do a Q&A session at the end. I tried to get a lot of my views of the platform engineering, what we do, build vs. buy, and the usual stuff in through my questions and the intro and outo parts. It’ll give an idea of what people do with our stack, you know, when it comes to building, running, and managing their apps. You should watch it!

Making Big-Ass D&D Maps with Generative AI

The second thing is a write-up of how I use Midjourney to make D&D battle maps. I even broke my 15 year hiatus and posted it on reddit.

I have a lot of pent-up material and commentary on how I do solo role-playing with ChatGPT (and other AI stuff). The problem in writing it up is that the time I spend writing it up is the time I could use to actually play. Maybe the “just start a live stream and push record as you play” option is what I need to get back to.

It’s fun re-entering this D&D world after (checks calendar) 33 or 34 years. I usually don’t like learning things new, let alone “on the Internet” because I really dislike the shame of being, like, ignorant and wrong. (Probably the number one reason I haven’t learned Dutch after 5 years living in Amsterdam.) But, with D&D, there’s a good mix of fun and safety when it comes to D&D. I don’t know if I’ll ever re-build the desire to play with a group of people, but, you know, it’s fun even being a learning-lurker in that world. For example, while there’s only a few replies to that post, there’s good suggestions in there that I’m excited to try out: better to overlay your own grid, and try out img2img. Learning doesn’t have to be shameful! It can be fun!

If “The Internet” has been one of my life-long obsessions (ever since that first day I logged into an AS/400 and starting typing up HTML files), then D&D was a very strong one before that. Mix the two together, and it’s a good stir-fry.

Anyhow! Check out some fun map making with AI.

Relative to your interests

Pile of AI stuff on-top here, mostly “enterprise AI.”

• AI - two reports reveal a massive enterprise pause over security and ethics - A preview of the next 3 to five years of “enterprise AI” as it nears then skis down peak of inflated expectations: “When we go into a CIO discussion, it’s ‘How can I use Gen-AI?’ And I’m like, ‘I don’t know. What do you want to do with it?’ And the answer is, ‘I don’t know, you figure it out!’”

• Don’t Get Canceled: How To Overcome GenAI Consumer Backlash - I am interested in enterprise AI governance and policy. I’m not even sure what that is! But what does security, audit, and governance look like for AI? What is DevSecOps, secure software supply chains, all that type of thing for enterprises using AI?

• CMOs Must Protect Consumer Trust in the AI Age - “only 20% of consumers are comfortable with businesses incorporating the use of GenAI into their operations, according to a survey by Gartner.”

• Americans increasingly using ChatGPT, but few trust its 2024 election information, Pew Research Center - Techmeme summary: “A survey of 10,133 US adults: 43% of those aged 18–29 used ChatGPT in February 2024, up from 33% in July 2023, compared to 27% of 30–49 and 23% of all adults”

• About Placemark.io - Is there room in the TAM for a startup like me? Seems representative of starting a software-business, there needs to be room in the market, a chance to make it big: “As I’ve said a bunch of times, the biggest problem with competition in the world of geospatial companies is that there aren’t many big winners. We would all have a way different perspective on geospatial startups if even one of them had a successful IPO in the last decade or two, or even if a geospatial startup entered the mainstream in the same way as a startup like Notion or Figma did. Esri being a private company is definitely part of this - they’re enormous, but nobody outside of the industry talks about them because there’s no stock and little transparency into their business.”

• Stop Chasing Unicorns - ‘When it comes to ways of working, what do the companies that beat you in deals do better product, design, and engineering-wise?" Silence. "Do they do better discovery and research, ship higher quality work, run more experiments, kill bad decisions faster, retain passionate team members, or have a more effective org design?’

• Skinny jeans hot for AW24? Two writers argue over the demonised drainpipes - Some real passion about skinny-jeans here: ’at least with skinny jeans there’s no chance of soaking up every puddle you slosh through on a rainy day, until the water reaches your knee and you develop a very real chance of developing trench foot. ’

• Redis vs. the trillion-dollar cabals - Defending yourself against the three public clouds.

Wastebook

• “Credit card issuers, when they screw this up, lose millions of dollars and dry their tears on money.” Here.

• Your cattle are my pets. Talk Theme.

• “Random acts of marketing.”

• Damnit, Jim. I’m a marketer, not a product manager.

• “We’re gonna need some more budget. No more Doritos for the rest of the FY.”

• “You fight like a dairy farmer!” (Example used by Gemini for something you’d have time to say with your free action in D&D 5e combat.)

• “Relative dearth.”

• “You’re pushing a rock [up a hill] that’s never gonna love you.” RoTL, #530.

• “Between you, me, and the microphone…”

• Living the dream: “Pelia related that what she found most challenging about her long life span was not the loss of friends and loved ones to time, but instead, boredom.”

Conferences, Events, etc.

Talks I’m giving, places I’ll be, and other plans.

Tanzu Defined online, April 3rd (watch the replay!), The Internet. TEQNation, May 22nd, Utrecht, speaking. DevOpsDays Amsterdam, June 20th, speaking. NDC Oslo, speaking, June 12th. SpringOne, August 26–29, 2024.

Logoff

Tomorrow’s Software Defined Talk podcast episode (“not illegal, works as designed”) is fun - we recorded it last night if you want to watch the unedited video instead of normal podcast-ery. Or, just subscribe to it and you’ll get it ready for your dog-walking, dish-washing, commute, or as good background noise for making your kids lunches in the morning. Those are the only sanctioned times to listen to the podcast, by the way.

Bye!

Relative to your interests

• Sometimes, Lipstick Is Exactly What a Pig Needs! - Abby Bangser, Syntasso & Whitney Lee, VMware - How can you start to take a design/UX-driven approach to building your platform (you know, your pile of Kubernetes stuff to pull it all together for app developers)? Whitney Lee & Abby Bangser have a good mind-model to think about designing the interfaces (how people use parts of that stack). Thinking through how you design your platform “interfaces” for app developers is especially important if you’re building your own stack instead of buying one of the already integrated ones.

• “Designing for Success: UX Principles for Internal Developer Platforms,” Kirsten Schwarzer, KubeCon EU, March, 2024. - Good tour of applying design-think to platforms. That is, what do designers do on platform engineering teams. Some items: (1) Do at least one hour long user interview a week. This gives you an idea of what your users (developers) are doing, struggle with, how your improvements are helping or not, and give you data to decide what to do next. The last is especially useful for fending off The Boss and others who have suggestions that are not helpful: show them the data about what is, at least that you do things driven by analysis, not hunch. (2) Progressive disclosure - only show what people need for a given talk, not everything the tool can do. Can help with cognitive (over)load. (3) Errors are a good source for finding what’s wrong.

• “Boosting Developer Platform Teams with Product Thinking,” Samantha Coffman, KubeCon EU, March 2024. - A lot of good commentary and advice on product managing the platform, some techniques, mindsets, etc. Chief among them: focus on the value/problem you’re solving first, then how you solve it second…also trying to quantify what the problem is so you can measure if it’s fixed, and prioritize it.

• State of Platform Maturity in the Norwegian Public Sector - Hans Kristian Flaatten - If you’re interested in how the Norwegian government is using cloud native stuff (like Kubernetes), this is a survey readout circa 2023/2024. The Q&A section is pretty great for walking through the usual concerns for a platform, especially compliance/governance.

• Ex-technology companies. - “Organizations that spun up dedicated in-house build and deployment infrastructure have fixed engineering costs to maintain that infrastructure, and the math that convinced executives earlier–some sort of argument about the multiplicative effect on the impact of other engineers–doesn’t make as much sense anymore. But often you can’t just stop maintaining those investments, because that would require slowing down to decommission the existing systems, and ex-technology companies have little capacity for maintenance. Instead they’re focused on survival or roleplaying the motions of rapid product development despite actually spending the large majority of their time on maintenance.” // This is pretty great! Finally, a business strategy model for deciding build vs. buy. Look at the costs of building, running, and maintaining your own stack over (whatever, let’s pick a number) 3 to 5 years. Is it higher than buying, assuming revenue is single digit growth? Put another way, with software, it’s the maintenance that kills your numbers. // Also, to ponder: “They no longer believe they can change the business' outcomes through R&D efforts, and as a result they shouldn’t include engineering as a major stakeholder in business decisions.”

• “Analogpunk, or, Tools, Shoes and Misery,” Bruce Sterling SXSW 2024 - He has a skill for turning mundane objects into lectures and relating them to culture. Put in direct link to MP3.

• How B2B Organizations Can Win With Younger Buyers - What the kids are up to. This feels like a description of youth of all generations. As the kids age in power, they both get tired, have their own kids, or otherwise just get tired and want to delegate, have help, or just coast. Until then: so much energy! So much flat hierarchy! So much energy! So much caring!

• Untranslatable - “We’ll let him do a trial run for a week first, to see what kind of meat we have in the tub.”

• 101 things I would tell my self from 10 years ago - “You are high in neuroticism, a trait that correlates with worse social relationships and an unhappier life. Sorry; there’s not much you can do about it other than be aware of it. Its saving grace is that it means you are attuned to what is wrong in the world and driven to fix it.” // Typical listical, but, sure, some fun stuff.

• The Justice Department Accuses Apple Of Smartphone Monopoly - ’When you’re as big as Apple, there’s a target on your back. The company’s market capitalization flirts with three trillion dollars, but more importantly, it commands a resounding 60%+ share of the smartphone market in the U.S. Therein lies the rub – our phones are the primary portal into how we live every moment of our waking (and sleeping) lives. What Apple chooses to allow or disallow has outsized implications for every provider hoping to get in through the portal and play a role in the digitally addicted lives of American consumers.’ And: “Apple’s obsession with its customer experience leads it to control the experience tightly, make decisions on its customers' behalf, and maintain an ecosystem that consistently delivers on the experience the brand promises. That philosophy limits choices for consumers. To that end, there is no dearth of people who are irked by this handcuffing and choose not to frolic in Apple’s walled garden. Then there are others who are part of the Apple family precisely because of the carefully managed ecosystem’s ease of use and intuitiveness.”

• A few thoughts on the Apple DOJ antitrust case, from someone who isn’t riding his first rodeo - “In organisations that are under antitrust pressure, ideas that might get put forward are held back, because people would rather not spend the time having them checked through legal and compliance teams. Acquisitions which a company might make don’t happen, because it would rather not appear rapacious or that it’s stifling nascent competition. And contractual clauses with partners can’t be as aggressive in locking them out of doing business in a way which doesn’t favour you.”

• AI means it’s Springtime for open source, says CNCF - “Bold words, alongside a prediction from the keynote stage that the cloud-native development market will be worth $2.3 trillion worldwide by 2029, up from $547 billion in 2022 – a 320% increase in less than a decade.” // Seems like a lot, especially when IDC forecasts the Kubernetes (“Container Infrastructure Software”) market to be $5.56bn in 2027. But, if you look at the CNCF “landscape” is basically all of infrastructure software now (a rewrite of the existing stack used to run applications), I mean…sure?

• From Here to GitOps and Back Again - GitOps as a feature of CI/CD.

• How People Are Really Using GenAI - It makes jargon-based work more accessible, and complex things easier to understand. Also, just some everyday uses. And: an alternative to the garbage filled results you get from search, a way to filter the Internet. // “just 10% use ChatGPT which enjoys 60% market share regularly”

• Late Night With the Devil: why people are boycotting the indie horror - “I’m not going to boycott an indie movie and the work of everyone else for what amounts to 20 seconds of AI title cards, because that doesn’t help artists either”

• Exit, Voice, and Loyalty - “The Exit, Voice and Loyalty model states that members of an organization, whether a business, a nation or any other form of human grouping, have essentially two possible responses when they perceive that the organization is demonstrating a decrease in quality or benefit to the member: they can exit (withdraw from the relationship); or, they can voice (attempt to repair or improve the relationship through communication of the complaint, grievance or proposal for change).”

• First custom brand font for TJ Maxx built by McCann Design - ‘The Maxx typeface has a family of four weights and is apparently “chock-full of little gems in the Open Type features”. Typing out two X’s will bring up the option of the famous XX ligature that appears in the logo. There are also alternative shorter glyphs for the I and J, “to close the leading more naturally in tight typesetting”.’

• Battle of the Redis forks? - Commercialized open source is a mess right now…for the past ₃ years. Like other types of software, cloud has really been, uh, “transformative.”

• Content Editing: How To Handle Major Rewrites - Pretty detailed guide to editing (corporate) content that isn’t good enough.

• Platform Maturity Model with Abby Bangser - Good framing: providing internal (dev) services to internal (dev) customers. (Abby has been doing a great job, devrel wise, in the past year+.)

• The Unbundling of ChatGPT (Feb 2024 Recap) - AI is a feature, not a product.

• KubeCon + CloudNativeCon - if you build it, your customers might not come. Why? - Platform as a product!

We’ll tell you what’s up with my work now. All the cloud, platform engineering, Java, development, cloud native, yadda-yadda you know you like stuff. April 3rd, coming up soon! You can watch in LinkedIn or YouTube. Register (for free!) at one of those two and you’ll get notified when it’s started and reminded after it happened.

Wastebook

• “Full Stack IT Elimination.”

• I’m sorry for your loss/thank you for your service/thank you, please drive through.

• “toddler-led walks” Here.

• “Richard Stallman, too. He is our hero. Stallman does not visit our Brain Dump hackerspace, because he refuses to use Google Maps on principle.” bruces.

• “I don’t believe in most recycling. I may believe in recycling cans, though I know it takes much higher heat to smelt. I may believe in non-intermingled paper pulp recycling. I may believe in glass recycling. I say may believe because I don’t know enough about it. It is possible it is all a sham. I do believe in French wine and the money it requires to buy it so I took a load of cans to my local recycling center on the way home from the swapmeet.” Coco’s Dispatch.

• “It’s so quiet, I can hear my hair grow.” Here.

• “Judy says the problem with lentil loaf is the word ‘loaf.’” Alex.

• “not an expert on the day of the week.” RoTL, #530

• “Essentially, level five is utopia.” Cloud Native Maturity Model.

• She is the only person who is more me than me.

Korean-flavored, American Soul food sold in the Netherlands, delivered by Internet-enabled courier. Back when my peers were throwing bricks into McDonald’s windows, they had no idea what was hurtling towards them - some real cyberpunk shit, man. Now, we’re the ones ordering this stuff. Plus: it’s damn good chicken. Their Korean chicken-fried cauliflower is amazing too.

Logoff

The solo D&D with AI has been rocky of late. I’ve hit the problem of the AI not being able to move to the next action. It lingers on a sort of “what will happen next?” cliff. Instead, I’m looking for it to take that active roll of moving the plot forward that a DM would.

I’ve been looking at the Plot Unfolding Machine (PUM) for some inspiration. It seems to be built around this problem in solo role playing. Instead of the usual oracle mechanics, injecting random plot twists, and inspiration for the solo-player coming up with a new story…PUM tries to get closer to saying exactly what happens next.

Also, I’ve tried Gemini Pro (I have a two month free trial). I don’t have the ability to upload files (because I’m on the EU…or just can’t find it), which is very limiting: you have to start all over. I thought the huge context window would help, but I’m not sure.

All in all, I haven’t been able to capture that wonder and awe of the first week of doing AI driven solo role playing. The work continues!

Many of the videos from KubeCon EU are on YouTube now, just days after the the talks were given. That’s pretty great! Here’s three talks from the Platform Engineering Day that I really liked. They’re primarily focused on what I’d call designing and product managing a platform. I’m a fan of the “platform as a product” notion - I came across it around 2016 or so at Pivotal and saw many organizations apply it. These three videos are in that general area: how do you build a good product that application developers will want to use and “get value” out of, not just deliver IT capabilities and services.

They’re worth watching all the way through:

• “Sometimes, Lipstick Is Exactly What a Pig Needs!”Abby Bangser, Syntasso & Whitney Lee, VMware - How can you start to take a design/UX-driven approach to building your platform (you know, your pile of Kubernetes stuff to pull it all together for app developers)? Whitney Lee & Abby Bangser have a good mind-model to think about designing the interfaces (how people use parts of that stack). Thinking through how you design your platform “interfaces” for app developers is especially important if you’re building your own stack instead of buying one of the already integrated ones.

• “Designing for Success: UX Principles for Internal Developer Platforms,” Kirsten Schwarzer, KubeCon EU, March, 2024. - Good tour of applying design-think to platforms. That is, what do designers do on platform engineering teams. Some items: (1) Do at least one hour long user interview a week. This gives you an idea of what your users (developers) are doing, struggle with, how your improvements are helping or not, and give you data to decide what to do next. The last is especially useful for fending off The Boss and others who have suggestions that are not helpful: show them the data about what is, at least that you do things driven by analysis, not hunch. (2) Progressive disclosure - only show what people need for a given talk, not everything the tool can do. Can help with cognitive (over)load. (3) Errors are a good source for finding what’s wrong.

• “Boosting Developer Platform Teams with Product Thinking,” Samantha Coffman, KubeCon EU, March 2024. - A lot of good commentary and advice on product managing the platform, some techniques, mindsets, etc. Chief among them: focus on the value/problem you’re solving first, then how you solve it second…also trying to quantify what the problem is so you can measure if it’s fixed, and prioritize it.

With platform engineering, we’re asking operations and infrastructure people to think differently about what they do and how they do it. We’re asking them to think in terms of products, design, customers. This is in contrast to the traditional/current way of thinking about infrastructure which is more like: you tell me what capablites, capacity, and uptime/reliability you need, and I will deliver it to you. What you do with all that is not my concern. This is fine!

When it comes to a platform, though, the platform engineering people are want the platform team to solve problems for developers, not just give them the foundation needed to run their apps. These are different concepts, skills, tasks, and ways of thinking than existing infrastructure think and many won’t know exactly what to do. The talks above, then, are good at walking through new ways to think about “delivering” infrastructure, new ways to evaluate and plan for how you stack things together and gather up requirements.

There’s more videos to check out from the little platform conference, and a ton from all KubeCon, of course.

Oh, and also: If you’re thinking about building and running platforms. You’re probably thinking of just piecing together your own out of free parts and little doo-dads here and there. That usually doesn’t work well. We have a fine selection of pre-shaved yaks you should try instead.

Check out the video series here.

Wastebook

• “The Old Town is Old and the New Town is … well, less Old.” A correspondent on Edinburgh.

• “Grandboss” and “great-great-grandboss.” Here.

• “Something I’ve been thinking about lately.” Here.

• “Add it up.”

• “Build something cool that also meets my company’s requirements for security.” Here.

• There’s not always an “always,” even if there’s often a “usually.” Ibid..

Conferences, Events, etc.

Talks I’m giving, places I’ll be, and other plans.

Tanzu (Re)defined online, April 3rd, The Internet. Tanzu (Re)defined, April 11th, Palo Alto. TEQNation, May 22nd, Utrecht, speaking. DevOpsDays Amsterdam, June 20th, speaking. NDC Oslo, speaking, June 12th.

Logoff

In case you didn’t notice it, if you’re interested in what Tanzu (where I work) is all about, we have an online event now, on April 3rd. It’d be cooler to go to the in-person on on April 11th, but it’d be coolest if you make it to at least one of them. The online one will be broadcast in YouTube and LinkedIn. Sign yourself up for it, why not?

I’ve written a few (little) business books, reviewed several, and reviewed several proposal for business books. Here’s what I think works well in proposals you’re sending to publishers:

1. The publisher is in it to make money first, “important” content second. Your proposal is a business pitch, not an idea pitch. Make sure you talk about who the audience is, why they will buy the book, and why your topic (the market for the book) is hot, or at least, room temperature. Remember: the publisher is looking to sell these books for $30 to $50 a piece. They better be worth it!

2. Defining the market/topic and why it’s “hot” is important. While they may publish a lot of books, publishers aren’t experts in the topics you’re covering, and becoming an expert isn’t what’s important to them. Selling the book is important. Don’t go too long on the market, but try to talk about why the market (current trends, what people want to buy, and why alternatives are not going to be as good as your book [or simply don’t exist]) is good and why this is the right time to publish a book, and why you’re the right one to write it.

3. Be brief (unlike this list!). You should have three sizes of your pitch: a 3 to 4 sentence email/paragraph; a one page version; a longer version. As the author, when you’re writing the proposal, you’ll find yourself wanting to go over the ideas and the actual writing. This is where you’ll write too many words. Summarize the take-aways people will get, quickly cover how you will teach people those lessons/take aways, and really focus on the next thing:

4. Focus on what will differentiate your book for the thousands of other already out there and that will be out there in the future. What is new, different, and unique in your book? New methodologies are good, just going over the basics not so much. Case studies and stories are the best because they’re often unheard and unpublished: they’re something new.

5. Have a detailed, “real” outline at the end. This will give the acquiring editor a quick idea of what’s in the book and also show that you’ve thought this out. Don’t worry about sticking to the outline as you write it, it will change and everyone knows that. In your outline, make sure to the differentiated stuff, especially case studies.

6. Talk about why you’re qualified to do this, why you’re an excellent choice. For business books, I would focus on your first hand experience if you have it. Did you work at an actual company, or are you just a consultant or working at a vendor? Do you talk with a lot of people in your community and have you gathered lots of stories over the years? In most cases, you won’t be a fun and entertaining writer (you’ll be a good writer, but being fun and entertaining is a whole other skill-set), but if you are, that’s an asset to emphasize as well. You will need a bio section, so put all this in there. Be sure to list any written material you already have, even videos and talks. You need some examples of your writing, hopefully published.

7. What fame and community can you bring to the book? Again, the publisher is in it to make money. How can your existing audience, network, etc. help make the book more money.

Other considerations:

• Most publishers have their own template to fill out. They’re all general the same sections, just in different order, wording, length allowance, etc. Don’t get too hung up on getting your original pitch perfect because you’ll need to make it fit to whatever those templates are. Make the pitch in the template “perfect,” of course. And, obviously, just recycle the content.

• Keep in mind that the publisher is also evaluating you as both a writer and as someone to work with. Proof read your text for basic writing mistakes and spelling, typos, to/too, lose/loose, affect/effect,1 etc.; use a consistent style on things (e.g., either end all bullet point lists with incomplete sentences with a period or don’t, use contractions or don’t, etc.) - you want to show that you’re meticulous about your writing and pay attention to the details that non-writers don’t even know exist; and try to demonstrate that you won’t be a handful to work with. Favor a “natural”/conversational style over formal, business speak. Write in the first person, use contractions, and try to use simple words instead of business bullshit words.

• Some publishers do more than just books, so keep their business models in mind when pitching. For example, O’Reilly publishes books (focusing on a single sale of an e-book or 3D book), has an online collection of educational stuff for corporate accounts (focusing on making the ongoing subscription valuable), makes video series (here’s a really good one!), and licenses content to vendors for marketing/lead-gen.

Finally, just keep at it and don’t take anything personally. If they come back with questions and suggested changes to your proposals, work on those. That may seem discouraging, but as long as you’re still talking, they haven’t said “no” yet. Also, be nice: if if this proposal doesn’t work, they might be one in the future or other work you can do with them.

Proposals aside, for me at least, the most important thing is to start writing the book once you have the idea. Certainly propose your book to publishers, but don’t wait on it being accepted. In fact, if you’ve already written the book, or just large parts of it, proposing it will be easier.

Good luck!

I’ve been mentioning the in-person event we have about my work, Tanzu, here. We also have an online version coming up on April 3rd. I was in Palo Alto last week filming it. If you’re wondering what’s up with Tanzu (the Cloud Foundry stack, our Kubernetes stuff, our Backstage/etc. platform, the Spring Framework, etc.) now that we’re part of Broadcom, you'll find out at this event. You can of course register for free to see it: right here! I was there the whole time, so I can assure you that it’s good stuff.

And if you want to attend the in-person event on April 11th, then sign up here.

Conferences, Events, etc.

Talks I’m giving, places I’ll be, and other plans.

Tanzu (Re)defined, April 11th, Palo Alto. DevOpsDays Amsterdam, June 20th, speaking. NDC Oslo, speaking, June 12th.

Logoff

No links today.

Wastebook

• “portal platform.”

• #outmeated.

• “Those sizzlers are nice.”

• “Tell him I’m eating,” 9 minutes in.

• “chair-use disorder.” Here.

• “Is a platypus a Kubernetes symbol? Developers love to take scary things and make them cute.” (Overheard in the crowd before a Cory Quinn talk at SCaLE 21x.)

• Also: “what about you, Charles, what are your thoughts on Terraform…and DevOps in general.”

Relevant to your interests

• Study finds that once people use cargo bikes, they like their cars much less - “A new study out of Germany suggests that once you let people try them, they tend to have a real impact on car use, and even car ownership.”

• Lengthy Memoranda and Gobbledygook Language: Be short and use Plain English by Maury Maverick - Be as simple and short as possible, the man says.

• AI Chair 1.0 - ChatGPT gives instructions for building a chair out of some left over wood - and the guy builds it. // “ultimately, builds agency rather than contributing to our general disempowerment us.”

• Prompt library - Prompts from Antropic, so, not crap.

• HashiCorp reportedly pondering sale amid growing challenges - The DevOps Index probably isn’t doing too well? // “HashiCorp’s share price peaked at the end of December 2021 at $91.04 and at the time of writing is $28.80. The market capitalization is $5.2 billion.”

• Finally, Platform Engineering for Enterprise Cloud Migration - “he asks them to talk about their top five or ten technological pain points. Then the Mechanical Orchard team starts to analyze the legacy system’s behavior based on intercepting inputs and outputs, in order to reproduce the system from there in an open source, cloud native way. This doesn’t mean they don’t use the source code when available — that’s just not the starting point.”

• How to make use of typographic refinement in Pages & other macOS apps - Get really deep into fonts on MacOS.

• What’s new with Tanzu Application Catalog - One of the easier things you can do to be more secure is having your own container registry. Here’s one that’s proven and ready to go.

• Costco CFO ‘voice’ looks back on 40 years, $1.50 hot dogs and leadership | Grocery Dive - “We went out years ago and built a hot dog plant that makes two items, the big hot dog that we sell one at a time and then 12-packs or 10-packs of a smaller size for families. That’s a plant that makes 300 million hot dogs a year and we did that to take a few cents of the cost out by doing it ourselves in such huge efficient volumes and to try to keep that price lower. It’s become part of our folklore, both of those items you mentioned [the hot dog combo and the $4.99 rotisserie chicken]. In terms of changing prices those will be two things that would be last on the list and I don’t see it happening in the near-term.”

• Bringing tech innovation to the American Red Cross - “We try to find the essence of the opportunity that matters most. We start small and then iterate. If you focus on a smaller problem and get that delivered, you have better chances of expanding it. It’s a good way to launch a product: get feedback, see if we are hitting the right areas, and expand from there. That gives us an opportunity to test an idea and then scale effectively once it’s successful.”

• An interview with Piketty - “It depends” applies most of them time: “One of which is that I put excessive emphasis on the universal law of capital. But doing that was mostly a technique to organise a large quantity of data. So when I refer to the ‘first law of capitalism,’ I think it’s clear to anyone who reads me carefully that I’m always trying to historicise the processes and national specificities of how capital works, that it’s a political construction and so on. So these “laws” are not really laws, they are just simplified conceptual relations which can help organise a vast quantity of evidence.”

Conferences, Events, etc.

Talks I’m giving, places I’ll be, and other plans.

Tanzu (Re)defined, April 11th, Palo Alto. DevOpsDays Amsterdam, June 20th, speaking. NDC Oslo, speaking, June 12th.

Logoff

Last week was a crazy-long week of travel. It was nice to see friends, though!

This is from last Fall at the SHIFT conference, but it still holds up:

Relative to your interests

• Why Are Pants So Big (Again)? - tl;dr: you can wear comfortable jeans again. // “There’s constancy, I thought, and then there’s becoming a relic of yourself” And: “If you zoom out far enough, all the paroxysms around self-presentation arrange themselves into an orderly, eminently predictable swing between big and small – you could call it the pants pendulum.”

• What if we rotate pairs every day? - “A few months after the experiment, one team gave us some interesting feedback: They found that when a problem came up in production, they didn’t need to depend on just one person to look into and fix it. The team could assign anyone to troubleshoot the issue. In addition, another feedback mentioned an incoming pair rotation brought new context that changed implementation direction and helped resolve a problem in the early stages of the feature’s development, thus saving the team lots of time and rework. These highlight the benefits of having knowledge spread among the team.”

• Sanders pitches 4-day workweek bill in US Senate • The Register - Works are the last to get worker productivity benefits - AMIRIGHT! “Today, American workers are over 400 percent more productive than they were in the 1940s. And yet, millions of Americans are working longer hours for lower wages than they were decades ago.”

• Understanding product marketing and go-to-markets - Good stuff.

• White House adds teeth to secure software development requirements - ’“Attestation is now a hard requirement that will be enforced during the procurement or renewal process"…. Among the secure practices included in the guidelines, they include separation of production and development environments, use of multifactor authentication, regular logging and monitoring and other factors’

• Europe’s AI Act demands extensive “logs” of users - This probably isn’t the kind of AI “safety” the nerds want, but the goals seems like what normies would want.

• Great Marketing Machines Are Like Costco - Marketing (operations) is about doing a lot of things that lead to one pretty slide to the BoD. // “Great marketing machines are like Costco. There is no magic wand. There is no secret lever. It’s about 50 little things, all working together. And that’s one reason why people have trouble understanding them. This may be obvious, but I’d never previously seen it so clearly. CMOs show the funnel slide in board meetings with stages and conversion rates. But no one really understands the machine. They ask a few random questions, usually about channels. The inevitable attribution conversation follows. You can almost feel them searching for the one thing. But in this case, there isn’t one.”

• Study finds that once people use cargo bikes, they like their cars much less - “A new study out of Germany suggests that once you let people try them, they tend to have a real impact on car use, and even car ownership.” // Electric bakfiets, as the Dutch call them, are awesome. It takes a few weeks of nerve control to cycle around Amsterdam with its narrow streets and along side other bikes, but then it is really close to having a car

Software Defined Talk Podcast

This week’s episode:

we discuss Coté's O'Reilly video series where he offers up some tips on how to survive and thrive in the workplace. Plus, some ideas on how to reinvent the virtual town hall.

This week’s episode is all about my surviving and thriving in large organization videos. Oh, you haven’t heard of that yet? Well, it’s a video series in O’Reilly. You should go watch it!

Wastebook

• “I know the automation will happen anyway, I know those jobs will go anyway. But I’d rather not be the one to build that.” Here.

• “I believe in laissez-faire for names, but if you are going to ban anything, surely ‘Elmer’ is worth some consideration?” Tyler.

• “I don’t care! I like lots of things.”

• “He moved to Chicago, married his college sweetheart, and found a job in a screw factory.” Here.

• “This is an explanation, not an excuse.”

• “Feel free to move fast and break it, and also feel free to pay billions of euros in penalties as a sort-of-tax for that privilege.” bruces.

• “Seagulls' impact on local wildlife can be significant and surprising.” Here.

If you want to know what’s up with Tanzu now-a-days, you should come to the above event and find out. It’s “invite only,” which means it’s for “executives” that we’re interested in talking with. If you’re at a large organization and you’re involved in app development or cloud strategy, you’re probably the type of person we want there. Check it out, and register for it. (And if paying for the travel is a problem, register anyway and maybe we can help out with that.)

🌐 Register now.

Conferences, Events, etc.

Talks I’m giving, places I’ll be, and other plans.

Tanzu (Re)defined, April 11th, Palo Alto. DevOpsDays Amsterdam, June 20th, speaking. NDC Oslo, speaking, June 12th.

I can’t make it to KubeCon EU this year, but if you’re going: come to our little party at KubeCon EU, it’s Thursday night. Register for free here! And, if you’re going to KubeCon EU and haven’t registered yet, you can get 20% off with the code KCEU24VMWBC20.

Logoff

I had a long week in the States - arriving in Palo Alto on Saturday for a fun work thing, then to Dallas for an executive dinner Wednesday night, and then to Pasadena to give the opening keynote at DevOpsDays LA. While a week is too long for me to travel now-a-days, each of the events was great, and it’s been nice to meetup with people.

Re: “Bad” Strategy

Strategy is people, and in a corporate setting, all the wonky parts of people are amplified. In the places I’ve worked, the lower down you go in the organization, the less relevant strategy is. What’s relevant is the actions you can take, not the outcomes the executes are going for with their strategy, let alone anything resembling a classic big-S Strategy.

Besides, unless you have a huge chunk of equity, you get paid the same no matter the outcome. Long-term you’ll suffer if the company goes out of business, sure, but short and medium term, you’ll just keep chugging along. Thus, for most workers, if the stated strategy doesn’t direct what actions to take (and not take!), it’s not very useful.

This also applies to OKRs. What’s missing from OKRs are the actions it takes to get from the O to the KR. This annoys me to no end. And, yeah, I read that OKR book a few years ago. You can’t set an objective and a realistic key result if you haven’t imagined the actions you’ll take to get there. Executives build the system that everyone works on, and just like an enterprise architect that no longer codes, if the executive has no idea, or even second hand experience of how the work is done, it’s hard to imagine what needs to be done to reach the KR. This means the KR is what they hope will happen, not what’s happen-able. To hedge: sure, I bet there’s just fine OKRs, but it’s too easy for people to mess them up.

Doing strategy in large companies is very difficult. One of the huge advantages of startups is that they can do MVP/lean strategy, if any at all. Big organizations often don’t - can’t - test and validate strategy content and adjust it every quarter or two to match what customers actually want.

Anyway, this is why the context and thinking around strategy is more important then the 25 to 30 words of the actual strategy. Fitting corporate strategy on a slide is a good start, but then outlining how it’ll be done is what really matters.

(Provoked from this good piece.)

Relevant to your interests

• Cognizant Predicts GenAI Will Inject $1 Trillion Into the U.S. Economy - Seems like a lot of money.

• Corn - “I've just had what feels like the hundred billionth reader inform me that, with all due respect, Hild is quite wrong to talk about corn in 7th-century Britain. And for the hundred billionth time I've politely responded that, actually, no, there's no mistake. To Hild, corn is wheat, not maize.”

• IT leaders dial back cloud-first strategies as hybrid IT becomes more of an investment priority - People interested in lowering costs, on-premises and public cloud. I mean, who’s ever like “nope, I’m fine spending more when I could be spending less.” // “over a third of the study’s EMEA participants (36%) are taking a cloud-first approach to new application deployments, which is slightly down on a similar study carried out by TechTarget in 2023. Back then, around half of the participants indicated that their organisation was favouring a cloud-first approach when choosing the best environment to deploy new applications and workloads.”

• Oh hey, check this out: With Tanzu CloudHealth, “[b]y enabling the [South African FSI Discover] to streamline its expenses and resources, the solution helped Discovery realize a 40 percent reduction in costs in less than a year’s time.”

• AI startups require new strategies: This time it’s actually different - Good stuff.

• Pairing and interviewing at Pivotal - People seemed to like this. Of course, there was survived bias: the only people who talked about it had gotten the job. Still!

• Codefresh and Octopus: GitOps, K8s and VMs Under One Roof - The “greenfield aasumption”…I like that! // ‘“The ‘greenfield assumption’ has broken and is still breaking a lot of advanced DevOps software implementations by failing to accommodate the complexities of real-life environments,” Torsten Volk, an analyst for Enterprise Management Associates (EMA), told The New Stack. “The vast majority of enterprises still have, and will have for many years, messy and heterogeneous environments that somehow need to be made part of CI/CD and GitOps.”’

• Speaking of, an example of the greenfield assumption anti-pattern in action: “A widespread local presence and deep roots in the community have given Germany’s savings banks a high standing since they were founded around 200 years ago: Tradition breeds trust. However, traditional financial institutions today find themselves confronted by growing competition – not to mention the need to design more customer-oriented offerings. FinTechs, for example, start ‘from the green field,’ do not bring legacy mountains of data with them and offer customer-oriented services quickly and efficiently.”

• 4 Engineering Slides CEOs Love - There’s a good mix of “business value” and inward facing technical activities and health-checks.

• Michael Joseph Lost and Found - Modern day hitchhikers and train hoppers.

• Is GenAI’s Impact on Productivity Overblown? - Generative AI hasn’t been around long enough to figure out what to do with it, especially in enterprises. Before you spin up too many projects and budget, you need to experiment with and validate how you apply it. After around a year of using ChatGPT, I suspect it’s a lot like email, intranets and intranet search, CRM, etc.: it’s not good enough to replace knowledge work, but it’s a better tool than what we have. Also, in the article, the point that productivity is nice, but accuracy is better: “while changes in task completion speed are easy to measure, changes in accuracy are less detectable. If an employee completes a report in five minutes instead of 10, but it’s less accurate than before, how would we know, and how long will it take to recognize this inaccuracy?”

• Facing reality, whether it’s about Apple or the EU, is a core requirement for good management - Understanding the EU’s position and motivation for the recent nerd/regulators fight.

• How DZ BANK uses a Cloud Run-first approach to unlock big savings, with Google Cloud - “We are now three years into our modernization journey with Google Cloud, and we’ve seen significant benefits. Running containers on Cloud Run instead of on-prem VMs eliminates OS and infrastructure maintenance, delivering a 70% toil reduction. In addition, the pay-per-use pricing model has reduced our infrastructure costs by 90%.”

Wastebook

• “Unlimited Netflixing in Your Mind.”

• A lot of executizing is removing context from your write-up. Background, explanation, proof, discussion - context. Most (American-style) executives wants to know the outcome, the conclusion, the decision to make, the next steps. Once they’ve decided they like the conclusion then they might be interested in understanding why it’s a good conclusion.

• “Things are the way they are because they got that way.” Here.

• “Revolutionizing Printing in the Modern Workplace” Sure to be a real heart-racer.

• “Font security ‘still a Helvetica of a problem’” Here.

• “The lunacy comes from a place of joy.” Sharp Tech, March 7th, 2024.

• “Bring 2–3 wardrobe options, pressed and ready to go.”

• “Some days you wake up and realise that you’re waiting on other people to do so many things that you yourself have become somewhat paralysed by the waiting.” Here.

We’ve got a little event coming up next month, Tanzu (Re)defined. Unlock the secrets of expert app development and delivery at VMware Tanzu's exclusive event. Dive into Tanzu Application Platform, Tanzu Application Service, and the Spring Framework. Discover optimization strategies for cost, performance, and security. Gain insights from Tanzu Labs' 30 years of app experience. Meet Tanzu's Executive Team and industry peers for practical strategies.
 
🌐 Register now.

Conferences, Events, etc.

Talks I’m giving, places I’ll be, and other plans.

Executive dinner on Java Security, March 13th, Dallas; DevOpsDays LA, speaking, March 15th, Pasadena “We Fear Change” talk; KubeCon EU, March 19th, Paris; Tanzu (Re)defined, April 11th, Palo Alto. DevOpsDays Amsterdam, June 20th, speaking. NDC Oslo, speaking, June 12th.

Come to our little party at KubeCon EU, it’s Thursday night. Register for free here! And, if you’re going to KubeCon EU and haven’t registered yet, you can get 20% off with the code KCEU24VMWBC20.

Logoff

Every now and then I like to try to slip something fun into the corporate world. I came up with that event name, “Tanzu (Re)defined” and thought, surely, someone is going to say this is silly. But, people liked it.

//

Also, hey, if you like my stuff about work-life, you’ll really like my new video series over at O’Reilly. If you work at a big company, you might already have access to it. You should check it out!

//

I’m on a weeklong tour of the States this week. As I’ve said before, I’m more or less over business travel. I’ve done it for 19 years now, and with three kids, a wife, a dog, two snakes, and turtle at home…but these long trips are really too much now.

Many of the people I grew up with in business travel don’t seem to travel much anymore either. However, business travel is a huge part of my job - it just is. And it’s hard to envision what else I’d do that’d have as much value and, despite what I’m saying, fulfillment.

But, you know: also I can’t go around harrumph-y about it, I’m sure there’s people who’d gladly switch places. Must be nice!

Just links today.

Relevant to your interests

• Two methods for designing better, more developer friendly platforms - Two ways to make good platform product management decisions: go to where the developers are, ask the developers // a little article by me.

• Platform Engineering: Orchestrating Applications, Platforms, and Infrastructure - A big overview of platform engineering. Also: Syntasso gettin' into the devrel game!

• Forrester: Tips for assessing hybrid cloud management - All these years later, enterprise workloads are still running on all the clouds, public and private. // “87% of global cloud decision-makers say their organisations deploy enterprise IT workloads on public cloud, private cloud and in datacentre hosting facilities.”

• Dell COO: AI will move to the data - (Enterprise) AI will go to where its cheapest to run, by whatever factors.

• Why Kubernetes needs an LTS - Currently, you can patches for the kubernetes version you’re running for supported for 14 months (12 months of support and 2 months of upgrade period)," a year and two months. He wants to make it 2 years: “I would propose an LTS release with a 24 months of support from GA and an understanding that the Kubernetes team can’t offer an upgrade to the next LTS. The proposed workflow for operations teams would be clusters that live for 24 months and then organizations need to migrate off of them and create a new cluster.” // LTS-talk makes my head hurt, but I think the charts in here are OK. // Also, vendors love LTS as an enterprise feature, and it usually is worth paying for. But, it’s also a trap if you let yourself get locked-in to older versions.

• CNCF Survey: Half of Organizations Spend More with Kubernetes, Mostly Due to Overprovisioning - “The survey participants shared their views on why running Kubernetes can get quite expensive. The main reason for overspending was overprovisioning (70%), accompanied by the sprawl of resources not being deactivated after use (43%). The second cluster of responses was related to the lack of visibility and insight into consumption and spending (40%) and the lack of awareness and responsibility at the individual and team levels (45%). Technical debt related to not re-architecting workloads migrated into the cloud environment for scalability accounted for 43% of the overspending. Further down, the respondents pointed to resource-hungry workloads (25%), fluctuating consumption demands (23%), and poor planning/prediction of cloud consumption.”

Wastebook

• “Little surprises around every corner, but nothing dangerous.” Willy Wonka.

• “The person continues to operate out of the old attitudes and strategies, but they are no longer effective.” Some Jungian shit.

• “When all else fails, wear a mustache so everyone sees you as more man-like.” Here.

• “Like, why would I want to look snappy in the office?” Here.

Conferences, Events, etc.

Talks I’m giving, places I’ll be, and other plans.

Executive dinner on Java Security, March 13th, Dallas; DevOpsDays LA, speaking, March 15th, Pasadena “We Fear Change” talk; KubeCon EU, March 19th, Paris; Tanzu (Re)defined, April 11th, Palo Alto. NDC Oslo, speaking, June 12th.

Come to our little party at KubeCon EU, it’s Thursday night. Register for free here! And, if you’re going to KubeCon EU and haven’t registered yet, you can get 20% off with the code KCEU24VMWBC20.

Logoff

See you next time!

Surviving and Thriving in a BigCo

If you work in a large organization, you’ll like this new video series I did with O’Reilly. Check out the intro above, and here’s the topics covered:

1. Cultivate your Style and Character.

2. How does a BigCo Work?

3. Mentors are Nice, Champions are Better.

4. Asking Questions Leads to Homework for You.

5. Assign Homework to Filter out Vampires.

6. To Innovate, Hide Out.

7. Slides are Docs.

8. Always Have an Ask Ready to Go.

9. Embrace Work/Life Imbalance.

If you have access to O’Reilly, you should check out the videos. If you work at a large organization, especially in a technical role, you should watch them all! You can get some kind of certification if you take the quizzes (a sort of hilarious thing for this type of content, but whatever).

These are good videos, if I don’t say so myself. If you like my style of stuff, you’ll like these. Tell me what you think!

Microservices Modernization Missteps: Four Anti-Patterns of Rebuilding Apps - and how to avoid them

One of my colleagues has a post out going over four anti-patterns when you're modernizing to microservices: (1) Relying only on code and documentation for business context; (2) Unvalidated architecture; (3) Insufficient test automation; (4) Big bang releases.

I helped put it together, so, you know, I think it’s pretty useful stuff. Check it out!

Software Defined Talk podcast #456

This week, we second guess recent decisions made by Google and Apple. Plus, what social media sites is everyone actually using these days?

Take a listen! Check out the unedited livestream video if you’re really a super-fan.

Relative to your interests

• We CAN Have Nice Things: Upgrading to Java 21 Is Worth It - “It’s (Jave 21) also morally superior. You won’t like the look of shame and sadness in your children’s eyes when they find out that you’re using Java 8 in production.”

• Thanks Oracle! Java licence squeeze puts a rocket under Azul - “Oracle, by developer use, was probably 60 to 70% market share according to Gartner. This year, that’s down to 30%. ” // Meanwhile, since Jan 2023: “The Oracle Java Licensing change made organisations purchase a licence for their entire employee population if even a single employee or server has installed a_ licensable_ version of Java – which is widespread, often without organisations realising this. And Oracle, notorious for its ferocious audits over the years, is stepping up audits of Java users.”

Wastebook

• “Every idea is a story of someone trying to solve a problem.” Here.

• “Boy, are you going to be glad you opened this newsletter. Because you are about to learn about the lone banana problem.”

• “A primer on space mining — and its impact on the IT sector.” From a 451 report.

Conferences, Events, etc.

Talks I’m giving, places I’ll be, and other plans.

Executive dinner on Java Security, March 13th, Dallas; DevOpsDays LA, speaking, March 15th, Pasadena “We Fear Change” talk; KubeCon EU, March 19th, Paris; Tanzu (Re)defined, April 11th, Palo Alto. NDC Oslo, speaking, June 12th.

Come to our little party at KubeCon EU, it’s Thursday night. Register for free here! And, if you’re going to KubeCon EU and haven’t registered yet, you can get 20% off with the code KCEU24VMWBC20.

Logoff

After a week of pissing rain, it’s sunny hear in Amsterdam. We’ll see how the weekend goes.

//

I finally got my 2FA login for my Twitter account fixed. I’d been ignoring it since the Fall, just posting my content, and then got locked out sometime in December or January. There’s still so many people in my tech world there. It’s kind of weird, weren’t they all supposed to abandon it out of Elon-hate, or something? I feel like I chose the wrong path during all that nerd-wailing. I’ve got a large enough following in Mastodon, but there’s just not as much engagement as I’m used to (there are a handful of people there that I write back and forth with that are great, though). And since I missed out on the initial tech-invasion of Threads (since I live in the EU), there’s not much there. This stuff always comes down to years of curation and activity, which is hard to build back up.

I don’t think that federated dream (where Threads, Mastodon, and Bluesky all interior) is ever going to come true: that was clearly just some hopeful-nerd talk last year. (And now that you an pay Twitter to remove all ads, what they should do is open up third party APIs for the Premium+ customers - they’re not missing out on ads anyhow - but, whatever). It’d be great to have an Adium-like app for all that shit. Dreams! Anyhow, speaking of quality content (or lack thereof!) I have a backlog of lots of my silly videos to post in Twitter.

Better put PR on the backlog

Art for no one, by no one. Art whose only audience is the collective pathos. Incredible. [AI culture problems as art]

The Gemini thing: the conversation around AI technology is now based on how it can navigate social and cultural issues, less if it “works.” These social and cultural issues eventually wear out - people forget - so you have to just stay alive and hold it back. Also, with AI (as with most technologies), you can fix the features/bugs that provoked the social and culture issues. In one way, the negative feedback is just “feedback” that you’d expect in the lean product methodology. However, with social and cultural issues, it’s difficult to accept failure as learning (product management feedback).

Social and cultural issues are usually negative, rarely positive.

Facebook means you can keep up with family and friends, previously we had letters and expensive long-distance phone calls. Now we bemoan screen time instead of saying “holy fuck, never mind a 1,000 songs in my pocket - now I have the Internet in my pocket!” I’d have to trust schools to adapt to my kid’s learning styles, pay a lot of time and money for private tutors, now they can ask ChatGPT to explain concepts to them in the style that works for them.

Also, with (business) software, the benefits are mostly boring: making it cheaper to run computers and software, speeding up or removing shitty office work (who wants summarize meetings that you didn’t want to be at in the first place?), removing the friction and bottlenecks of reaching new customers and interacting with newer ones (online bill pay instead of mailing checks; automating inventory instead of walking around with a clipboard and pencil). “People have forgotten, I think, just how big a deal having a common interface to all the storage arrays was with VMware like before,” Justin. When transferring money in the US is finally fixed (like it is in Europe), few people are going to writing and podcasting about that for months on end: “regional credit unions enable easy money transferring, yay!”

My point here is not to bemoan this - it is what it is! - but to be prepared for it, to weave it into your operational strategy, your product management. Put PR in the backlog, call up your marketing and comms people, and have them take a seat at your daily stand-up meeting. You’ll need them and their contribution will be as valuable as any technical thing. devPRops.

“Rude” is culturally relative

I’ve lived in the Netherlands for almost six year, and as a Texan, this is still a daily struggle:

Dreams of Having it Both Ways

Phase 01: There is too much vendor lock-in and there are only, like, two viable options for anything. Why don't these people innovate anymore?

Phase 02: Oh my God! Have you seen how many choices there for everything?! <insert CNCF Landscape lulz here>.

Phase 03: GOTO Phase 01.

Relative to your interests

• 3 Ways to Help Struggling Open Source Communities - By supporting local meetup groups and sharing your time with organizers, you can help sustain our vital tech communities.

• RTO doesn’t improve company value, but does make employees miserable: Study - ‘"Results of our determinant analyses are consistent with managers using RTO mandates to reassert control over employees and blame employees as a scapegoat for bad firm performance," the researchers concluded.’

• How startups beat incumbents - “big companies don’t like to take big risks even when the outcome might be large. The fear of failure is an order of magnitude more motivating than the desire to innovate or even the greed of success.”

• Sabre completes migration to Google Cloud, closes 17 data centers - Starting in 2020, now in 2024: “Over the course of this effort, we’ve closed 17 data centers and moved more than 40,000 servers, 400,000 CPUs, and 50 petabytes of storage into the cloud.” Congrats!

• Public Intellectuals Have Short Shelf Lives–But Why? - Keeping thought-leader’ing fresh is difficult. // “why are so many public intellectuals capable of generating insight, originality, or brilliance at the beginning of their careers, but are utterly incapable of fresh thinking a decade later?” // “Old attitudes die because generations that hold them _literally _die off. Such is the stuff of progress and disaster. Such is also the problem of the public intellectual. A public intellectual’s formative insights were developed to explain the world he or she encountered during a specific era. Eras pass away; times change. It is difficult for the brain to keep up with the changes.”

• Me: “I want to start seeing (only?) more analyst estimates of kubernetes usage by app/workload (not just if people are using it). Not out of some desire to see it be small and poke fun at it, but just as with public cloud in the 2010’s to just know what’s actually happening. We need that annual (quarterly would be better) thing like the storage growth/data explosion thing IDC and EMC used to do.1 That’d be great for the CNCF to start estimating. All opinions about how hard it is are besides the point now: adoption and migration of workloads (and also new workloads) to it are the only thing that matters and is interesting).”

• How I stay (more) focused with ADHD - “I often go to a café to write, and it helps me a lot to focus on writing. As much as I loathe noise and distractions, the café noise and presence of other people (known as body doubling, see below) help me to focus on writing. Unless, of course, I can hear and understand what people are talking about — in this case, I must hear the gossip.”

• Why Do East Asian Firms Value Drinking? - Also, a lot of charts and ideas from The Culture Map, a great book for understanding differences in business communications across the globe.

• TikTok Is For Millennials, It Turns Out - Everyone gets old. // “it’s probably smart to not assume that the kids are the ones responsible for whatever new weird thing is on your FYP. Those videos are probably being made by weird adults.”

• What It’s Like to Be a Sociopath - “Yes, [as a journalist conducting an interview] you are manipulating people to a certain extent — to your point — in the way that I might manipulate somebody in therapy, but I would never feel the need to justify it, and your justification came so quickly. That’s why I was like, Hey, what’s happening that you felt the need to defend your answer?”

• Gemini For Google Workspace Plays The Long Game Gemini for Google Workspace Plays The Long GameAI Insights artificial intelligence - Office workers are the new kingmakers. // “If you don’t give them something sanctioned, they’ll use bring-your-own AI tools such as ChatGPT on the web, opening your organization up to security and privacy risks and rendering their activities unmonitored by your IT team.”

• 30+ ways I’m using AI in everyday writing life as a technical writer, blogger, and curious human - Whole lot of prompts, many related to writing, but plenty of everyday things.

• Legendary CEO James Keyes: Here’s how I saved 7-Eleven–and why I couldn’t save Blockbuster - Lesson learned: avoid being $1bn in debt during a financial crisis.

Wastebook

• “It makes a sound like mixin' macaroni and cheese.” Here.

• “parameters and pushback”

• “Sam Altman tech CEO speedrun.” Here.

Conferences, Events, etc.

Talks I’m giving, places I’ll be, and other plans.

Executive dinner on Java Security, March 13th, Dallas; DevOpsDays LA, March 15th, Pasadena “We Fear Change” talk; KubeCon EU, March 19th, Paris; Tanzu (Re)defined, April 11th, Palo Alto.

Come to our little party at KubeCon EU, it’s Thursday night. Register for free here! And, if you’re going to KubeCon EU and haven’t registered yet, you can get 20% off with the code KCEU24VMWBC20.

Logoff

I’m home for a few weeks, then traveling for two weeks: to the US for a three city tour (including DevOpsDays LA and that executive table above); the next week in Paris for KubeCon. I need to get on submitting talks to more conferences. I don’t know, man. Is there anything left to talk about?