A honest example of technical debt

Is this article.

You were supposed to write a consistent, well documented article on <random topic> or complete that project piece of code, write the best crafted unit tests, have the finest wiki documentation…

But life happens: COVID-19 hits you, anniversary in the family, a (new) personal project or just plain sloth. You end up with.. this.

The team/project ends up with a piece of not properly tested code that you push to source control (and pray), not well documented, not well explained to other teams.

While it addresses the core concept, it still remains not your best work expression and could should definitely be improved. But when?

Leave a Comment