Just published: pull requests are the routine human gate that survived a pipeline whose sole purpose is to remove them.

Andrea Laforgia’s “Stop Using Pull Requests” pulls the receipts together — the defect-detection rate, the queue waste, DORA’s review-speed lever. His name for the alternative is T*D: Test-Driven, Trunk-Based, Team-Focused Development. If you’re running the Delivery Playbook, you already know what each leg looks like.

#engineering #softwaredelivery #dev
https://blog.bosslogic.com/p/pull-requests-are-a-symptom-of-low-trust

The single most predictive variable for an engineering team's output is the cycle time of "I changed the system — do I know whether it broke?"

Not headcount. Not process maturity. The loop.

Sub-30-second loops produce teams that refactor freely and find bugs by accident. Twenty-minute loops produce teams that stop refactoring and find bugs in production.

Every other engineering investment gets cheaper when the loop is short. Shorten it first.

#engineering #softwaredelivery #devops

Taking a walk to solve a problem isn’t passive. It has rules.

Load the problem first. Pick the right pace and place. Phones away — incoming notifications collapse the mental space the walk is supposed to create. Don’t take too long; there’s a sweet spot between fifteen minutes and an hour. Come back ready to capture what landed.

#creativity #productivity #engineering
https://blog.bosslogic.com/p/do-this-to-find-your-inspiration

Domain driven design isn’t free. It’s an investment in shared modeling that pays off at certain scales of complexity and underwhelms at others.

For a small CRUD app, DDD overhead doesn’t earn its keep. For a system with multiple integrating subsystems and several years of expected lifetime, it’s the difference between coherence and entropy.

Knowing which side you’re on is the start of using DDD well.

#softwarearchitecture #ddd #softwaredesign
https://blog.bosslogic.com/p/30-minute-guide-to-domain-driven-design

Most architecture reviews ask “is this the right choice?”

Wrong question. The right one is “if this turns out wrong, how much of the system pays the bill?”

Reversibility is the architect’s real job. Picking the right path matters less than designing the system so the next team can pick a different one.

The seams aren’t accidents — they’re permission slips for everyone who comes after.

#softwarearchitecture #engineering

John Cutler: “The translation was never just a tax. It was also a learning mechanism.”

The friction we keep trying to remove with AI is also where shared understanding gets built. Strip it without thinking and you get legibility without comprehension.

Three engineers reading the same spec and coming to three slightly different interpretations isn’t a bug. It’s where the alignment conversation starts.

#engineering #ai #softwareengineering
https://cutlefish.substack.com/p/tbm-421-minimally-viable-consistency

Abi Noda's 16-month study of 400+ engineering orgs: AI adoption climbed 65%. PR throughput climbed 8%.

Coding is ~14% of an engineer's week. If AI accelerates only coding, the overall ceiling is mathematically low.

The teams getting more aren't the ones with better tools. They're the ones extending AI past coding — into discovery, planning, validation. The other 86%.

#engineering #ai #devops
https://newsletter.getdx.com/p/ai-productivity-gains-more-modest-than-expected

A five-day gap in my daily notes cost me a deliverable that was already overdue when I came back.

The work didn't degrade in the gap — it stayed invisible. The note isn't a log. It's what pulls due-soon items into view before they pass.

Skip the ritual, lose the surfacing.

#engineering #productivity

Most "professional communication" is broadcast: slides, memos, status updates, agendas. Outbound, structured, one-directional.

Conversation is investigation. A back-and-forth where the other person’s words change what you say next. You find out what they need, not what you assumed they needed.

Most of us are mostly broadcasting. The career return on switching is enormous.

#leadership #communication #careers
https://blog.bosslogic.com/p/knowing-your-coworkers-your-boss

A steel thread is feature-complete in its narrow slice — not feature-light, not a prototype, not a "we’ll harden it later" stub.

A prototype is allowed to fake the parts that are hard. A steel thread isn’t. Every piece touches production-grade code, narrowed to a single slice but real all the way down. The discipline is what makes the thread useful.

#engineering #softwarearchitecture #softwaredelivery
https://blog.bosslogic.com/p/solve-delivery-with-a-steel-thread