home.social

#estimating — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #estimating, aggregated by home.social.

fetched live
  1. Spotted in my Calishat Snaps: a number-based daily guessing game called Estimania. From the Hacker News Announcement: “Estimania is a daily game where you get 5 numerical questions and are scored based on how close your guesses are to the actual number. There’s also a leaderboard and groups, so you can compare your judgment with other players and friends.”

    https://rbfirehose.com/2026/07/10/daily-estimate-guessing-game-estimania/
  2. Spotted in my Calishat Snaps: a number-based daily guessing game called Estimania. From the Hacker News Announcement: “Estimania is a daily game where you get 5 numerical questions and are scored based on how close your guesses are to the actual number. There’s also a leaderboard and groups, so you can compare your judgment with other players and friends.”

    https://rbfirehose.com/2026/07/10/daily-estimate-guessing-game-estimania/
  3. 4/

    I've been thinking about #uncertainty from risk POV, & Doug Hubbard's concepts of calibrated estimators. My team does weekly calibrations for #estimating uncertainty. Listening to Choi-Greene talk about AI's certainty - confidently wrong, sometimes - I couldn't help but think that having calibrated, specific uncertainty on events, plans, projects, #technology would become MORE valuable in the future.

    @bsidesseattle #BSidesSeattle #BSidesSEA #2026 #cybersecurity #infosec #cyber #security

  4. 4/

    I've been thinking about #uncertainty from risk POV, & Doug Hubbard's concepts of calibrated estimators. My team does weekly calibrations for #estimating uncertainty. Listening to Choi-Greene talk about AI's certainty - confidently wrong, sometimes - I couldn't help but think that having calibrated, specific uncertainty on events, plans, projects, #technology would become MORE valuable in the future.

    @bsidesseattle #BSidesSeattle #BSidesSEA #2026 #cybersecurity #infosec #cyber #security

  5. In carpentry you measure twice and cut once. In software development you never measure and make cuts until you run out of time.

    — Adam Morse

    #estimating #planning #programming

  6. In carpentry you measure twice and cut once. In software development you never measure and make cuts until you run out of time.

    — Adam Morse

    #estimating #planning #programming

  7. The sooner you start to code, the longer the program will take.

    — Roy Carlson

    #estimating #programming

  8. The sooner you start to code, the longer the program will take.

    — Roy Carlson

    #estimating #programming

  9. Measuring programming progress by lines of code is like measuring aircraft building progress by weight.

    — Bill Gates

    #estimating

  10. Measuring programming progress by lines of code is like measuring aircraft building progress by weight.

    — Bill Gates

    #estimating

  11. Calvin Liang: The Fed says this is a cube of $1M. They’re off by half a million.. “I first tried counting the stacks right there in the room. The cube was tall, so I had to step back to see the whole thing, squinting at the stacks, trying to follow each row. I lost track almost immediately. Also, people were starting to look at me funny. Apparently, staring intensely at a pile of cash while […]

    https://rbfirehose.com/2025/07/14/calvin-liang-the-fed-says-this-is-a-cube-of-1m-theyre-off-by-half-a-million/

  12. Measuring programming progress by lines of code is like measuring aircraft building progress by weight.

    — Bill Gates

    #estimating

  13. Measuring programming progress by lines of code is like measuring aircraft building progress by weight.

    — Bill Gates

    #estimating

  14. The sooner you start to code, the longer the program will take.

    — Roy Carlson

    #estimating #programming

  15. The sooner you start to code, the longer the program will take.

    — Roy Carlson

    #estimating #programming

  16. The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time.

    — Tom Cargill

    #estimating

  17. The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time.

    — Tom Cargill

    #estimating

  18. Estimate always goes wrong. That too in one way.

    — Sumit Agrawal

    #estimating

  19. Estimate always goes wrong. That too in one way.

    — Sumit Agrawal

    #estimating

  20. Measuring programming progress by lines of code is like measuring aircraft building progress by weight.

    — Bill Gates

    #estimating

  21. Measuring programming progress by lines of code is like measuring aircraft building progress by weight.

    — Bill Gates

    #estimating

  22. The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time.

    — Tom Cargill

    #estimating

  23. The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time.

    — Tom Cargill

    #estimating

  24. The first step of any project is to grossly underestimate its complexity and difficulty.

    — Nicoll Hunt

    #estimating #management #planning

  25. The first step of any project is to grossly underestimate its complexity and difficulty.

    — Nicoll Hunt

    #estimating #management #planning

  26. After you finish the first 90% of a project, you have to finish the other 90%.

    — Michael Abrash

    #estimating

  27. After you finish the first 90% of a project, you have to finish the other 90%.

    — Michael Abrash

    #estimating

  28. Editing this latest batch of screenlogs is a chore (just about halfway through December, now). I worked a lot of longer days, so there's a lot of footage. Also, when I'm doing a lot of rendering, there's more task-switching, so more edits to make to summarize it.

    But these will among the most valuable ones for estimating my maximum real output.

    I'm hoping to get a useful number for estimating production time on episode two, then follow through with that and see if I can't actually get it done in the predicted time.

    It'd be a real confidence builder if I could.
    #LunaticsProject #Management #Screenlogging #Estimating

  29. Editing this latest batch of screenlogs is a chore (just about halfway through December, now). I worked a lot of longer days, so there's a lot of footage. Also, when I'm doing a lot of rendering, there's more task-switching, so more edits to make to summarize it.

    But these will among the most valuable ones for estimating my maximum real output.

    I'm hoping to get a useful number for estimating production time on episode two, then follow through with that and see if I can't actually get it done in the predicted time.

    It'd be a real confidence builder if I could.
    #LunaticsProject #Management #Screenlogging #Estimating

  30. Things that are impossible just take longer.

    — Ian Hickson

    #estimating #planning

  31. Things that are impossible just take longer.

    — Ian Hickson

    #estimating #planning

  32. After you finish the first 90% of a project, you have to finish the other 90%.

    — Michael Abrash

    #estimating

  33. After you finish the first 90% of a project, you have to finish the other 90%.

    — Michael Abrash

    #estimating

  34. The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time.

    — Tom Cargill

    #estimating

  35. The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time.

    — Tom Cargill

    #estimating

  36. In carpentry you measure twice and cut once. In software development you never measure and make cuts until you run out of time.

    — Adam Morse

    #estimating #planning #programming

  37. In carpentry you measure twice and cut once. In software development you never measure and make cuts until you run out of time.

    — Adam Morse

    #estimating #planning #programming

  38. The sooner you start to code, the longer the program will take.

    — Roy Carlson

    #estimating #programming

  39. The sooner you start to code, the longer the program will take.

    — Roy Carlson

    #estimating #programming

  40. In carpentry you measure twice and cut once. In software development you never measure and make cuts until you run out of time.

    — Adam Morse

    #estimating #planning #programming

  41. In carpentry you measure twice and cut once. In software development you never measure and make cuts until you run out of time.

    — Adam Morse

    #estimating #planning #programming

  42. The first step of any project is to grossly underestimate its complexity and difficulty.

    — Nicoll Hunt

    #estimating #management #planning

  43. Things that are impossible just take longer.

    — Ian Hickson

    #estimating #planning