I hated Scrum by the morning of Day-2 when I saw it was being weaponized. It was a whip to drive relentless change within what was otherwise waterfall, but with 1/10 the thought common to waterfall. That was 20 years ago.
Teams that I worked with still used Scrum.
I've learned that half of software development is recovering from everyone who yells, "SQUIRREL!!!"
I know y'all probably hate Grok, but just saying.
in the cloud. Some have tried, but the emulators fall over on load.
Huh, I may have just convinced myself to buy IBM on the cheap.
4/4
you should work with a single bank with the goal of doing just that. Five years later, they're still scratching their heads, trying to make a *that decision* on *how* they can possibly succeed.
What some company should do is throw a bunch of CPUs and GPUs at emulating z/OS and iSeries ...
3/4
programmers to *maintain existing* financial systems.
No, I don't own IBM stock, and I'd love to see COBOL systems replaced, but I'm not that naive to think that 67 years of gargantuan work and lock-in will go up in smoke even in the next 10 years. If you don't understand, ...
2/4
The IBM stock sell-off demonstrates how little investors understand about AI and LLM-based coding assistants. If anything, the stock should have surged 15% due to Claude Code extending the life of COBOL systems. It *writes* COBOL, which means it can be used by another generation of...
1/4
Keynote "Stochastic Architecture" by Vaughn Vernon | Software Architecture Gathering 2025
𝗪𝗮𝘁𝗰𝗵 𝗩𝗮𝘂𝗴𝗵𝗻 𝗩𝗲𝗿𝗻𝗼𝗻’𝘀 𝗦𝗔𝗚 𝟮𝟬𝟮𝟱 𝗸𝗲𝘆𝗻𝗼𝘁𝗲 “𝗦𝘁𝗼𝗰𝗵𝗮𝘀𝘁𝗶𝗰 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲” – 𝗻𝗼𝘄 𝗼𝗻 𝗬𝗼𝘂𝗧𝘂𝗯𝗲! 🎥
In his #SAG2025 keynote, @vaughnvernon.bsky.social explains why #LLMs don’t reason but predict – and what that means for using #AI coding assistants in production systems.
Watch now 👉 t1p.de/lo8ql
#SAGconf #iSAQB
Yet, devs continue to pinch their noses while they chew and swallow config.
2/2
I think a big issue with config is the tension between needing a machine readable format and devs wanting to write it themselves—quickly, no pain, low boilerplate, and min syntax. That's a lot of bad combinations. If it were food, nobody would eat it.
1/2
Readers are brutal. I'll have to be more careful about the free stock photos that I download.
Why that test code was green for the contributing developer: It took 30 seconds to add code to print the value in the failing test, copy the value, and paste it to the toBe(...). Then: priceless photo-op.
That's why perfection is impossible and continuous improvement matters.
4/4
when coverage says "90%" or higher. There were always gaps, always wrong assumptions, always insufficient knowledge. Same now. You find a bug? You create new tests. You will find more later. Even if they are minor, don't forget new and useful functionality that closes newly discovered gaps.
3/4
I have several thousands of tests across four products—probably close to 10,000. I have no more confidence in them than I had before #GenAI. Yes, they help. Yes, they instill a level of confidence. Yet, I can never count on any of those being thorough, let alone complete—not even...
2/4
Vaughn Vernon: PANIC FREE! Specification by Example; Acceptance Testing; Unit Tests; #IDDDWorkshop #DDDesign #DomainDrivenDesign #DDD
Change is hard. So, do we hang on to the past? After all, everybody else does.
That is, except for the rational people. Really. There's a not-so-fine-line between clinging to the past and doing what's necessary to move beyond.
Attend my "Implementing DDD Workshop":
kalele.io/iddd-workshop
1/4
Explore and discover at my #IDDDWorkshop
Regardless of how you produce source code in 2026, how do you know that you are implementing the right thing on purpose? Going 10x-20x faster on the wrong things is wrong. Conventional approaches are completely backwards. Make #DDDesign your differentiator: 23-26 March
kalele.io/iddd-workshop/
DomoTacticalStorage-TS is now available for #ActorModel.
Persistent storage backends for DomoTactical-TS providing #EventSouring Journal and DocumentStore implementations for @kurrent-io.bsky.social KurrentDB/EventStoreDB, @postgresql.org, and @cloudflare.social #D1.
www.npmjs.com/package/domo...
I've been saying for at least 15 years that going all #DDDesign Trojan-Horse:
1. scares the horse
2. won't have troops to push it forward
3. will, if it is pushed, fall down and not get up
4. is unnecessary
REPEAT AFTER ME: Not everyone in our org structure is ADHD.
This is my brief experience report regarding #LLM-based coding assistants.
www.linkedin.com/feed/update/...
Join me for my upcoming @IDDDWorkshop, 23-26 March. It's four half days of advanced #DDDesign, both strategic and tactical design, Ports and Adapters, Event-Driven Architecture, #EventSourcing, and #CQRS, and a lot more.
See link for registration #DDD #DomainDrivenDesign
kalele.io/iddd-workshop
Today I had to drive on public roads. There was a very large sample set of stupid people out there, and it's not New Years Eve. Be careful.
Steve Job's: "Disease of the great idea."
In case you were in a coma, the "In 6 Months..." spiel is dead. And yet...
“In 6 Months, Everything Changes”: A Microsoft Executive Describes What Artificial Intelligence Will Really Look Like in 6 Years
3dvf.com/en/in-6-mont...
The title of my next book:
"Domain-Driven
Dis-Discombobulation"
Thank you, and have a nice day.
"Microsoft Scales Back AI Goals Because Almost Nobody Is Using Copilot"
www.extremetech.com/computing/mi...
MCP is the new API
Try to keep up.
but the point is to be meaningful, clear, and accurate rather than avoiding object disclosure.
2/2
In some cases I consider the "Law of Demeter" more of the "Style of Demeter." When you are designing an "internal DSL," it's very common to favor a fluent, expressive model through object navigation. Sure, your clients (consumers) will pay for any redesigns, ...
1/2
In case you are tempted by the #CyberMonday #MiniPC deals, be aware of the tricks Chinese manufacturers play with CPUs. For example, the AMD Ryzen 7 H 255 is a defective 260 with the XDNA NPU disabled that's rebranded only for the Chinese budget market.
www.reddit.com/r/MiniPCs/s/...
