EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·Aug 13·5 min read
Let's not call it "tech debt," it's just "mess"
TL;DR
The term 'technical debt' often misrepresents issues in software development, which are better described as 'mess.' This distinction helps clarify the nature of problems and their origins.
✦ Why It Matters
Reframe discussions about software quality by using 'mess' instead of 'technical debt' to clarify issues.
Key Takeaways
- Use 'mess' to describe software issues instead of 'technical debt'.
- Recognize that not all messy code is due to poor decisions.
- Acknowledge the unpredictability of costs in technical decisions.
- Encourage ongoing maintenance and organization in software projects.
Full Summary
Many software developers use the term 'technical debt' to describe various issues, but this metaphor can be misleading. While some instances of technical debt involve conscious trade-offs for future benefits, much of what is labeled as debt is simply poor quality work or personal preferences.
For example, slow tests or poorly organized code do not constitute debt but rather a lack of skill or aesthetic choice. The author argues that the unpredictability of costs associated with technical decisions makes the debt metaphor inappropriate.
Instead, viewing software projects as 'mess' emphasizes the ongoing need for maintenance and organization, akin to managing a workspace. This perspective encourages a more accurate understanding of the challenges faced in software development.