Tagged software-development
-
Extreme DRY: When ‘Don’t Repeat Yourself’ Repeats All Your Other Problems
Or: How the Engineering Principle You Learned First Quietly Strangles the Architecture You’re Trying to Build
-
The Floor Plan Is Your First Architecture Decision
Or: Your Seating Chart Is Picking Your Software Architecture, Whether You Like It or Not
-
Design Thinking Is Not a Workshop — It’s a Hiring Criteria
Or: Why Your Two-Day Empathy Exercise Won’t Fix a Feature Factory
-
The Directness Dial: Teaching Engineers to Be Honest Without Being Brutal
Or: Why “Too Respectful” Is Just as Dangerous as “Too Blunt”
-
Teaching the Agent What You Know: How to Build, Test, and Ship AI Coding Skills That Actually Hold…
Or: Your AI Assistant Is as Naive as the Day It Was Hired — and That’s Your Fault
-
Teaching Engineers to Speak in Constraints
Or: Why “We Can’t Do That” and “Sure, No Problem” Are Both Lies
-
The Biggest Problem With Our Codebase Is the Developers
Or: What Platform Teams Actually Exist For (And Why Most Get It Completely Backwards)
-
Introducing DX Telemetry Manager
Or: An Open Source Dashboard for the Developer Inner Loop
-
What We Actually Instrumented — and What We Found
Or: Three Engineers, One Hardware Correlation, and the Test Suite Nobody Was Running
-
The Inner Loop Nobody Measures
Or: Why Your Production Monitoring Is Excellent and Your Developer Experience Is a Black Box
-
What It Looks Like When It’s Working
Or: The Engineer Who Brings You Problems You Didn’t Know You Had
-
Ask for Forgiveness, Not Permission
Or: The Four Words That Changed How an Entire Room Understood Failure
-
The Process That Punishes the Behaviour You’re Building
Or: Why Your Engineers Stopped Taking Initiative — and Scrum Helped
-
Why Your Engineers Are Still Waiting
Or: The Ownership Problem Nobody Admits They Created
-
The Thematic Quarter: Why Your OKRs Are Fighting Each Other
Or: How a Book About Silos Changed How We Set Goals
-
Your New System Is Done. Now Good Luck Getting 40 Teams to Care.
Or: What Nobody Tells You About Retiring a Legacy System
-
Knowing It’s Fixed: How to Actually Validate a Performance Improvement
Or: Shipping a Fix Is Not the Same as Knowing It Worked
-
Where Web Performance Actually Lives
Or: Why Your Frontend Engineer Can’t Fix What Isn’t a Frontend Problem
-
Your Performance Dashboard Is Lying to You
Or: How to Actually See the Problem Before You Try to Fix It
-
A Brief History of Web Performance at Agoda
Or: What Ten Years of Measuring the Wrong Things Taught Us About Measuring the Right Ones
-
When Designers and Engineers Disagree (And Both Are Right)
Or: Why the Best Products Come from Arguments Nobody Wins
-
The Business Logic Your Engineers Can’t See
Or: Why Technical Excellence Without Domain Understanding Is Expensive
-
Stop Copying Prod Into Dev: Test Data Strategies That Actually Scale
Or: Your Database Snapshots Are a Confession, Not a Solution
-
The History Lesson Nobody Wanted: Why Your Team Is Living in 1985
Or: How We Forgot What Agile Actually Meant and Built a Cargo Cult Instead
-
The Lego Problem: Why Engineers Add Complexity Instead of Removing It
Or: Why Your Architecture Reviews Have a Benefit Slide and No Cost Slide
-
Designing APIs That Outlive Your Current Sprint
Or: Why Your API Contract Is the Most Important Code You’ll Never Unit Test
-
Show Me the Architecture and I’ll Show You the Silos
Or: How We Broke Down Our Monolith and Accidentally Built Walls Between Our Teams
-
Resilience Isn’t a Feature — It’s the Absence of Naivety
Or: Why Your System Is One Slow Query Away from a Very Bad Night
-
The Bug That Won
Or: Why Your Best Experiment This Quarter Might Be Sitting in Your Bug Backlog
-
Your DNA Document Is Dead Without a Voice: How Recognition Shapes Engineering Culture
Or: The CTO’s Loudest Tool Isn’t a Strategy Doc — It’s a Slack Message
-
The T-Shaped Trap: Why Your Org Says It Wants Versatile Engineers but Punishes Them for It
Or: Stop Hiring Full-Stack Engineers and Start Building Full-Stack Teams
-
Your Engineers Don’t Trust Your Data (And They’re Probably Right)
Or: Why Your Analytics Pipeline Is the Most Expensive Lie in Your Stack
-
The Signature Question: How Culture Actually Spreads
Or: Why Your Values Document Is Collecting Dust While One Person’s Habit Is Rewriting Your Organisation
-
Your Senior Engineers Are Trapped in Sprint Tickets — And You Put Them There
Or: Why Giving Someone a Title Without Giving Them Time Is Just Gaslighting with Extra Steps
-
The UX Debt Nobody’s Tracking: Why Your Engineers Think “Working” Means “Done”
Or: Why Your Feature Works Perfectly and Ruins Lives
-
Your Meetings Are Broken (Yes, Even the In-Person Ones)
Or: Why Being in the Same Room Doesn’t Mean You’re in the Same Conversation
-
The Prototype That Became Production
Or: Why “It Was Only Supposed to Take Two Sprints” Is the Most Expensive Sentence in Software
-
Your Team Is Too Respectful (And It’s Killing Your Product)
Or: Why Silence Isn’t Agreement and Nodding Isn’t Understanding
-
Your Engineers Can’t Negotiate — And It’s Your Fault
Or: Why “We Can’t Do That” and “Sure, No Problem” Are Both Career-Limiting Answers
-
Experimentation Theatre: The A/B Test That Taught You Nothing
Or: Why Running 200 Experiments a Quarter Doesn’t Mean You’re Learning
-
Is This Scrum, or Is This Just Meetings?
Or: A Diagnostic for the Disease Nobody Admits They Have
-
Developer Experience Is a Product — You Just Don’t Have a Product Manager for It
Or: You Already Know How to Build Products. You Just Forgot Your Developers Are Users Too.
-
The Solutioneering Trap: Why Your Best Engineers Are Solving the Wrong Problems
Or: How a Perfectly Good Prototype Taught Me We Were Asking the Wrong Question
-
Recognition Is a Safety Signal (Not a Reward)
Or: Why Your Team Already Knows What You Actually Value — Even If You Haven’t Said It
-
Co-location, Remote First, and the Rollback Every Few Decades
Or: Why the Most Important Architecture Decision Is Your Floor Plan
-
Why Empathy Is a Technical Skill
Or: Your Users Aren’t Edge Cases, and Neither Are Their Feelings
-
Silent Standby: The Invisible Tax on Your Engineering Velocity
Or: Why Your Sprint Is a Two-Week Hiding Spot for Waiting
-
The Tech Time Tightrope: Why Scrum Has No Handle for Technical Health
Or: How to Stop Drowning in Debt When Your Process Only Speaks Features
-
The Security Afterthought: Why You Won’t Care Until You’re on the Front Page
Or: Why Your Security Culture Needs to Grow Up Before Your Company Does
-
The Phantom Stakeholder: Why You’re Building for Someone Who Doesn’t Exist
Or: How “Because Legal Said So” Became the Most Expensive Sentence in Software Engineering
-
The Pressure Is Coming From Inside the House
Or: Why Your Engineers Are Burning Out and Nobody’s Asking Them to
-
The Dashboard Delusion: Why Your Metrics Are Just Expensive Wallpaper
Or: Why Your Team Spent Two Sprints Building Beautiful Charts That Nobody Checks
-
The Design Handoff Is a Lie: Why Your Engineers and Designers Are Playing Telephone
Or: What Pixar’s Brain Trust Can Teach You About Product Development
-
The Design Review That Reviews Nothing
Or: Why Your Engineers Are Asking for Permission When They Should Be Writing Code
-
The 1:1 Is Broken (And You’re Both to Blame)
Or: Why the Most Important 30 Minutes of Your Week Has Become the Least Honest
-
The Config File That Runs Your Company: Why Your Most Important Code Isn’t Code
Or: How a Missing Comma Took Down an Entire Product Page
-
Your Roadmap Is a Lie You Tell Yourselves Every Quarter
Or: Why Architectural North Stars Matter More Than Your Q3 Technical Roadmap
-
The Slack Channel Graveyard: Why Your “Async Culture” Is Just Loneliness at Scale
Or: Why #architecture-decisions Has Been Dead Since That One “Thanks!” Seven Months Ago
-
The Onboarding Cliff: Why Your New Engineers Are Productive at Month Six (If They’re Still Here)
Or: What Restaurant Kitchens Mastered That Tech Companies Haven’t
-
The Migration That Never Ships: Why Your Team’s Best Intentions Are Paving the Road to Technical…
Or: Why 80% Complete Is the Most Dangerous Number in Engineering
-
The Helpful Senior Who Isn’t: Why Your Best Engineers Are Accidentally Breaking Your Team
Or: How Mentorship Became a Trap and Nobody Noticed Because It Looked So Good on Peer Reviews
-
The Greenfield Myth: Why Your New Service Is Already Legacy Code
Or: Why “This Time We’ll Do It Right” Is the Most Expensive Lie in Engineering
-
The Business Model Blindspot: Why Your Engineers Don’t Know How Your Company Makes Money
Or: We Shipped It, But We Can’t Explain Why It Matters
-
The Craftsman’s Dilemma: Why Your Best Engineers Are Your Biggest Overengineering Risk
Or: Why the Engineers Who Care Most About Quality Are Building Solutions Nobody Asked For
-
The Ownership Illusion: Why Your Platform Team Is Building Solutions to Problems That Don’t Exist
Or: How We Spent Three Years Maintaining a Band-Aid on a Bullet Wound
-
The Senior Engineer Plateau
Or Why Your Best People Are Quietly Rotting
-
The Hiring Bar Is a Lie You Tell Yourself
Or: Why Your Interview Process Selects for Interview Skills
-
On-Call Shouldn’t Feel Like Punishment
Or: Why Your Engineers Treat Production Alerts Like Car Alarms in a Parking Lot
-
The Documentation Graveyard
Or: Why Nobody Reads Your Confluence and What to Do About It
-
The Tragedy of Shared Code: Why Your Most Critical Infrastructure Is Already Dying
Or: Nobody Owns the Basement, and Now the Whole Building Is Sinking
-
The COVID Hangover Is Killing Your Engineering Velocity
Or: Why Walking Twenty Metres Beats Two Weeks of Slack Messages
-
The Org Chart Trap: Why Your Company Structure Is Silently Killing Velocity
Or: How to Stop Building Bureaucracy and Start Building Teams That Actually Ship
-
The Question That Changes Everything
Or: Why Asking Engineers “How Can We Do This Faster?” Is the Worst Question You Can Ask
-
The AI Coding Trap: Why 95% of Companies Are Measuring the Wrong Thing
Or: Your AI Can Write Code. So What?
-
The Feature Team Fallacy: Why Your “Agile” Teams Are Just Waterfall in Disguise
Or: How We Accidentally Recreated 1990s Software Development with Better Tooling
-
Recognition: The Leadership Skill Nobody Taught You
Or: Why Your Best Engineers Might Be One Missed “Thank You” Away from LinkedIn
-
I Don’t Care What You Build (And Neither Should You)
Or: Why Your Design Reviews Are Missing the Point Entirely
-
The Expensive Illusion of Intuition: Why Your Product Team Is Probably Wrong
Or: How a Slightly Misplaced Price Column Nearly Cost Us Millions
-
Centralization Is Contention: The Hidden Tax on Your Engineering Velocity
Or: Why Every Centralized Team Becomes a Bottleneck (And the Math to Prove It)
-
The 40-Minute Pipeline: Why Your Build System Is Making You Dumber
Or: How We Measured What Everyone Suspects But Nobody Wants to Talk About
-
The Regenerate Button: Why Your Snapshot Tests Are Lying to You
Or: The Most Dangerous Command in Your Test Suite
-
The Data Trap: Why Your Company Will Never Be “Data-Driven”
Or: How Developer Experience Became the Secret Weapon Nobody’s Talking About
-
Breaking Engineering Silos: The Uncomfortable Truth About Collaboration
Or: Why Your Teams Are Islands and What You’re Actually Going to Have to Do About It
-
Please Stop Asking AI to Count Your Tabs
Or: Why Your LLM Is the Most Expensive Linter in History
-
The Automation That Isn’t: Why Your CI Pipeline Is Just a Very Expensive Reminder App
Or: How We Built Machines to Tell Humans to Do the Work Machines Should Be Doing
-
“But, But… My Points!”: The Story Point Trap That’s Killing Your Engineering Culture
Or: Why Your Team Might Be Measuring Success While Missing the Point Entirely
-
The Taste Gap: Why Your Engineering Teams Keep Solving the Same Problems Differently
Or: Why Your ADRs Are Unread and Your Guilds Are Dead
-
Semantic Monitoring: The Question You’re Not Asking About Your Production Systems
Or: Why Your Dashboards Are Green and Your Business Is Bleeding
-
Code Entropy: The Silent Killer of Engineering Velocity
Or: Why Your Codebase Is Slowly Dying and Nobody’s Talking About It
-
The Art of Engineering Constraints
“Aerodynamics are for people who can’t build engines.” — Enzo Ferrari
-
Technical Debt: The Elephant in the Scrum Room
Or: Why Your Product Owner Shouldn’t Be the Only One Steering the Ship
-
Your Linting Rules: Are They the Police or a Teacher?
I. Introduction
-
The F5 Experience (Testing)
Part of the F5 Experience is also running tests. Can I open my IDE and “just run the tests” after cloning a project?
-
The F5 Experience (Speed)
Is a term I’ve been using for years; I originally learned it from a consultant I worked with at Readify years ago.
-
Push Groups: Encouraging Adoption of New Tools and Technologies
Another process I’ve been trialling I wanted to share: