Fran Díaz

Están desesperados. Hay mucho dinero invertido y cada vez menos perspectivas. Esto no está reñido con su utilidad como herramienta, pero no son ni mucho menos el reemplazo de la mano de obra que quieren vender. Solo espero que el batacazo financiero ocurra pronto, ya solo por la paz mental

Nobody knows what programming will look like in two years Kent Beck doesn't know what programming will look like in two years, and he's been thinking about this longer than most of us.

leaddev.com/ai/nobody-kn...

Unacceptable

a 90s wooden computer desk with towers and drawers and lots of storage

this was basically the model we had. it was glorious. we've strayed so far from the light

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

Pattern card: Distributed Monolith (Architecture). Stats: Latency 95/100, Pain 99/100, Maintain 5/100, Resume HIGH. Quote: "Why call a method locally when you can send a synchronous HTTP request across three availability zones?". Special ability: Cascading Failure - If one service fails, the entire cluster throws 500s. Stack trace size: 400MB.

# Analysis The result of taking a spaghetti codebase and throwing it across the network. Driven by the cargo cult of "Microservices," architects often slice a highly coupled system into smaller pieces without actually establishing bounded contexts or autonomous data ownership. You haven't decoupled your domains; you've merely decoupled your deployment artifacts. By doing so, you have successfully replaced highly optimized, in-memory local function calls with unreliable network hops, JSON serialization overhead, and eventual inconsistency. **The Reality:** To deploy a single, trivial feature, four different teams must orchestrate their releases in a highly specific, coordinated sequence, essentially recreating Waterfall over a CI/CD pipeline. Local development is practically impossible unless developers are issued laptops with 64GB of RAM to run 15 interdependent containers via `docker-compose`. When a user clicks "Checkout", the system initiates a fragile, synchronous HTTP chain reaction across six different services. If just one sidecar proxy hiccups, the entire transaction collapses, leaving the database in an inconsistent state and generating a distributed stack trace large enough to trigger your logging provider's billing alerts. You traded a simple `NullPointerException` for a `504 Gateway Timeout`.

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

It's amazing that coding agents allow you to build quickly to validate ideas. But the outcome should be treated as a throw-away prototype. A long term sustainable software requires skilled developers because of the reasons Allen exposed

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

Fragments: February 19 fragments 19 Feb 2026

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...

And allow me to clarify: I do not expect to provide a spec, API and go to sleep expecting the rest to be automated and deterministic. But have an inspection loop, TDD style: provide minimum spec, prompt to implement, run and verify tests, increment spec, repeat.

Of course, by no means I meant that an LLM is an abstraction like modern languages and compilers are over assembler. I meant devs operating and directing the process at a higher abstraction level: Gherkin style specs, APIs, modules...

I mean wouldn't the human be in the process of building but just a different level of abstraction?

Couldn't such knowledge be acquired along the process if the loop starts with the dev providing a module boundary and executable specifications BDD style? The API is the abstraction that grows as part of such a process where the human is in the loop and it is our responsibility that feels natural.

I'm with you here. However what do you think if devs follow are in the loop enforcing modularity, where such modules expose meaningful abstractions and BDD style tests for example? Devs would still keep a mental model of the system components and their behaviors, just as black boxes. Right?

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.

The Bottleneck That Wasn't Here's the punchline already at the start: If you say you addressed a bottleneck in the system (coding), and then you claim it moved to some other place (e.g.

open.substack.com/pub/draganst...

Besides that, I would like to know what these studies understand by productivity. Lines of code? Merge requests? Features shipped? Even if the latter, shipping larger batches may increase the likelihood for defects and higher churn.

"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

The Agile Manifesto at 25 – The Most Talked-About Unread Document In Software Feb 11th 2001 – exactly 25 years ago – was the first day of a 3-day meeting at the Snowbird ski resort in Utah that gave birth to the Manifesto for Agile Software Development. Like all …

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...

Stories on Facilitating Software Architecture & Design - Virtual Domain-Driven Design We’ve consistently observed a common pattern: regardless of the architectural approach—from traditional enterprise to more hands-on, emergent methods—teams face similar obstacles when building…

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

Fair. Since you say "at least for business code", am I assuming right that we would need at least to provide test code as a sort of specification then?

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.
...

AI is a High Pass Filter for Software Delivery A high-pass filter (HPF) is a circuit or software algorithm that allows signals with frequencies above a certain cutoff to pass while reducing those below it.

Strong agree

The AI-Ready Software Developer #10 – Comprehension Debt In my previous post, I talked about the need to recognise when an “AI” coding assistant is circling the event horizon of a “doom loop” and take the wheel. Taking the wheel, …

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...