RSSAmplifier

Blog

Software engineering is decision making on Barry Hennessy

Recent content in Software engineering is decision making on Barry Hennessy

barryhennessy.comRSS feed ↗47 posts

Latest posts

The finest of standups

I have been in truly good standups. It was nice. I would like you all to have that experience too. Moreover I would like that you all can stop experiencing such limp-coffee standups. You know the ones. The perfunctory ones. The low energy ones. The norm . Have you held these beliefs? Be honest: Standups are to make sure we’re at our desks on time. Standups are to make sure nobody’s…

Flexibility and Discipline

I’ve taken a few solid swings at picking up Clojure, but something just never quite clicked. I like the idea of it. I like the pitch of it. It very much tickles my engineering fancy. But I never got to that productive, smooth place. Then a few years ago it hit me: the thing getting in the way wasn’t Clojure. It was me. Since then I’ve seen the same pattern pop up throughout…

Automation Paradox - Original Draft

link here: https://www.linkedin.com/posts/ashley-frieze_heres-the-ai-fallacy-that-the-junkies-are-activity-7411011732246007808-jHRp?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAlGRrEBiJl3WYxHcYWhKP0pz9RSvtCmRkU Software Engineers’ value is - roughly speaking - in automating processes - we make machines generate value 1 like tireless robotic hamsters in little virtual wheels.…

The Automation Paradox: How Software Engineers Create Their Own Commodities

The Irony of Automation in Software Engineering Software engineers create value by automating processes. We build systems that generate value tirelessly—like robotic hamsters in virtual wheels. But here’s the paradox: when a process becomes fully automated, it often transforms from a competitive advantage into a commodity. This isn’t just theoretical. It’s happening across our…

The Automation Paradox: How Software Engineers Create Their Own Commodities

The Irony of Automation in Software Engineering Software engineers create value by automating processes. We build systems that generate value tirelessly—like robotic hamsters in virtual wheels. But here’s the paradox: when a process becomes fully automated, it often transforms from a competitive advantage into a commodity. This creates an uncomfortable tension. We celebrate automation as…

The Automation Paradox: When Making Things Easier Makes Them Worth Less

Software engineers automate processes. We make machines generate value[^1] like tireless robotic hamsters in little virtual wheels. Ironically, the moment a process gets fully automated, it becomes a commodity. Enough competitors automate it, and price gets dictated by supply/demand, not the value it creates. The Web Development Story Take web development from the early 2000s. If you knew HTML,…

The Automation Paradox: When Making Things Easier Makes Them Worth Less

Software engineers automate processes. We make machines generate value[^1] like tireless robotic hamsters in little virtual wheels. Ironically, the moment a process gets fully automated, it becomes a commodity. Enough competitors automate it, and price gets dictated by supply/demand, not the value it creates. Take web development - once a killer money spinner. People couldn’t make websites,…

The Automation Paradox: When Making Things Easier Makes Them Worth Less

Software engineers automate processes. We make machines generate value[^1] like tireless robotic hamsters in little virtual wheels. Ironically, the moment a process gets fully automated, it becomes a commodity. Enough competitors automate it, and price gets dictated by supply/demand, not the value it creates. Take web development - once a killer money spinner. People couldn’t make websites,…

The Automation Paradox: When Making Things Easier Makes Them Worth Less

Software engineers automate processes. We make machines generate value[^1] like tireless robotic hamsters in little virtual wheels. Ironically, the moment a process gets fully automated, it becomes a commodity. Enough competitors automate it, and price gets dictated by supply/demand, not the value it creates. Take web development - once a killer money spinner. People couldn’t make websites,…

The Automation Paradox: When Making Things Easier Makes Them Worth Less

Software engineers automate processes. We make machines generate value[^1] like tireless robotic hamsters in little virtual wheels. Ironically, the moment a process gets fully automated, it becomes a commodity. Enough competitors automate it, and price gets dictated by supply/demand, not the value it creates. Take web development - once a killer money spinner. People couldn’t make websites,…

The Automation Paradox: When Making Things Easier Makes Them Worth Less

Software engineers automate processes. We make machines generate value 1 like tireless robotic hamsters in little virtual wheels. Ironically, the moment a process gets fully automated, it becomes a commodity. Enough competitors automate it, and price gets dictated by supply/demand, not the value it creates. Take web development - once a killer money spinner. People couldn’t make websites,…

The Automation Paradox: Why Software Engineers Create Their Own Commoditization

Software engineers create value by automating processes. We build systems that generate value tirelessly, like robotic hamsters in virtual wheels. But here’s the cruel irony: when automation truly succeeds, it transforms skilled work into a commodity. This is the automation paradox, and it’s reshaping how we think about our craft. The Web Development Graveyard Remember when web…

The Automation Paradox: Why Software Engineers Create Their Own Commoditization

Software engineers create value by automating processes. We build systems that generate value tirelessly, like robotic hamsters in virtual wheels. But here’s an interesting observation: when automation truly succeeds, it opens new opportunities for skilled work. This is the automation paradox, and it’s reshaping how we approach our craft. The Web Development Evolution Remember when web…

The Automation Paradox: Why Software Engineers Create Their Own Commoditization

Software engineers create value by automating processes. We build systems that generate value tirelessly, like robotic hamsters in virtual wheels. But here’s an interesting observation: when automation truly succeeds, it opens new opportunities for skilled work. This is the automation paradox, and it’s reshaping how we approach our craft. The Web Development Evolution Remember when web…

The Automation Paradox: Why Software Engineers Create Their Own Commoditization

Software engineers create value by automating processes. We build systems that generate value tirelessly, like robotic hamsters in virtual wheels. But here’s an interesting observation: when automation truly succeeds, it opens new opportunities for skilled work. This is the automation paradox, and it’s reshaping how we approach our craft. The Web Development Evolution Remember when web…

The Automation Paradox: Why Software Engineers Create Their Own Commoditization

Software engineers create value by automating processes. We build systems that generate value tirelessly, like robotic hamsters in virtual wheels. But here’s an interesting observation: when automation truly succeeds, it opens new opportunities for skilled work. This is the automation paradox, and it’s reshaping how we approach our craft. The Web Development Evolution Remember when web…

Decision-Driven Development Retainer

Learn and apply Decision-Driven Development methodology through hands-on collaboration with guaranteed monthly hours.

The Automation Paradox

Software engineers automate processes. We make machines generate value 1 like tireless robotic hamsters in little virtual wheels. Ironically, the moment a process gets fully automated, it becomes a commodity. Enough competitors automate it, and price gets dictated by supply/demand, not the value it creates. Take web development - once a killer money spinner. People couldn’t make websites,…

[Result-Focused Headline]

[Result-Focused Headline] Example: “How a Growing SaaS Company Reduced Infrastructure Costs by 60% While Improving Performance” The Situation Industry: [e.g., FinTech, Healthcare, E-commerce] Challenge: Brief description of what the client was facing from a business perspective (2-3 sentences). Focus on the problem they needed to solve and why it mattered to their business. The Problem…

Decision Sandwich

I found myself in a decision sandwich today. Those moments when you are stuck between a decision you just made, and the decision that follows, but you can’t make just yet. Blocking; stuttering ; stumbling toward completion. They’re “you can’t move on, but you can’t leave either” moments. The “I’ve decided to deploy… now to wait and decide if I…

Software Design Services

A guided decision-making track to design, refine, and ship systems with clarity on goals, options, and trade-offs.

Don't Believe the Tools

I have worked with some tools for years. I like them. I trust them. I rely on them. But I do not believe in them. I don’t believe in any technology. And as engineers I don’t think we should. Technologies are neither pets nor ideologies; they’re tools. Some are fast and strong. Some are tough and reliable. Some have saved your ass. Others make an awful mess of the place; and…

AI Is Going to Be Something

AI really is going to be something 1 . What exactly? I have no idea. Theories range from: The end of the world (for us) The end of your job A revolutionary tool that could expand human capacity But there’s another possibility I’d like to throw in the mix: A useless tool we’re stuck with. Useless!? Right now there are many pitfalls to using generative AI in practice: Prompt…

Rest Your Weary Head

Software engineers spend a lot of time in their head. If you’re anything like me your head can generate ideas like a “how it’s made” factory at full speed 1 . Some of them are useful at the time, others are great ideas that don’t help you cook dinner and some … well the sooner they’re done with the better. In lieu of any great theory I want to let my…

Does it reduce your decision workload

In software engineering the question “Does it reduce my decision workload?" can be a great guide in almost all situations 1 . Because if you view software engineering as decision making then your decision workload is your software engineering workload. An example is in order Take the decision: Should we implement this service by plugging together off the shelf components or primarily build it…

Clean code, clean decisions

Clean code, code quality, refactoring code, tidying up. Whatever name you give it, the difference between a messy codebase and a clean one is unmistakable - to software engineers. To those outside, looking in, our frustration working in an unclean codebase can be mystifying. And our needs for time to clean our code can appear anywhere from surprising to downright baffling. Code is, frankly,…

Shorthand, longdiscussion

“Bing!” 7:14pm and I’m still stuck, staring at Slack 1 . No! When you pay the status should be ‘RESERVED’ Didn’t you just say it was a number?? That’s the other status. Just make sure it’s ‘RESERVED’ Ok, sure. Reserved. Got it. So what about the other status? Which one? Didn’t you just say there’s another one? Oh, that other…

Laziness and infinite productivity

I was only a few months out of college when I got my first taste of what I’ve come to call ‘infinite productivity’. I found myself in a meeting room with our most senior engineering lead, Mike, and Paul from what I then naïvely thought of as ’the business side'. Like any young engineer eager to prove themselves I was absolutely terrified I’d say the wrong thing and…

THROW DATABASE 'away'

The biggest event your company will see for two years is fast approaching. Life or death for the startup. Everyone is gearing up, finishing off new features, load testing like it’s 1999. It’s all going to be fine. Except, you’ve got a problem. That older system. The one with the MVP 1 you grafted on. It’s not going to make it; it’s not going to scale. You don’t have much choice.…

(untitled)

Case Study Creation Guide for LLMs This guide provides comprehensive instructions for creating effective case studies for Barry Hennessy’s consulting website. Use this to understand the context, structure requirements, and quality standards for generating new case study content. IMPORTANT: Always read content/plans/AGENTS.md FIRST for site-wide guidelines on SEO, tone, quality standards, and…

(untitled)

To enable rapid onboarding of new partner platforms in a fast-moving, high-value ecosystem, I modernised a fragmented and expanding landscape of ~11 microservices. Through an intensive design sprint I identified shared requirements, standardised event flows, and delivered a simple platform library and system template that allowed several services to be simplified, replaced, or fully retired, while…

(untitled)

Content Generation System This document explains how to use the Obsidian-based content generation system for creating Hugo blog content using LLMs. Overview The system uses Obsidian markdown files stored in plans/ directories as content outlines. Each content type (services, posts, etc.) has an AGENTS.md file that guides LLMs in generating properly formatted Hugo content. Important : plans/…

(untitled)

Blog Post Creation Guide for LLMs This guide provides comprehensive instructions for creating engaging blog posts for Barry Hennessy’s technical writing. Use this to understand the context, structure requirements, and quality standards for generating new blog content. IMPORTANT: Always read content/plans/AGENTS.md FIRST for site-wide guidelines on SEO, tone, quality standards, and brand…

(untitled)

Blog Post Creation Guide for LLMs This guide provides comprehensive instructions for creating engaging blog posts for Barry Hennessy’s technical writing. Use this to understand the context, structure requirements, and quality standards for generating new blog content. IMPORTANT: Always read content/plans/AGENTS.md FIRST for site-wide guidelines on SEO, tone, quality standards, and brand…

(untitled)

link here: https://www.linkedin.com/posts/ashley-frieze_heres-the-ai-fallacy-that-the-junkies-are-activity-7411011732246007808-jHRp?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAlGRrEBiJl3WYxHcYWhKP0pz9RSvtCmRkU Software Engineers’ value is - roughly speaking - in automating processes - we make machines generate value 1 like tireless robotic hamsters in little virtual wheels.…

(untitled)

link here: https://www.linkedin.com/posts/ashley-frieze_heres-the-ai-fallacy-that-the-junkies-are-activity-7411011732246007808-jHRp?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAlGRrEBiJl3WYxHcYWhKP0pz9RSvtCmRkU Software Engineers’ value is - roughly speaking - in automating processes - we make machines generate value 1 like tireless robotic hamsters in little virtual wheels.…

(untitled)

link here: https://www.linkedin.com/posts/ashley-frieze_heres-the-ai-fallacy-that-the-junkies-are-activity-7411011732246007808-jHRp?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAlGRrEBiJl3WYxHcYWhKP0pz9RSvtCmRkU Software Engineers’ value is - roughly speaking - in automating processes - we make machines generate value 1 like tireless robotic hamsters in little virtual wheels.…

(untitled)

link here: https://www.linkedin.com/posts/ashley-frieze_heres-the-ai-fallacy-that-the-junkies-are-activity-7411011732246007808-jHRp?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAlGRrEBiJl3WYxHcYWhKP0pz9RSvtCmRkU Software Engineers’ value is - roughly speaking - in automating processes - we make machines generate value 1 like tireless robotic hamsters in little virtual wheels.…

(untitled)

link here: https://www.linkedin.com/posts/ashley-frieze_heres-the-ai-fallacy-that-the-junkies-are-activity-7411011732246007808-jHRp?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAlGRrEBiJl3WYxHcYWhKP0pz9RSvtCmRkU Software Engineers’ value is - roughly speaking - in automating processes - we make machines generate value 1 like tireless robotic hamsters in little virtual wheels.…

(untitled)

link here: https://www.linkedin.com/posts/ashley-frieze_heres-the-ai-fallacy-that-the-junkies-are-activity-7411011732246007808-jHRp?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAlGRrEBiJl3WYxHcYWhKP0pz9RSvtCmRkU Software Engineers’ value is - roughly speaking - in automating processes - we make machines generate value 1 like tireless robotic hamsters in little virtual wheels.…

(untitled)

Service Page Creation Guide for LLMs This guide provides comprehensive instructions for creating professional service pages for Barry Hennessy’s consulting website. Use this to understand the context, structure requirements, and quality standards for generating new service offerings. IMPORTANT: Always read content/plans/AGENTS.md FIRST for site-wide guidelines on SEO, pricing, tone, quality…

(untitled)

Impressum

Anbieter / Provider Barry Hennessy, Software-Entwicklung und technische Beratung / Software engineering and technical consulting. Gotenstrasse 53 10829 Berlin Kontakt / Contact E-Mail: impressum@barryhennessy.com Telefon: +49 1 5259753167 Umsatzsteuer-Identifikation / VAT identification Umsatzsteuer-Identifikationsnummer gemäß § 27 a Umsatzsteuergesetz: DE319517688 Angaben zur…

Let's Connect

Hi, I’m Barry I help technical leaders and teams make clearer decisions and move faster. Whether you need hands-on development work, consulting support, or just have a question—let’s start a conversation. What works best for you? Schedule a call 15-minute chat — Quick intro to see if we’re a fit 30-minute deep dive — Discuss your specific needs in detail Book a 15-minute call →…

Redirecting...

Safe AI on Your Systems

Your APIs. Their AI. Under your control. The problem you’re in Your merchants — or your teams — want more than you can build. The backlog grows. The pressure to “do AI” is real, but you’re not handing over API keys and hoping for the best. You need a way to let users and AI do useful things with your systems without opening the vault. Hecate is that control layer: they get…

Services

Explore offers and ways to work together. Each service can flex between sprints, retainers, and workshops.