Haunted Graveyards in Consulting(datosh.github.io) |
Haunted Graveyards in Consulting(datosh.github.io) |
I've done consulting in esoteric products, so the content is accurate and a useful cautionary tale.
Imho, the skill gap is the original sin. If the team inheriting ownership is seriously underskilled, no amount of knowledge transfer is going to fix that -- so stick to whatever is dirt simple and most obvious in language du project.
If you can actually make an AI detector that works, do that and print money for yourself. Otherwise accept that all "AI detectors" have massive false positive rates, your intuition included.
If visitors like what they see on the page, they will up vote it. If they don't, they won't. That's how HN works.
Even at a high level though, it’s poorly reasoned. If quality code is not maintainable, what are your criteria for quality exactly? It’s basically an ad for consulting services targeted at people without strong critical reasoning skills.
While the solutions you list can help, it will not solve the haunted graveyard problem, just ask all of the companies with Cobol programs in production.
// Ugly hack. To fix later {inserts reasons and breadcrumbs here}
Beats naked magic numbers/logic any day of the week.
So probably it's been "fixed" and caused stuff to break since then.
If that's what technical debt ever amounted to, then the average software developer is stupid, because he doesn't know how to innovate and improve within the meta-system he's functioning in. It's not hard to restructure things when inefficiency becomes a problem. Just do it.
Instead of lionizing technical debt as some sort of boogeyman demon around the Internet forums water coolers.