1
Technical Debt
Technical Debt is a metaphor for the consequences of cruft. You either have to accept a drag on further features (paying interest) or fix the software (paying the principal)
Martin Fowler
A website on building software effectively
- Popular posts
- 84
- Total points
- 17,806
- HN comments
- 10,168
- Rank
- #33 personal
Visit martinfowler.com → On Hacker News Jun 2009 – Oct 2026
Software Engineering 66Career & Management 20Tech Industry & Business 15AI & Machine Learning 13Society, Policy & Culture 10Systems & Performance 8
2
Technical, cognitive, and intent debt
three layers of system health, AI as cognitive system 3, what's expensive if agents make coding free, and the future of source code
3
Is High Quality Software Worth the Cost?
We usually perceive that it costs more to get higher quality, but software internal quality actually reduces costs.
4
ThoughtWorks has been sold to private equity
Thoughtworks is acquired by Apax Funds. The current management team will continue to run the company as before.
5
The Economic Benefit of Refactoring
Notes from my colleagues on AI-assisted software delivery
6
You Can't Buy Integration
The usual build-versus-buy rules for applications don't apply to integration
7
Products Over Projects
Projects are a popular way of organizing software efforts, but long-running product teams are often superior
8
Product vs. Engineering
Friction Between Product and Engineering; Lack of trust and collaboration slowing down product growth
9
TeamTopologies
A model that helps people design effective teams for software development.
10
Martin Fowler on Software Patents
a bliki entry for Software Patent
11
Martin Fowler: An Open Letter to Pearson about SOPA/PIPA
To: John Isley, Executive Vice President, Higher Education & CEO Pearson Technology Group
12
Cannot Measure Productivity
It is impossible to measure the effectiveness of tools and techniques in software development because we have no way of measuring our output, and thus our productivity.
13
The Lies that can Undermine Democracy
Recent events highlight our need to take serious measures to counter lies that are undermining democracies.
14
bliki: Bounded Context
Don't try to build a single, unified model for a large domain. Instead DDD advises us to divide such a domain into many bounded contexts with explicit relationships between them.
15
bliki: Anemic Domain Model
If you use an object-oriented domain model, and you don't put behavior in your objects, you're missing out on most of the benefits of that pattern.