Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
Is there any terminology for a problem that is caused by a previous wrong decision?
For example you build your own framework, with a flawed MVC design. This in turn leads to weird situations when routing requests. A person then asks how to solve the latter problem, while the actual problem is the wrong design of the framework.
I've tried searching several descriptions but as I'm looking for the word, it's hard to find anything relevant.
It's not one of these Anti-patterns
I think this question has no answer because problems aren't categorized by what they're caused by, but by what kind of problem they are. A security vulnerability can be caused by a design flaw or an implementation error, regardless: it's a security vulnerability.
I think the term "technical debt" is used often to mean precisely that.
Wikipedia's definition seems to describe what you express in your question:
Technical debt (also known as design debt or code debt) is a neologistic metaphor referring to the eventual consequences of poor system design, software architecture or software development within a codebase. The debt can be thought of as work that needs to be done before a particular job can be considered complete or proper. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on. Unaddressed technical debt increases software entropy.
The term does not refer though to any given problem but to the sum af all of them.
