What Remains for Software Developers When AI Writes Code?

What the research says about AI and software development, and why I think fundamentals and review are still the job.

When AI Writes the Code, the Engineer's Work Moves

A plausible 200 response, an inactive customer and the rule missing from the requirement.

Circuit Breaker in MuleSoft: When Retry Makes Things Worse

Retry alone turns a degraded backend into an integration outage. A public, measured, tested plugin shows the difference — and what changes once you add replicas on CloudHub 2.0.

Delivering MuleSoft applications with Azure DevOps · Part 2 of 4

Versioning Mule applications with the Maven release plugin in Azure Pipelines

release:prepare and release:perform explained step by step, running inside Azure Pipelines — detached HEAD, pushing with the pipeline token, [skip ci] and branch protection.

SOLID in MuleSoft · Part 6 of 6

Dependency Inversion in MuleSoft: business flows that own their abstractions

DIP is not externalised configuration. It is the business flow defining the model it needs and adapters conforming to it — shown in Mule 4 with swappable ERP and in-memory implementations.

Delivering MuleSoft applications with Azure DevOps · Part 3 of 4

Azure Pipelines templates for MuleSoft: one delivery flow, many applications

How to structure versioned Azure Pipelines templates for Mule applications — stages, jobs and steps, secrets without secure files, and why MUnit is left out of a public pipeline.

Delivering MuleSoft applications with Azure DevOps · Part 4 of 4

Deploying to CloudHub 2.0 from Azure Pipelines: build once, approve, verify

Promote the same Exchange artifact through test, uat and prod on CloudHub 2.0, with approvals on Azure DevOps environments and a smoke test after every deployment.

Delivering MuleSoft applications with Azure DevOps · Part 1 of 4

GitFlow for MuleSoft: branch rules a pipeline can act on

Why GitFlow still fits scheduled MuleSoft releases, where it doesn't, and how to turn branch names into pipeline behaviour — with a working reference project.

SOLID in MuleSoft · Part 5 of 6

Interface Segregation in MuleSoft: an API for each consumer

One order endpoint that returns everything to everyone, split into consumer-shaped interfaces — and why the strongest argument for ISP in integration is data exposure.

SOLID in MuleSoft · Part 4 of 6

Liskov Substitution in MuleSoft: implementations that can replace each other

Mule has no inheritance, but LSP still bites: two adapters behind one contract, where the new one keeps the field names and quietly changes their meaning.

SOLID in MuleSoft · Part 3 of 6

Open/Closed in MuleSoft: extending without editing, and what it costs

Adding a payment method to a Mule 4 app without touching the router — with config-driven dynamic routing, MUnit evidence, and an honest look at the trade-offs.

SOLID in MuleSoft · Part 2 of 6

Single Responsibility in MuleSoft: one reason to change per flow

SRP is not about small flows. It is about grouping logic by the reason it changes — shown with a Mule 4 order flow before and after, with MUnit tests.

SOLID in MuleSoft · Part 1 of 6

SOLID in MuleSoft: what carries over from object-oriented design, and what doesn't

A code-backed look at the five SOLID principles in Mule 4 — where each one fits integration work, where it needs translating, and where it stops being useful.