2 ms·

I looked through your site, and was a bit confused. How does this help you monitor technical debt specifically? This seems like traditional engineering issue tr

• 1123581321 5y ago
  I wasn’t sure either. This page of the docs shows what you can track: https://www.hellocaribou.com/documentation/#types-of-migrations-supported https://www.hellocaribou.com/documentation/#types-of-migrati... Technical debt findable with those tools could be a less-than-ideal language choice, “fix this crap” comments, bad architecture identified by certain statements, etc. A traditional issue tracker would require identifying and marking those instances for refactor.
• attasimo 5y ago
  Thanks for your feedback! Caribou tracks files that match specific custom rules that you set. So you will need to set the rules to match the ‘tech debt’ in your codebase. Once you set these rules, Caribou will track the decrease/increase of this tech debt and who is contributing to this decrease/increase. For example, you are using a deprecated library in your codebase and you need migrate it to another library. The old library is considered tech debt. You can set a rule to monitor the usages of the old library in your codebase. As your team starts migrating from the old library to the new library, Caribou will detect these changes and will show you the progress in the dashboard together with information on who is contributing to this improvement. Does this make sense?