Timeline for Can technical debt be detected by code analysis?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2022 at 12:15 | comment | added | Ewan | I don't see how your examples follow clearly from either the wiki or the Wikipedia definition, or even your own tbh. eg. "bad variable names" arguably detectable with software, arguably makes maintenance harder, arguably "impedes development". It fits only in the broadest sense and you even argue against it a bit when you talk about uniformity not always being good. A tool with a rule will always be looking to impose uniformity on your variable naming example | |
| May 28, 2022 at 8:39 | comment | added | JacquesB | @Even: Yes, it is a wiki created by Ward Cunningham who coined the term "technical debt". If you want a more clear definition you can go to Wikipedia: "technical debt [..] is the implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer." | |
| May 27, 2022 at 18:46 | comment | added | Ewan | erm seems like a mishmash of various quotes | |
| May 27, 2022 at 18:28 | comment | added | JacquesB | @Ewan: See for example here: wiki.c2.com/?TechnicalDebt | |
| May 26, 2022 at 18:12 | comment | added | Ewan | have you got any backup to show your definition of tech debt is correct? | |
| May 26, 2022 at 8:11 | history | answered | JacquesB | CC BY-SA 4.0 |