Most doctors are scheduled out for weeks. Best bet is an urgent care/walk in clinic. (Good luck if they have a pediatrician.)

And less pollution from cars.

The saying for landing is: "throttle for altitude, pitch for speed". Most folks attempt the opposite.

Are we estimating developer cost (investment cost, writing code only tome), development costs (investment costs including QA time), or time to delivery and first use? People want and use estimates for different purposes. You point out great reasons why knowing what the estimates are for is important.

As mentioned in a sibling comment reply:

Time estimations, or conversations to days or other units, typically fail because if a developer says 1 day they might mean 8 focused uninterrupted development hours while someone else hears 1 calendar day so it can be done by tomorrow, regardless of if a developer spends 8 or 16 hours on it.

Time estimations, or conversations to days or other units, typically fail because if a developer says 1 day they might mean 8 focused uninterrupted development hours while someone else hears 1 calendar day so it can be done by tomorrow, regardless of if a developer spends 8 or 16 hours on it.

Regarding #4, does thinking about it count as starting? Or do they me starting to put pen to paper or fingers to keyboard?

"An error occurred: API rate limit already exceeded" at the end...

Is that intentional and a joke? I hope so. I find it funny.