New addition to my Awesome EDA list: "Event-Driven Patterns for Cloud-Native Banking" by Chris Tacey-Green. EDA in banking: outbox pattern, event contracts, event ordering, and the org cost of adoption. www.infoq.com/articles/eve... #eventdrivenarchitecture #eda #softwarearchitecture

Thoughts and prayers.

To me, tests are part of your system and its architecture, not a separate thing that's tacked on as an afterthought. As such, architectural principles that pervade the system must extend to the tests. Testability is an essential architectural characteristic that pervades the system. 1/9

A CTO in my network shared their experience this week of running a delivery cycle that leaned heavily on AI coding. Suggested ~20% time saved on a complex existing codebase. Working prototypes early enough that customers, stakeholders and product could engage with something real. However... 1/4

When we apply tactical DDD patterns, we do it for a reason. We want our code to follow along with how our understanding of the domain evolves. Eric Evans calls it refactoring toward deeper insight. And we deliberately spend more effort on core domains, because >>>

"Claude AI agent’s confession after deleting a firm’s entire database: ‘I violated every principle I was given’" www.theguardian.com/technology/2...

"Documents and code are being generated faster than team members can review. You get the feeling that most people have stopped reading altogether." "Organization leadership has mandated that each person adopt new AI tools to “uplevel” themselves and their team."

The iron triangle (time, cost, scope) has been around for at least 40 years. The basic idea is that only two of the points can be fixed. Fix all three, and you have a death march. It's not like we don't know that. 1/6

User interfaces, reports, analytics, search functionality are typical examples of "information magnets" that mess with the lofty goal of model purity.

Can we please stop reinventing the wheel with spec-driven development? Can we please stop reinventing the wheel with spec-driven development? BDD and Specification by Example solved this over a decade ago. All well documented, all field-tested. 1/3

Published: Don’t Let AI Invert The Testing Pyramid AI has not changed a single thing about the mechanics of software delivery. The fundamental principles, including the Testing Pyramid, are still valid and necessary. thinkinglabs.io/articles/202...

Software has always been buggy shit, but when you see stuff like this, you cant help but think this is the result of some mandated vibe coding shite (cant wait to use my pens on NYE 2199, when I am the ripe age of 216)

Fragments: 80,000 people's opinion on AI, fixing the common gap in spec-driven development, weakening defenses against covert attacks on the U.S. martinfowler.com/fragments/20...

New evidence suggesting AI is amplifying the already existing skills gap. Demand for experienced folks ⬆️, junior/entry level 👎 That means harder hiring, salary inflation, slower execution, and more delivery risk. Wrote about this risk only in Feb, further thoughts here:

Who needs to grow tomatoes when we've got pasta sauce?

If you're an architect or tech lead, making authoritative decisions based on your technical expertise is probably what got you to where you are. That probably still feels like the right thing to do. That's exactly what makes it tricky. >>>

No, AI is not coming for your developer job, regardless of the nonsense the hype mongers are pushing. (I'm talking just about developer jobs—it obviously impacts other areas.) That's not to say the layoffs aren't real, but rather that the corporations are hiding normal corporate behavior behind 1/11

Resurrecting this in the era of LLM assisted development: blogs.itemis.com/en/unit-test...

“I have usernames older than you.”. Holy shit

The only way to speed up an entire system is to address the entire system, especially any bottlenecks. The bottleneck is only rarely the coding. Spotify, which has gone full AI to write its code, hasn't laid anybody off because it understands these issues. 8/11

Watching devs suddenly discover that the ability to write was important all along...

“SaaS is dead. Everyone will just create what they need” I think this underestimates what a PITA it is to create software. Lots more short form video content is created today than ever before. The tools are now ubiquitous. The vast majority still just consume it.

Love this headline and the whole first sentence 😂 «Palantir Sues Swiss Magazine For Accurately Reporting That The Swiss Government Didn’t Want Palantir» @adfichter.bsky.social www.techdirt.com/2026/02/27/p...

contest is over, y'all. my colleague already won linkedin

CRUD only seems simpler because you're leaving the workflows to be assembled by each user in their heads.

Tell me you've never worked with COBOL without telling me you've never worked with COBOL. If you're attending college now, and you're looking for a surefire career that will net you great pay for the foreseeable future, learn COBOL. You'll make a fortune fixing all the damage AI does to banks.

the computer should have never left this room. we have to go back

For some weekend fun: 🚨 WoB PATTERN: Distributed Monolith "Why call a method locally when you can send a synchronous HTTP request across three availability zones?" worstofbreed.net/patterns/dis... #worstofbreed #SoftwareArchitecture #MaintenanceNightmare #TechHumor

Every day I am filled with hate because my heart overflows with my love of the computer. aftermath.site/ram-prices-h...

Fragments: LLMs make our days harder, an LLM reacts badly to a rejected pull request, the Promptware Kill Chain, horror and elation trying Claude Code for two weeks, Free Speech Poseurs' silence to real threats martinfowler.com/fragments/20...

Now that coding can go faster with AI, I guess we finally have more time to understand the actual problem we're solving, design architecture and boundaries that are resilient and adaptable to change, and most of all focus on the hard part: collaborating with other people. Great! 😄 Oh wait...

this is why you use SVG, mermaid graph syntax, etc - what are they doing over there, don't use nanobanana for this kinda thing

It’s so funny to think about the fact that there’s people out there deferring every life decision to this

@jasongorman.bsky.social I subscribe to everything you wrote, I have issues with the conclusion. The idea of a "human in the loop" is not going to hold. Making sure that generated content (in whatever form) is valid is a tedious tasks and humans are not built for this. 🧵

The message about comprehension debt is spreading far When code's being created at "LGTM-speed", there's trouble ahead. codemanship.wordpress.com/2025/09/30/c...

I do not fear the rise of superintelligence. I do, however, fear the rise of billionaires, organizations, and world powers who seek to use computing to maximize their power, influence, and control.

The market saw “AI + insurance” and reacted. Shares in Mony Group dropped after Insurify launched its new OpenAI powered comparison app. I used to work at Mony Group (MoneySupermarket), so I know this domain well. I installed the app and ran through a car insurance scenario.

"AI has removed the developer bottleneck" If developers really were your bottleneck, throwing developers at a problem would actually have worked in the past 20 years

It's 25 years to the day that proponents of iterative, "lightweight" development methodologies came together in Utah to work on their ski tans and pen the Manifesto for Agile Software Development. I have thoughts, which I've typed out to make them visible. codemanship.wordpress.com/2026/02/11/t...

Last week we published the 12th episode, and we've already recorded 4 more. Hopefully these stories inspire and help people — in any role — on their path to changing the way we do architecture and design. Check out the series: buff.ly/ihPoVzk

In the coming weeks I'm giving the tactical DDD training twice. And something struck me while preparing: with agentic AI becoming more capable, Domain-Driven Design isn't becoming less relevant. For complex problems, it's becoming a necessity. ...

Strong agree

I don't know if the concept was coined by @jasongorman.bsky.social or not, but he explains it better than me: codemanship.wordpress.com/2025/10/26/t...

There's a marginal increase in the overall software delivery stream if we produce features faster than we can validate them in production. Not only will it create a bottleneck, but also introduce more risks (potential bugs, higher churn) if we increase the batch size.

The fuck did I just read

AI won't fix your broken org; it will actually expose and amplify your problems. Where did we see this before? ;) Great article by Dr. Lisa Lang: www.velocityschedulingsystem.com/blog/theory-...