[mdip]

Kind of love the initial story in the article about 48-hour wait times.

I had a stint writing conferencing software for quite some time, and every once in a while we'd come across a customer requirement that had capabilities which were obvious to us developers "would be misused". As a result, we did the "Thinking, Fast and Slow" pre-mortem to help surface other ways that the system could be attacked (along with what we would do to prevent it and how it impacted the original feature).

If you create something, and open it to the public, and there's any way for someone to misuse it for financial incentive (especially if they can do so without consequence), it will be misused. In fact, depending on the incentive, you may find that the misuse becomes the only way that the service is used.

[kazinator]

When the doctor's office is inundated with patient visits, you cannot fix scheduling back-logs by fiddling with the scheduling algorithm, no matter how much data you have.

Say the calendar is initially empty and 1000 people want to see the doc, right now. You can fill them all into the calendar, or you can play games that solve nothing, like only filling tomorrow's schedule with 10 people, asking 990 of them to call back. That doesn't change the fact that it takes 100 days to see 1000 patients. All it does is cause unfair delays; the original 1000 can be pre-empted by newcomers who get earlier appointments since their place in line is not being maintained.

[strathmeyer]

How do we read more than the initial story? Do we have to pay to read it? There is no indication on the webpage there is more than two paragraphs other than the advertisement for the author's book.

[jrochkind1]

Not what I see, including in a Chrome incognito window (which shows me the whole article). Could you have an ad blocker or other extension that is going wrong? Do you use an unusual browser?

[jrochkind1]

What is 'the "Thinking, Fast and Slow" pre-mortem'?

[lifeisstillgood]

conferencing as in 'ComicCon' or 'Zoom'? Can you give an example?

[mdip]

Haha, hadn't even thought of that -- Conferencing as in developing bespoke (and some white-label) software for organizations deploying Office Communications Server (and R2), Lync and ultimately Skype for Business (I do a little Teams work these days but I am focused on other areas, presently).