📎 Webclip
What types of features typically lead to lots of tech debt?
The thread focuses on feature requests that create technical debt when they force rushed patches, special-case handling, or extra complexity around the existing system. Comments also single out work that is tightly tied to specific customers, vendors, products, or internal organizational requirements, because those changes are harder to generalize and maintain.
Reading notes#
- Features unlike anything already implemented often require new infrastructure and time that the team may not have.
- Features that are almost the same as existing ones, but with important differences, can lead to duplicated code or hacks.
- One-off requests for a special check or a quick exception often become permanent code.
- Requests driven by urgency, small exceptions, or “we will worry about it later” tend to hide complexity.
- Features tied to specific customers, vendors, products, events, or hardware can break when the scope expands.
- Organizational requirements that are outside the app’s normal usage can become a lasting burden.
- A/B testing is described as useful when done well, but it adds complexity and coordination that can create debt.
- “Example” versions and prototypes can turn into debt when they become the final product.
