jhbrown

5 ms·

1. 1.▲
   by jhbrown 1y ago

   Slides author here. Thanks for flagging that. I'll fix it before I give the talk again, most likely in 2044 :)
2. 2.▲
   by jhbrown 4y ago

   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
3. 3.▲
   by jhbrown 4y ago

   One of the recurring problems my early users have had is the need to move data back and forth between DoomCheck and their organizational system, most commonly Jira. So you're right about that being a problem. Integrations aren't
4. 4.▲
   by jhbrown 4y ago

   You're exactly right! Under the hood, DoomCheck actually uses a log-logistic distribution -- https://en.wikipedia.org/wiki/Log-logistic_distribution -- which it fits using the range endpoints as 10% and 75% respe
5. 5.▲
   by jhbrown 4y ago

   At a prior startup of mine, we needed to set prices for a series of 12-month, fixed-price, fixed-deliverable contracts. Since most tools typically used for planning software projects are terribly bad at helping you make good estimates, we
6. 6.▲
   Show HN: DoomCheck: A tool for probabilistically estimating project size(doomcheck.com)

   27 points by jhbrown 4y ago|7 comments
7. 7.▲
   Software developer perceptions about software project failure: a case study(doomedprojects.com)

   2 points by jhbrown 4y ago|0 comments
8. 8.▲
   Story: “It would be career limiting..."(doomedprojects.com)

   457 points by jhbrown 4y ago|324 comments