Engineering Excellence: Driving High-Quality, Sustainable Software Development
Engineering excellence is the foundation of high-quality, maintainable, and scalable software systems. It is about fostering a culture that values continuous improvement, technical rigor, and long-term sustainability in software development. This category is dedicated to discussions on how organisations can elevate their engineering standards to deliver predictable, resilient, and valuable software.
Why Engineering Excellence Matters
- Ensures Quality – Drives consistency, reliability, and maintainability in software.
- Reduces Risk – Identifies and mitigates issues before they become costly.
- Enhances Scalability – Supports long-term growth and adaptability.
- Improves Efficiency – Streamlines development and delivery processes.
- Strengthens Collaboration – Aligns teams on shared technical goals and standards.
Core Principles of Engineering Excellence
- Software Craftsmanship - Engineering excellence is grounded in a deep understanding of design, architecture, and maintainability. It prioritises clarity, simplicity, and adaptability, ensuring that software remains robust over time.
- Modern Software Engineering Practices - A commitment to continuous validation, automation, and integration enables teams to build and evolve software with confidence. These practices ensure that software remains reliable, scalable, and secure, while allowing teams to respond quickly to change.
- Technical Debt Management - Engineering excellence requires a proactive approach to code health and system maintainability. It involves regular assessment, improvement, and simplification to prevent long-term inefficiencies and ensure that systems remain adaptable.
- Metrics & Observability - Effective engineering is driven by measurable outcomes and transparency. By establishing clear metrics and monitoring, teams gain insights into performance, stability, and efficiency, enabling data-driven improvements.
- Security & Compliance - A secure and compliant system is fundamental to engineering integrity. Engineering excellence ensures that security is embedded into development processes, reducing vulnerabilities and aligning with regulatory and organisational standards.
- Scalable & Resilient Architecture - Scalability and resilience are essential to long-term software success. Engineering excellence ensures that systems are designed to handle change, growth, and unexpected conditions, enabling sustainable evolution.
The strongest work on Engineering Excellence — ranked by substance, not recency. How this is ranked
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Why Topic Branches Drive High-Quality Delivery
Explains how short-lived topic branches in source control improve software quality, enable modularity, speed up integration, and support …
Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams
Struggling with inconsistent delivery? Discover why a shared definition of done is key to predictable, high-quality results your teams, and …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and …
Should You Use One Project to Rule Them All in Azure DevOps?
Explores when to use a single Azure DevOps project versus multiple projects, detailing impacts on flow, visibility, governance, and team …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams
Struggling with inconsistent delivery? Discover why a shared definition of done is key to predictable, high-quality results your teams, and …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward
Struggling with technical debt? Discover practical ways to tackle legacy systems, boost team morale, and deliver value, without grinding to …
Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems
Ditch the Big Bang rewrite. Discover why sustainable, in-place change drives true engineering excellence and lasting transformation in your …
Why Azure DevOps Wins for Governance, Security, and Scale, Right Out of the Box
Unlock seamless governance, security, and scale with Azure DevOps, integrated tooling that lets you deliver value, not just manage …
Stop Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics
Stop guessing, start making data-driven decisions in Azure DevOps. Discover tools, tips, and insights to make your work visible and your …
Stop Testing Quality In: How Shifting Left Builds Better Software, Faster
Stop testing quality in, start building it in. Learn how shifting left, automation, and fast feedback loops drive engineering excellence in …
Still Deploying Manually? Why Automation Is the Bare Minimum for Modern Engineering (and Your Business Survival)
Still deploying manually? Discover why automation isn’t optional, protect your business, avoid disaster, and deliver value with modern …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …
Building a Resilient Token Server: Engineering for Flow, Fault Tolerance, and Speed
Explains how to engineer a robust, fault-tolerant token counting server using FastAPI and PowerShell, covering error handling, retries, …
Convert Legacy Projects and ASP.NET MVC Apps to SDK-Style with Confidence
Learn how to upgrade legacy .NET and ASP.NET MVC projects to SDK-style for easier builds, modern tooling, and future readiness, including …
Detecting Agile BS
277 resources, newest first
Stop Flying Blind: Why Telemetry Belongs in Your Definition of Done
Stop flying blind after release, learn why telemetry is vital to your Definition of Done and how real feedback drives better software, …
Resilience is Part of the Product, Not an Afterthought
Resilience must be designed into products from the start, not added later. Build systems to detect, contain, and recover from failures, …
Stop Firefighting Bugs: Why Shifting Left Saves Time, Money, and Your Reputation
Stop firefighting late-stage bugs, discover how shifting left saves time, money, and reputation by building quality in from the start. Learn …
DevOps: The Practical Path to Modernising Legacy Systems Without Starting Over
Unlock legacy system agility, discover how DevOps transforms slow, brittle tech into fast, scalable, and change-ready platforms without …
Evolving Engineering Practices to Improve Sprint Workflow in Scrum
Learn how evolving engineering practices like Feature Flags, TDD, and refactoring enable smoother Sprint workflows and reduce technical debt …
Convert Legacy Projects and ASP.NET MVC Apps to SDK-Style with Confidence
Learn how to upgrade legacy .NET and ASP.NET MVC projects to SDK-style for easier builds, modern tooling, and future readiness, including …
Stop Hoping for Quality: Why Automated Pipelines Are the Only Way to Deliver with Confidence
Stop relying on memory for quality. Discover why automated pipelines beat manual checks, and how embedding quality gates ensures trust, …
How to Build for Business Resilience and Continuity
Learn key strategies for building business resilience and continuity, including observability, system decoupling, routine deployments, team …
How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward
Struggling with technical debt? Discover practical ways to tackle legacy systems, boost team morale, and deliver value, without grinding to …
Scrum doesn’t stop you from optimising flow
Explains how Scrum supports continuous flow and agility by prioritising Sprint Goals, Done increments, CI/CD practices, and outcomes over …
Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results
Stop paying the hidden costs of weak delivery. Discover how a strong, shared definition of done builds trust, quality, and real agility in …
When Heathrow went down, they blamed the power supplier
Heathrow’s outage was caused by an over-sensitive disaster recovery system, not a power loss, highlighting the risks of untested resilience …
Everyone has a disaster recovery plan, on paper
Most disaster recovery plans fail in practice due to overlooked dependencies and lack of real-world testing, leaving organisations …
Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams
Struggling with inconsistent delivery? Discover why a shared definition of done is key to predictable, high-quality results your teams, and …
Fragile by Design: The Cost of Pretending to Be Resilient
Explores how poor engineering, shallow product thinking, and organisational denial lead to fragile systems, stressing that true resilience …
Modernising Legacy Systems: How to Tackle Security Risks Without Breaking Your Business
Struggling with legacy systems? Discover how to modernise securely, reduce risk, and build resilience, without trading old problems for new …
Building a Resilient Token Server: Engineering for Flow, Fault Tolerance, and Speed
Explains how to engineer a robust, fault-tolerant token counting server using FastAPI and PowerShell, covering error handling, retries, …
Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery
Discover why “done” means live in production, not just code complete. Learn to deliver real value, close feedback loops, and drive outcomes …
Technical debt cripples business agility and slows engineers down
Technical debt limits business agility, slows engineering, and hinders innovation. Managing it with automation and transparency is key to …
I’ll never understand teams that manage bugs instead of fixing them
Highlights the importance of promptly fixing software bugs instead of managing backlogs, arguing that unresolved defects harm product …
let-us do the maths
Explains how slow product release cycles delay feature delivery, risk losing relevance, and create competitive disadvantages, highlighting …
Unlocking Legacy Systems: How to Embrace Automation and Drive Innovation
Learn how to automate legacy systems by shifting organisational mindset, adopting DevOps practices, and making incremental improvements to …
Understand the true risk of technical debt in your business
Technical debt poses significant business risks, reducing agility, slowing innovation, and causing lost opportunities. Addressing it is …
Microsoft shift from 2-year cycles to 3-week Sprints caused team anxiety
Microsoft’s switch to 3-week Sprints increased team anxiety due to greater transparency, exposing inefficiencies but enabling faster, more …
Would your CFO approve misrepresenting corporate assets?
Ignoring technical debt misrepresents software asset value, risking financial loss and operational issues. Properly account for technical …
There no such thing as "good" technical debt
Technical debt always harms productivity and system stability. Ignoring it leads to inefficiency and risk, making it essential to address …
Navigating the Legacy System Dilemma: Balancing Stability and Innovation for Modernisation Success
Learn how to modernise legacy systems by balancing stability and innovation, managing technical debt, and adopting gradual, sustainable …
We don’t have time for automation, but manual testing slows releases and quality
Manual testing limits release speed and quality, while automation enables faster, more reliable software delivery by reducing regressions …
If every release feels high-risk, you lack a true Definition of Done
Releases feel risky when teams lack a clear Definition of Done. Learn how a strong DoD ensures stress-free, reliable software delivery with …
A changing Definition of Done undermines quality and predictability in teams
Frequent changes to the Definition of Done reduce team quality and predictability. Consistent, enforced standards are key to reliable …