How to handle minor bugs that are design flaws?

Question

I am working on a project where I have several related errors that are pretty minor in terms of loss of functionality. These are mostly minor but annoying aesthetic problems, and ultimately, based on the loss of functionality, it should be fixed, but not as a top priority. However, these errors are caused by a fundamental, baked design flaw that will be nightmare to fix.

When you encounter errors that are functionally insignificant, but caused by sophisticated design flaws, it is usually best to consider them as demonstrators, so as not to draw yourself further into the corner or to consider them as low-priority errors, continue the functionally more important material and hope you find out later the way to them when the project becomes more mature, and corrections for minor errors are given priority?

Answer 1

, , , , , .

, , , , , , , , , , , , , -.

Answer 2

, -, , , , . , . , , , , .

Answer 3

. , , , x y . , . , , . , , . , , .

In an ideal world, we will have an infinite amount of time to constantly redesign a design based on changing requirements. In the real world, we have to weigh the cost of a design change versus the cost of continuing with a current design. You can start by quantifying the amount of time you spent fixing bugs in the current project and compare it with the time you are evaluating to reverse engineer this component.