There was a part of the article that discussed that you create tasks, not stories.
You can group the tasks into stories or milestones or iterations or epics.
In general, he’s saying you should always keep breaking down a task until it’s a 1, since 1s are easy to estimate.
The key part that may be missed is the “mob programming” or “pair programming” aspect where all the engineers on a team sit together and work through a story or milestones or epic to come up with a list one 1 point tasks.
Obviously this still can’t be done, so the only effective end solution is maximum pair/mob programming unless all tasks in an iteration are accounted for and broken down into easily understandable and estimable bits of work.
There is at least some truth to the notion that if you use mob programming, estimating becomes pointless.
1) Services are often unique per patient. Even for patients with the same ICD-10 codes, the quality of service will vary. Hospitals cost different amounts to run. If you always peg the price to the lowest, it will be a race to the bottom for quality of service.
2) Patients are unique, with different health profiles, with different preferences for paying. Markets are different. Some markets only have one insurance payer.
It seems that an anesthesiologists job is to make sure you’re unconscious. If there’s anyone that knows how to define consciousness, it should probably be them.
Seems that consciousness is an awareness of certain stimuli that give rise to novel patterns in our brain, in turn triggering our frontal lobes to notice…
Facebook (and social media in general) has made the world a more divided place full of sadder and angrier people. He runs a company that optimizes for that scenario while accruing unimaginable sums of capital, and he doubled down with Meta. Hmm I wonder why some people are not fans.