All software has technical debt.

"Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite... The danger occurs when the debt is not repaid. Every minute spent on not-quite-right code counts as interest on that debt. Entire engineering organizations can be brought to a stand-still under the debt load of an unconsolidated implementation, object-oriented or otherwise."[8]

— Ward Cunningham, 1992

How are you addressing it?

When you add a github repo, imdone will scan your source code for TODO, FIXME, HACK, etc. comments and open github issues for each one labeled with it's comment tag (e.g. TODO)

Imdone creates a webhook that runs on push events to your github repo and looks for new, updated and deleted TODO comments.

  • When a TODO comment is deleted, imdone will close it's corresponding issue.
  • Add labels to issues with +label-name
  • Add comments by adding a TODO with the same gh:[issue number]

Avoid context switching by adding TODO comments to your tracker or backlog when you push.


Are your developers telling you that problems with the code are making their estimates higher?

Are you noticing a slow down in implementing new features?

Get your technical debt into the product backlog

Integrate with anything!

Right now we're pretty focussed on making our github and waffle integration rock solid, but we've got webhooks too! They're still in beta, but after you setup your project and feel the urge to tinker, you might want to check these out...


Check out these TODO numbers in open source...

~2750 TODOs

TODO comments

[tuh-doo]

A code comment that begins with TODO, FIXME, HACK, XXX etc. We know most of them and if we don't you can add them yourself!

© 2017 Innobuilt Software LLC. All rights reserved. | Privacy Policy | Contact Us