No. Especially if you work in iterations, sometimes things get left behind because of other priorities. I work at a company that prefers shipping software out quickly vs quality, there's plenty of tech debt given the time constraints.
-
-
-
Sounds like the debt is due to design and planning failures, you wouldn’t have time constraints if a solid plan was in place from the start imho
- Još 5 drugih odgovora
Novi razgovor -
-
-
There are (also) legit reasons to use technical debt. Ex: you don't know if the product is what people want. In that case, cut corners, get it out there, pay back the debt only if people like it.
-
If your users don’t like what you’re putting out, couldn’t it be due to design? Choosing to cut corners is after the fact
- Još 2 druga odgovora
Novi razgovor -
-
-
If you consider unwillingness to spend poor design.

-
I don’t think I was clear enough in OP. I do not mean TD as it refers to depreciating assets SW/HW more in the program/or programming perspective such as “workarounds” , “optimizations”, “improvements”. For assets like windows xp all you can do is spend by no fault of your own
Kraj razgovora
Novi razgovor -
-
-
No, it’s also caused by a lack of maintenance over time.
-
Could better design eliminate maintenance?
- Još 1 odgovor
Novi razgovor -
-
-
No, take on tech debt now and ship today knowing paying down that debt in the future will come with interest, YMMV
-
Why would you have to take on technical debt if design had considered the concern to be dealt with?
- Još 2 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

丨Proud Dad丨he/him丨ex: 