⚡ Quick Summary
- A viral blog post argues that software engineering promotion structures systematically reward complexity addition over simplification, creating a compounding technical debt crisis across the industry.
- AI-assisted coding tools like GitHub Copilot are dramatically lowering the cost of writing new code, which — without incentive reform — risks accelerating complexity accumulation by an order of magnitude.
- Software complexity has direct security consequences: the Log4Shell vulnerability (affecting ~3 billion devices) and the XZ Utils backdoor both exploited the opacity that bloated codebases create.
- Smaller, simplicity-focused competitors like Linear are growing rapidly by explicitly positioning against the feature bloat of incumbents like Jira and Confluence.
- Organisations that redesign performance review frameworks to measure and reward complexity reduction — tracked through concrete metrics like cyclomatic complexity scores and dependency counts — are likely to outperform peers on reliability and security posture.
What Happened
A blog post published on March 3, 2026, at terriblesoftware.org under the provocative title Nobody Gets Promoted for Simplicity has ignited a significant conversation in software engineering and product management circles, accumulating 118 upvotes and 59 comments on Hacker News within its first news cycle. The piece — sharp, candid, and uncomfortably accurate — argues that the structural incentives embedded in most technology organisations actively punish engineers and product managers who pursue elegant, minimal solutions, while rewarding those who ship visible, feature-heavy complexity.
The argument is not merely philosophical. The author contends that performance review cycles, promotion rubrics, and project visibility metrics are all calibrated to recognise addition rather than subtraction. An engineer who refactors 10,000 lines of legacy code down to 2,000 — eliminating bugs, improving performance, and reducing maintenance overhead — is often invisible in quarterly reviews. Meanwhile, a colleague who ships a new dashboard feature, however redundant, has a tangible deliverable to point to during promotion conversations.
The post resonated particularly strongly with the Hacker News community, where senior engineers and engineering managers shared their own experiences of watching organisational complexity compound over years, driven not by user need but by internal career mechanics. Several commenters noted that this dynamic is especially acute in large enterprise software companies, where product surface area has ballooned to the point where no single engineer can hold the full system in their head — a phenomenon sometimes called cognitive overload architecture.
The timing is notable. The post arrives at a moment when the software industry is grappling with the consequences of a decade of rapid feature accumulation, accelerated further by the AI-assisted development boom of 2024 and 2025, which has made it cheaper and faster than ever to generate new code — regardless of whether that code should exist at all.
Background and Context
The tension between simplicity and complexity in software is as old as the discipline itself. Fred Brooks articulated the essential challenge in his 1975 landmark essay The Mythical Man-Month, distinguishing between essential complexity — the irreducible difficulty of the problem being solved — and accidental complexity, the unnecessary burden introduced by poor design choices, organisational friction, and tooling decisions. Forty years later, the ratio of accidental to essential complexity in enterprise software has arguably never been higher.
The roots of the current crisis trace back to the SaaS explosion of the early 2010s, when cloud-delivered software unlocked continuous deployment and made it trivially easy to ship features without the forcing function of a boxed-software release cycle. Products like Salesforce, which launched its first cloud CRM in 2000, had by 2015 accumulated so many features across Sales Cloud, Service Cloud, Marketing Cloud, and Commerce Cloud that Salesforce itself began offering dedicated certification programmes just to navigate its own product ecosystem. Microsoft 365 — which consolidated Office, Teams, SharePoint, OneDrive, Exchange, and dozens of auxiliary services under a single subscription umbrella — faced similar criticisms, with enterprise IT administrators routinely reporting that the sheer scope of available configuration options created decision paralysis rather than empowerment.
The promotion incentive problem specifically gained academic attention around 2018 and 2019, when researchers studying engineering organisations at large technology firms began documenting what they termed feature factory culture — a term popularised by product consultant John Cutler. In a feature factory, teams are measured by output (features shipped per quarter) rather than outcome (user problems solved), creating a perverse loop where complexity compounds indefinitely. Google's internal research, partially surfaced through Project Aristotle and subsequent engineering effectiveness studies, noted that teams spending more than 30 percent of their time on maintenance and simplification work consistently outperformed peers on long-term reliability metrics — yet those same teams received lower performance ratings on average, because their work was harder to quantify in standard review frameworks.
The arrival of large language model-assisted coding tools — GitHub Copilot launching in general availability in June 2022, followed by Copilot Workspace in 2024 and a wave of competitors including Cursor, Codeium, and Amazon CodeWhisperer — dramatically lowered the marginal cost of writing new code. This is the crucial accelerant: when generating a new function costs minutes rather than hours, the organisational temptation to add rather than refine becomes nearly irresistible.
Why This Matters
For enterprise IT professionals and business technology leaders, the implications of this incentive misalignment are deeply practical, not merely theoretical. Software complexity is not a neutral condition — it has direct, measurable costs that accumulate on balance sheets, in security vulnerability registers, and in employee productivity statistics.
Consider the maintenance burden alone. According to a 2024 report by the Consortium for Information and Software Quality (CISQ), poor software quality cost US organisations approximately $2.41 trillion in 2022, with technical debt — the accumulated cost of complexity shortcuts — representing the single largest component. Every unnecessary abstraction layer, every redundant API endpoint, every feature that serves 0.3 percent of users but must be tested, documented, and secured, contributes to this figure.
The security implications are particularly severe. The attack surface of a software system scales roughly proportionally with its complexity. The Log4Shell vulnerability of December 2021, which affected an estimated 3 billion devices globally, was a direct consequence of a ubiquitous logging library that had accumulated functionality far beyond its original scope. The 2024 XZ Utils backdoor — embedded in a widely-used compression library — exploited the opacity that complexity creates, hiding malicious code in a codebase that had grown too large for any single maintainer to audit comprehensively. When organisations run bloated, over-featured enterprise software stacks, each additional component is a potential attack vector.
For businesses running Microsoft 365 environments specifically, this complexity problem manifests in concrete ways: SharePoint deployments that have accumulated years of redundant site collections, Teams environments cluttered with channels and apps that nobody uses, and Power Platform automations built by well-intentioned citizen developers that now nobody understands or dares to modify. IT departments managing these environments spend significant portions of their operational budgets on complexity remediation that could have been avoided with better incentive structures upstream. Organisations looking to right-size their software investments — including sourcing an affordable Microsoft Office licence rather than defaulting to the most feature-laden tier — often find that simplification at the licensing level mirrors the cultural simplification the industry desperately needs.
Industry Impact and Competitive Landscape
The complexity problem described in this viral post cuts across every major enterprise software vendor, but its effects are not evenly distributed — and the competitive dynamics are fascinating.
Microsoft is perhaps the most instructive case study. The company's product portfolio has expanded dramatically under Satya Nadella's leadership since 2014, growing from a Windows-and-Office company into a sprawling cloud, AI, gaming, and productivity conglomerate. Microsoft 365 now encompasses over 25 distinct applications and services, and the Azure platform lists more than 200 individual products. Microsoft's engineering culture has historically rewarded this kind of expansion — the company's stack-ranking era under Steve Ballmer was notorious for incentivising internal competition over collaboration, and while Nadella's cultural reset improved collaboration, the fundamental promotion mechanics that reward visible feature work remain largely intact across the industry.
Google faces an identical structural challenge. The company's graveyard of discontinued products — Google Reader, Google+, Stadia, Allo, Hangouts, and dozens more — is a direct artefact of teams building new things for promotion credit and then abandoning them when the next shiny project beckoned. Google Workspace, competing directly with Microsoft 365, has itself accumulated significant feature bloat, with Docs, Sheets, Slides, Sites, Forms, Jamboard, AppSheet, and multiple chat platforms coexisting in various states of integration and redundancy.
Apple, by contrast, has historically maintained a more disciplined approach to feature addition — Steve Jobs's famous mantra that deciding what not to build is as important as deciding what to build remains culturally embedded at Cupertino, at least at the product level. This philosophical difference partly explains why Apple's consumer software products consistently score higher on usability benchmarks despite lower feature counts.
Salesforce, now the world's largest CRM vendor with approximately 23 percent market share as of 2025, has responded to its own complexity problem by acquiring Slack in 2021 for $27.7 billion — a move that, critics argue, added integration complexity rather than reducing it. The company's Einstein AI layer, now deeply embedded across its product suite, risks following the same trajectory: AI features added for visibility rather than utility.
Smaller, focused competitors are beginning to exploit this dynamic. Linear, a project management tool that has explicitly positioned itself against Jira's sprawl, grew its enterprise customer base by over 200 percent between 2023 and 2025 by offering a deliberately constrained feature set. Notion, despite its own complexity creep, initially won significant market share from Confluence by offering a simpler mental model. The market is signalling that users value simplicity — the incentive structures inside the companies building these tools simply haven't caught up.
Expert Perspective
From a strategic standpoint, the blog post's viral traction on Hacker News is itself data worth analysing. The 59-comment thread attracted contributions from engineering managers at major technology firms, independent consultants, and CTOs of mid-market companies — all corroborating the same fundamental observation. When a piece of technical writing achieves this level of resonance, it typically signals that the industry is approaching an inflection point where the pain of the status quo has become acute enough to generate genuine demand for change.
The most significant risk the post identifies — and the one that industry analysts should watch most carefully — is the interaction between AI-assisted development and complexity incentives. If GitHub Copilot and its successors make it ten times faster to write new code, but organisational incentives still reward code written over code deleted, the net effect could be a ten-times acceleration of technical debt accumulation. This is not a hypothetical: engineering teams that adopted Copilot aggressively in 2023 and 2024 are already reporting that their codebases have grown substantially in line count without commensurate growth in functionality.
The opportunity, conversely, is for organisations that deliberately restructure their engineering performance frameworks to value simplification. Companies that build promotion rubrics rewarding measurable complexity reduction — lower cyclomatic complexity scores, reduced dependency counts, improved mean time to recovery — will likely outperform peers on reliability, security posture, and long-term development velocity. This is not idealism; it is competitive strategy. Running leaner, more coherent software on a properly licensed and maintained platform — including a properly activated genuine Windows 11 key as the foundation of a clean, auditable endpoint environment — is increasingly a security and operational imperative.
What This Means for Businesses
For business decision-makers, the conversation this post has sparked should prompt a concrete internal audit rather than a passive read. The question to ask your engineering and product leadership is direct: what percentage of your current sprint capacity is allocated to simplification, refactoring, and technical debt reduction? If the honest answer is below 20 percent, your organisation is likely accumulating complexity faster than it is managing it — and the downstream costs will materialise in security incidents, slow delivery cycles, and engineer attrition.
IT departments should advocate for changes to performance review frameworks that explicitly recognise and reward simplification work. This means creating measurable proxies: lines of code deleted per quarter, number of deprecated features successfully removed, reduction in mean time to onboard a new engineer. These metrics exist; most organisations simply don't track them.
On the vendor side, enterprise procurement teams should scrutinise software renewals with fresh eyes. Are you paying for feature tiers your organisation genuinely uses? The enterprise software market is full of organisations paying for platinum-tier complexity when a gold-tier product — or even a simpler competitor — would serve them better. Exploring enterprise productivity software options through legitimate resellers can surface meaningful savings while right-sizing your actual capability requirements. The simplicity principle applies to procurement as much as to engineering.
Organisations should also consider whether their internal tooling — the Confluence wikis, the Jira boards, the SharePoint intranets — has itself become a complexity burden. Periodic simplification of internal tooling is as valuable as simplification of customer-facing products.
Key Takeaways
- Incentive misalignment is structural: Most engineering organisations reward visible feature addition over invisible but valuable simplification, creating a systematic bias toward complexity accumulation.
- The AI coding boom amplifies the risk: Tools like GitHub Copilot and Cursor lower the cost of writing new code dramatically, which — without countervailing incentives — will accelerate technical debt accumulation across the industry.
- Security exposure scales with complexity: Every unnecessary feature, dependency, and abstraction layer represents a potential attack surface; the Log4Shell and XZ Utils incidents demonstrate this at catastrophic scale.
- Smaller, focused competitors are exploiting this: Products like Linear and Basecamp are winning enterprise customers specifically by offering disciplined simplicity against the bloat of legacy incumbents.
- Promotion rubrics need redesign: Organisations that explicitly measure and reward complexity reduction in performance frameworks will outperform peers on reliability, security, and long-term velocity.
- Procurement reflects engineering culture: Right-sizing software licensing — choosing appropriate tiers rather than defaulting to maximum feature sets — is the procurement equivalent of the simplicity principle.
- The market is signalling readiness for change: The viral resonance of this post, combined with the growth of simplicity-focused competitors, suggests enterprise buyers are increasingly willing to reward restraint.
Looking Ahead
Several developments in the next 12 to 18 months will determine whether this conversation translates into structural change or remains a recurring lament. The most important variable is how major engineering organisations respond to the AI-assisted development productivity paradox — if internal complexity metrics begin deteriorating visibly in 2026 as AI coding tools become ubiquitous, expect a wave of engineering leadership initiatives focused on codebase health and technical debt reduction.
Watch for whether any major technology companies — Microsoft, Google, Salesforce, or a prominent SaaS unicorn — publicly revises its engineering promotion framework to explicitly include simplification metrics. A high-profile announcement of this kind would signal genuine cultural shift rather than rhetorical acknowledgment.
The broader AI product landscape also bears watching. As Microsoft Copilot, Google Gemini, and Salesforce Einstein deepen their integration into enterprise workflows through 2026, the question of whether AI assistance is used to help users navigate complexity or to genuinely reduce it will become a meaningful competitive differentiator. The vendors that choose the latter path may find themselves with a durable advantage that no feature checklist can easily replicate.
Frequently Asked Questions
Why do software organisations reward complexity over simplicity?
Most engineering performance review frameworks measure visible, attributable output — features shipped, products launched, APIs built. Simplification work, by contrast, is largely invisible: deleting code or consolidating redundant systems reduces the codebase but produces nothing a manager can point to in a quarterly review. This creates a structural bias where engineers rationally choose to add rather than subtract, even when subtraction would deliver greater value. Changing this requires explicit redesign of promotion rubrics to include measurable simplification metrics, which few organisations have undertaken systematically.
How does AI-assisted coding make the complexity problem worse?
Tools like GitHub Copilot, Cursor, and Amazon CodeWhisperer lower the marginal cost of writing new code dramatically — tasks that once took hours now take minutes. Without countervailing incentives to delete and simplify, this productivity gain translates directly into faster complexity accumulation. Engineering teams that adopted these tools aggressively in 2023–2024 are already reporting significant codebase growth without proportionate functional improvement. The technology amplifies existing incentive problems rather than solving them.
What are the security implications of software complexity?
Attack surface scales with complexity. Every additional feature, dependency, abstraction layer, and integration point is a potential vulnerability. The Log4Shell incident of December 2021 — which affected an estimated 3 billion devices — exploited a logging library that had accumulated functionality far beyond its original scope. The 2024 XZ Utils backdoor hid malicious code in a codebase too large for any single maintainer to audit comprehensively. Enterprise organisations running bloated software stacks face proportionally higher breach risk, making complexity reduction a security imperative, not just an engineering preference.
What practical steps can businesses take to address complexity in their software environments?
Businesses should start with an honest audit of sprint capacity allocation — if less than 20 percent of engineering time is dedicated to simplification and technical debt reduction, the organisation is likely accumulating complexity faster than it manages it. IT departments should advocate for performance review changes that explicitly reward measurable simplification. On the procurement side, organisations should scrutinise whether they are paying for feature tiers they actually use, and explore right-sizing through legitimate resellers. Internally, periodic simplification of tools like SharePoint intranets, Jira boards, and Confluence wikis delivers operational value comparable to product-side simplification efforts.