Posts in "newsletter"

What they don't tell you about conference MC script writing

A quick one today, no time to compile the links and stuff Writing good MC scripts for the keynote sessionsI’ve been writing the MC script for our upcoming SpringOne conference. I was supposed to go be one of the MCs but had to cancel. It would have been awesome to know both sides of MC script writing - creating it, and reading it. I wrote the MC script last year. And, you know, I’ve watched lots of main stage keynote dog and pony shows (and plenty of goat rodeos).

Half-harpy

I’ve had an unhealthy1 obsession with getting my kids to play D&D recently - they asked to! So, I haven’t had my usual liminal time to get a newsletter out. To that end, my son wanted to make a harpy character. While there are home-brew (is that the right lingo? I stopped playing D&D in about 1993, maybe ‘92) harpy character races, we encountered a problem: harpies don’t have hands, really.

Money spent on containerized workloads is growing fast, but overall spend is still small compared to traditional infrastructure

PSA: I recommend that you use your personal email address to subscribe to this newsletter. We're approaching and in layoff and job change season. Starting now to the end of the CY/FY, bonuses are paid out, promotions have been denied or gained, etc. If you're subscribed with your work email, consider switching to a personal email address. 📨 📨 📨 📨 📨 Hunting for the cloud native and kubernetes pay-offThis is an excerpt from my talk yesterday with Bryan Ross, his theory here is fun, clever, and probably right:

The eternal principles of an (enterprise) app stack

Suggested vibe for this edition: The eternal principles of an (enterprise) app stackThese are not all of them, but it’s a start. The function of an app stack is to allow your developers to be creative, use fast release cycles, and create software that can run in production: that stays up and meets whatever compliance (regulations, security, etc.) you need. We keep trying to merge the dev tools stack and the runtime tools environment into one platform.

Why is developer experience so bad if we all think software is so important?

This week’s Tanzu Talk podcast (video above) is all about developer experience, and COBOL: "75% of IT and business executives say that their companies’ ability to compete is directly related to their ability to release quality software quickly" reads a recent Forrester Consulting report. If that’s the case, why are so many developer in large organizations have a bad developer experience? Paul Kelly wrote up the case for good DevEx and what it looks like for developers on the VMware Tanzu blog recently.

Pair Programming is a great fit for large organizations because of this one unexpected benefit. CLICK NOW.

I have another video today. You've heard of pair programming and you probably think it's bonkers. Not many people benefit from this practice. Here, I go over how teams in the US military have been using pair programming to improve how they do software and spread that change to other teams. Some real DIGITAL TRANSFORMATION! Check out the blog post I based this on, it has a lot more on how other agile practices are helping out programmers in the DoD.

Developers are bad at estimating in at least three ways.

Midjourney: Olan Mills style photograph of software programmers standing around a conference table in 1980s sitcom styleSoftware people are bad at estimatingHere are three ways that software people (developers, mostly) are bad at estimating: Estimating the feasibility of writing code for new features, that is, the risk of failure - if the new feature is difficult to impossible to write, or just doesn’t work altogether. Generally, it’s a lot harder than it seems because of all the things apart from the actual feature.

Waiting for the close of open - how long can the 2000s spirit of open source and open APIs last?

Midjourney: Medieval serfs defending a castle from demons in the style of Hieronymus Bosch, from venusinfurs.The changing nature of “open”In our tech world, the idea of “open” has changed a lot in the past few years. Instead of it meaning “open to everyone,” the classic notion of “open source,” now it more means “open to everyone except our competitors.” Making money with open source is difficultRunning a high growth business on open source is difficult; you’re giving up on the easiest, most obvious thing to get paid for: the software itself.

The problem with t-shirt schwag at tech conferences

Ever wonder why there’s not more t-shirts at tech conferences? Marketing people hate getting t-shirts for booths at conferences. In last week’s Tanzu Talk about platform marketing I went over why: Tech conference attendees love t-shirts. They’re also good for brand- and idenity-marketing: if you’re wearing the shirt, you’re likely a fan. Or, at least, you tolerate the brand. You don’t see a lot of t-shirts at tech conferences because marketing people usually hate t-shirts.

If you’re so smart, why are we all still so dumb?

We’re back from a three day weekend in London for our anniversary. I tried very hard to eliminate all “productivity,” so I have very little to say today. I did want to ADVERTISE for a thing I have tomorrow. So I’ve gathered up some waste book for you today. Snow-Covered Field with a Harrow (after Millet), Vincent van Gogh (1889).WastebookWe should revise the Peter Principle not to be insulting (reached the level of your incompetence), but burnout driven: reached the level of being able to put up with more bullshit.