Hacker News new | past | comments | ask | show | jobs | submit login

I really like this tool (text-based, yes!), thank you for creating this! I'm working on creating estimates at work and it is a real struggle. Creating estimates with a range and probability is awesome because it reflects the uncertainty inherent in any estimate.

It would be nice if the system showed its work somehow. In addition to giving me comfort as the estimator, it's nice to show the person on the receiving side the my inputs and help them understand process being applied. I looked for some docs on this, but I couldn't find anything. At the very least, it would make a great blog post!

Another bit of feedback while I'm here. I tried using {1-2d} for days and {budget 10d} for budget. It seemed to work for estimates, but not for the budget. Looked for docs on the syntax, but I couldn't find it and it all the examples in the quickstart use hours.

P.S. I'd love to talk to you about how I'd like to use this if you're looking for more feedback / collaboration. This has legs!




Thanks for the kind words, I'm very glad you like this!

It would be neat to be able to "show work", but I'm not entirely sure how to achieve that in a way that adds enlightenment instead of confusion in the main workflow. A blog post about how it works under the hood would definitely be a good thing, though, you're absolutely right.

The "d" suffix in estimates exist only to keep older plans valid -- it meant "8 hours", but since not everyone agrees that's the length of a day, I removed it from the documentation pretty early -- before budget and spent tags even existed, so they never had it at all. We all pretty much agree on what an hour is, so that's the one true unit for now, anyhow.

I'd love to chat more -- hit me at info@doomcheck.com and I'll respond directly!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: