If this tickles your curiosity, we wrote a book on #ProgressiveDelivery, based on similar principles!
And coming very soon, a podcast with @kentbeck.com as a guest!
progressivedelivery.com
Latest posts tagged with #ProgressiveDelivery on Bluesky
If this tickles your curiosity, we wrote a book on #ProgressiveDelivery, based on similar principles!
And coming very soon, a podcast with @kentbeck.com as a guest!
progressivedelivery.com
My #2 recc is where possible, give people options. For electronic documents, everyone should be able to set their own best experience. Big comic sans? Great, if it works for you.
Adding rendering optionality is a huge accessibility win, and good #ProgressiveDelivery.
Today's #ProgressiveDelivery content is from Dr. Glaucomflecken youtube.com/shorts/BWmrh...
If you've read the book, don't forget to leave a review, there's a magic number!
I legit may need to blog about this video tomorrow.
Help, I was rewriting a removed bit from the #ProgressiveDelivery book (out Nov 4, pre-order now!) and somehow it's all about Roosevelt's Four Freedoms speech, and in fact that maps really well to the modern SDLC, and why am I like this?
en.wikipedia.org/wiki/Four_Fr...
4. Automate the iteration process Because we have all the context on both users and the product, we can automate large chunks of the cycle of shipping -> observing -> iterating. Secret master plan Ship every tool and all the data that engineering teams need to understand their product and users Use that to speed up the cycle of shipping -> observing -> iterating Eventually, automate the entire cycle
I have an application in at PostHog (look, I know, but it's their name), and look at this #ProgressiveDelivery vibe!
"We also knew that many engineers struggle to understand the impact they have on the people who use what they build."
What tells Flagger a release is safe to keep going? What is the safety mechanism?
@stefanprodan.com tells how it decides, and when it rolls back.
Watch the full 🌩️ Thunder episode:
youtu.be/Qi9Xq_QxX7M
#Kubernetes #Flagger #ProgressiveDelivery #CanaryDeployments #Prometheus
What is a “canary deployment” in Kubernetes?
@stefanprodan.com has the answer, and he talks about how the Canary custom resource in Flagger relates.
Watch the full 🌩️ Thunder episode:
youtu.be/Qi9Xq_QxX7M
#Kubernetes #Flagger #CanaryDeployments #ProgressiveDelivery
The authors of the #ProgressiveDelivery book. On a boat!
Left to right: @wiredferret.bsky.social @kimmykimkimber.bsky.social @azimman.bsky.social and @monkchips.com
A screencap of the “Amazon Hot New Releases” page for Project Management. The cover for the Audible version of the Progressive Delivery book is listed at #1. It is also cheap to pre-order, only $14 or one Audible credit.
This week we gave away almost 100 fully-signed #ProgressiveDelivery books while we were at #Monktoberfest, and even more than that at #ETLS25 (but fewer signatures).
We are exactly one month from release day!
And look at this pre-order sales ranking!
Whitney Lee smiling on the left and Stefan Prodan on the right, with a blackboard full of Flagger notes in the background. Large yellow text reads “Flagger,” with white text below: “Progressive Delivery and Canary Deployments.”
Deploying fast is easy; deploying safely is hard. ※
In this 17-minute 🌩️ Thunder episode, @stefanprodan.com shows how Flagger brings control to Kubernetes deployment rollouts.
Watch the Thunder episode here:
youtu.be/Qi9Xq_QxX7M
#Kubernetes #Flagger #Flux #ProgressiveDelivery #CanaryDeployments
Anyway, #ETLS25 was an incredibly useful conference for me and the #ProgressiveDelivery team, and I'm the way to escaping from Las Vegas.
Next week, for a total tonal shift, we'll be in Portland, Maine for Monktoberfest.
Migrating from K8s Deployments to Argo Rollouts? It’s easier than you think.
☆彡
Nicholas Morey explains how Rollouts extend Kubernetes with progressive delivery and are designed for smooth adoption.
Watch the full 🌩️ Thunder episode →
youtu.be/ToF9fb2sjlE
#ArgoRollouts #K8s #ProgressiveDelivery
We signed 200 copies of the #ProgressiveDelivery book! I didn't take pictures, but it was very orange! #ETLS2025
A gridded cutting table supports a box. A person is opening the box with a seam ripper.
A box full of books. Most of them are faced down so you see the back cover, which has concentric rings from inner red to outer orange. It is covered with white text. Sitting on top is one book positioned vertically with the front cover showing. The title is "Progressive Delivery: Build the Right Thing, For the Right People, At the Right Time". The authors are James Governor, Kim Harrison, Heidi Waterhouse, and Adam Zimman.
A physical book that is a real thing is being held open. The text above the image says "...out some preparation and notification prior to release. You may want to prime your early group to be excited about adoption or avoid shocking change-averse users. We can't tell you what emotions your users have. We just want to remind you that users feel things about their tools. This calculation of factors is why deployment is about software getting where it needs to go, and release is about what the user experiences. Figure 10.1 provides a visual representation of how to think about the separation of deployment and release. In the diagram, we can see how the activities relate to who owns the activity and who is impacted by that portion of the cycle, as well as who participates in that particular feedback loop." The image is based on the two-lobe devops loop, but this one has three lobes, labeled Dev/Ops/User. Further text: "We also need to be able to undo changes if and when we discover they are unwelcome. Building in a way that makes it fast and easy to reverse our releases is a part of making them safer to release. Feature flags are an elegant way to distribute code that can behave in different ways at runtime without needing to replace the whole code base exposed to the user end. The best changes are often transparent to your audience. This doesn't mean you keep the look and feel of your GeoCities site from the late 1990s, Google search to figure out how to but your users shouldn't have to do a Google search..."
I am thrilled to report that my author copies of the #ProgressiveDelivery book are here!
And they smell like ink!
Automate the predictable, focus humans on uncertainty. Manual processes kill adaptation bandwidth when disruption hits.
itrev.io/3UZUEa7
#ProgressiveDelivery
Hello, my artists.
How would I go about hiring someone to draw an invertebrate mascot? Maybe a couple poses, we can use in marketing?
I will pay, but can't pay Corporate Much. #ProgressiveDelivery
"Progressive Delivery brings the art of responsibly shipping early and often into the daylight. It reframes delivering value via software in a world swimming in dreck. Software serves people, not the other way around & Progressive Delivery maps out how." -- Kent Beck, Author of Test-Driven Delivery
We were thrilled to get a quote from @kentbeck.com on our upcoming #ProgressiveDelivery book. itrevolution.com/product/prog...
When your users complain about the pace of updates, support tickets spike after every release, and features with obvious benefits have mysteriously low adoption, you might be encountering "technological jerk."
Read more: buff.ly/tEwtasr
#SoftwareDelivery #ProgressiveDelivery
Pavel's cooking here. The people experiencing the software are a crucial part of the software lifecycle, and how we measure their experience changes what we are making.
bsky.app/profile/spav...
#ProgressiveDelivery
It's time to write the acknowledgements for the #ProgressiveDelivery book, and I got through family and close friends and now I'm trying to describe/remember all the other people who helped, and it is giving me The Fear. Because I will forget someone, and they'll be sad.
I will make someone sad.
#ProgressiveDelivery is about using that telemetry to help the user be less pissed off.
How's your evening?
Oh, I'm just sitting around talking about how the foundational value of #ProgressiveDelivery is consent.
Also dinner smells amazing.
I think it's incredibly useful to have ongoing user research, but it's hard to sell that way. My current tactic is to talk about "end-user observability". Makes it sound much fancier than "actually watch use patterns"
#ProgressiveDelivery
But before I go, please enjoy my first-draft take on #ProgressiveDelivery intellectual ancestors:
Frederick Fucking Winslow Taylor - utter gremlin who wanted make people into more efficient machines
This thread is so #ProgressiveDelivery -pilled.
Feature flags and #ProgressiveDelivery have been part of your software experience for longer than you may realize.
Cut from #ProgressiveDelivery
When we are talking about automation as a part of Progressive Delivery, it’s important to remember that we can’t automate what we don’t understand.
Cut from #ProgressiveDelivery
And yet… the automated washing machine was invented to save (mostly) women from the backbreaking labor of boiling water, carrying it, hand-scrubbing clothing, putting it through a clothes mangle, hanging it to dry, and ironing it. And it did.
Cut from #ProgressiveDelivery
”In order to deliver what users and people need, we need to understand what is needed. This is similar, but not identical to what they might ask for.