This website is:

• a public repository of articles, lectures, and other original works I authored or co-authored;
• a place to repost comments, reviews, and recommendations I wrote on other sites (like Quora, Amazon, etc);
• a place where my half-baked ideas and philosophizings go if I think them interesting enough for general consumption.

This last one is what gives me trouble. Ideally, if I think a topic is worth writing about, I should make the extra 3-day effort to gather references, edit it nicely, and have it published. But like the character in “The bridge on the Drina” who means to be the town chronicler but can never find an event worthy enough to write about, most subjects have me less excited the more I think about them. By the time I finish a blog post, then, I have no intention to revisit the matter.

This is an excellent filter against appearing foolish in print, but horrible for productivity.

Two solutions come to mind readily, with equal chances of failing—either stop posting the third category of articles altogether and start writing everything with an intention of publishing; or start writing even more with the hope that at least a small percentage of that will turn into something a journal would accept for publication.

The former is a set-up for procrastination, the latter—doing extra work in a hope to create material for even more work—oxymoronic. I will try both and see where I end up.

Two years ago, I haplessly expressed excitement about my task list manager of choice being updated soon.

Speaking of @culturedcode, looks like Things 3 is progressing nicely. Hope “more structure” is code for dependencies. pic.twitter.com/ctwycDyL1e

— Miloš Miljković (@Miljko) February 2, 2014

It hasn’t yet. Two iterations of iOS and an Apple Watch later, Things 3 is still not available, and I am becoming increasingly annoyed. Inside my mind, two kinds of costs—Ms. Sunken and Mr. Opportunity—are battling it out.

Mr. O has me thinking about time wasted on not being able to turn a next action into a project; or having to make too many taps to edit anything in the iOS app. And then I stress out even more contemplating all the features I don’t even know I’m missing out on—not wanting to find out about those is why I not dare read reviews of the competition.

Ms. S, meanwhile, is raising dread whenever I thinking about moving to Omnifocus, Taskpaper, or whatever the GTD app du jour is—knowing that I would be trading a set of known deficiencies for a potentially grater set of unfamiliar ones.

The mister and missus are irrational beings—even though Things 3 remains vaporware, there have been a few 2.x updates that iOS7-fied the experience—from going flat to adding extensions and notification center widgets. All that considered, I should not spend so much time thinking about an app.

And yet, it is 6pm on January 2, 2016, and instead of writing about getting back to the lab, finally finishing the PhD thesis, or being a haughty gastro-tourist in unseasonably warm New Orleans, I am being much too first-worldly for my Balkano-Serbian comfort.

Which I will add to the pile of absurd reasons for why I dislike Cultured Code.

Shonda Rhimes on work:

Work will happen 24 hours a day, 365 days of the year, if you let it. We are all in that place where we are all letting it for some reason, and I don’t know why.

Via Cal Newport’s blog.

John Siracusa is a programmer. Merlin Man is a lifehack guru-cum-internet personality. If you are in a medical field, there is no particular reason you would know them.

They co-host a podcast that modestly has themselves as the subject matter. It is one of the best new podcasts this year, second only to CGP Grey’s (though with Road Work coming out this week, it may be a three-way tie). In this week’s episode, Siracusa had this to say about programmers (link to the audio here—it sounds better than it reads):

Plenty of people can espouse information telling some younger programmer “make sure you always call ‘srand’ before you call ‘rand’”, and they can easily tell you “don’t listen to that guy, you should not call ‘srand’ before you call ‘rand’”.

Neither one of them really understands it, because they can’t explain it. If that young programmer is saying “But why? But why? Why? How do these things work together? Explain it to me.” and they realize “Oh, I can’t explain it. All I have is this…"—it’s not a cargo cult, but it’s more like—“I have this practice that I’ve learned through supposed bitter experience that if I didn’t do this one time and something didn’t work, then I did do it, then it did work.” Very often in programming you can sort of learn that way where basically “I tried this one thing and it didn’t work, or this bug happened, then (I did) this other thing, and the bug was fixed”, and come away from that with a rule, or a heuristic, or something you think is an unwritten law without actually understanding the underlying…

Remind you of anything? In medicine, “cargo cult” is exactly
the term I would use. Programming’s saving grace is that it is a finite system created by humans, and—at least in theory—knowable. The human body is as black a box as it ever was—the only difference between now and the 1800s being a stronger flashlight.

So, programming clearly shares this with medicine: most of its practitioners don’t have a firm grasp of what they are doing, and don’t understand the underlying principles of their craft. Why, then, do we fool ourselves that adding programmers' idiosyncracies to physicians' by the way of electronic medical records, clinical decision support systems, and ultimately AI-run e-doctors, will somehow “fix” medicine instead of making it bad in a different way?

July 1st is when most US residency programs let their new interns loose after a week of corporate compliance training and ACGME-mandated talks about burnout.

If you are a medical student or a new intern, read this.

And this short post of mine still applies.

In addition, remember that it is easy to become very cynical very quickly. That is not the best of defense mechanisms, but it is better than substance abuse, domestic violence, or suicidal ideation. So, if you have to be cynical, do it up the chain of command, not down or laterally. That way you will avoid preconditioning medical students, observers, and your fellow interns. The senior residents will either support you in your jadedness, or will get to feel smug when they tell you that you are too young for that much cynicism. Your attendings should, ideally, teach you why you are wrong—though the younger they are the more likely it is they will behave like senior residents. So it’s a win for everyone, really, unless someone dings you for lack of professionalism.

Also, please remember to eat.

There are many misnomers in American medical English. Patients walk into your clinic (from Greek kline, bed) to learn whether their scan was negative (good) or positive (bad). Those who have severe chronic pain may ask for their pain medicine (that relieve pain, not cause it), usually opioids. Some physicians would call them pain-seeking (though what they are seeking is relief). If they don’t get a prescription, they may rate their doctor poorly on a patient satisfaction survey, which is a big thing if you are into quality improvement. Quality improvement. There’s a misnomer.

Quality improvement in medicine is by definition limited to improving things you can measure, i.e. quantify, i.e. judge by criteria that are the ying to quality’s yang. Those measures may be valid or not, and may improve patients' lives, longevity, etc. (or not) but they are not quality. Because they are measures. Numbers. You know, quantities.

The movement is dangerous in at least three ways. Firstly and most obviously, many of the things being measured haven’t been validated in prospective trials. They are either (poor) conjecture—like tight glycemic control for type II diabetics assumed to help because of good outcomes in type ones (since, you know, a skinny teenager and a morbidly obese 60-year-old are similar that way.) Or they came out of a corporate think-tank cocaine-fueled outside-the-box brainstorming session, like patient satisfaction scores. Some speculation on my end there. They might have been on LSD.

Secondly, even if they were the best measures in the world, tying them to promotion and compensation would have the unintended consequence of having practitioners loose sight of all other aspects of medicine, including the patient. There are many accounts of how it can happen—this one from Dr. Centor comes readily to mind—but since (1) identifying and (2) addressing the patient’s actual problem is difficult to measure objectively, it is not one of the benchmarks.

And finally, wherever there are numbers and money, techniques will evolve to game the system. David Simon’s account of how this happens in law enforcement is applicable. Want fewer central line infections? Enact a policy not to draw blood cultures from central lines! Too many nosocomial urinary tract infections? Urinalyses on admission for everyone! Hospitals create teams with dozens of people whose only job is to find new and better ways to do this. And they have to—because everyone else is doing it. A depressing amount of time, money, and effort wasted because of pointless exercises of anonymous pencil-pushers.

This is how you get to a near 3000% increase in the number of hospital administrators over 30 years. I am sure they are all good people, with good salaries, but they are, for the most part, insignificant. An epiphenomenon induced by someone’s desire to turn healthcare into an industry, forgetting that the six sigma ideology that works so well for toaster ovens can’t be forced onto moist, squishy, and fragile humans.

Which is also a good working definition of quality improvement.

“She makes the mistake of talking to patients.”

– Overheard from a fellow discussing the consult attending’s rounding habits

Is there such a thing as spending too much time with a patient? The question seems preposterous, when recent time motion studies showed that physicians in general, and residents in particular, clock embarrassingly few face-to-face minutes. The quote above was said with a wink and a nudge, but there are situations when it can be true, particularly if you talk to a patient—or get talked to—instead of having a conversation.

Two groups are at highest risk of talking too much—trainees and consultants. Many an internist remembers having to pick up the pieces after a consulting physician flew by the bedside to throw an unasked for opinion bomb. Think hematologists talking about insulin regimens, cardiologists about causes and treatment of back pain, or orthopedic surgeons about code status. “But one doctor said…” and a perplexed look is the usual outcome, more so if the consultant debated him or herself out loud.

Fellows are even more efficient sowers of confusion. Unlike some of their superiors, they still remember other fields well enough to a) have a valid opinion, and b) keep it to themselves. Where they are at highest risk for foot-in-mouth is the area of their future expertise—picking up just enough from the attendings to sound knowledgeable, yet not knowing enough to tell the patient what they don’t know. Even at later stages of training, a fellow’s best plan shared with the patient may tumble down when the attending gives a diametrically opposed recommendation. The common scenario is one in which there is no evidence, and clinical judgment rules. You can either not share your own view, or punctuate every conversation with “But we’ll see what my attending says.” More time wasted, and for nothing.

Patients themselves can be talkative, sometimes to their detriment. The reasons are many, and understandable: they have much to say about themselves—relevant to why they are in the hospital and not so much, they might not have anyone at home listening, they may have some level of delirium, dementia, or other cognitive disorder. Being able to identify such a person, and then knowing how to direct the conversation, is an unknown skill for most trainees and goes against today’s dogma of giving patients time to talk. No harm done to the chatty ones, but there are only so many hours in the day, and some of them should be spent thinking.

To be clear, we don’t have an epidemic of young doctors staying in the hospital until 2am while demented World War II veterans regail them with half-made up stories from Normandy. If only. But more isn’t always better, and physicians need to know when to speak up (to get their patient back on the topic), and when to stay quiet (not to overwhelm them with half-baked ideas).

Now they are coming for the doctors (see What’s New in Version 3.0.5). The makers of MedCalc, the best medical calculator app out there, explained what happend in detail. ⊕ Seeing that URL made me appreciate the developers even more. This was the rule they were supposedly infringing:

22.9 Apps that calculate medicinal dosages must be submitted by the manufacturer of those medications or recognized institutions such as hospitals, insurance companies, and universities.

Nevermind that many doctors view themselves as institutions—this is an idiotic rule. Is University of Baltimore, which has no biomedical science courses or programs, allowed to publish a drug dose calculator? Is GEICO?

The FDA has issued guidance for mobile medical apps. It specificaly allows calculators that use generally available formulas, and forbids apps which calculate radiation dosage, but does not mention drugs. Where, then, did this rule come from?

It is, of course, the same App store rules that allowed these pearls of quackery.

It’s madness, and it’s maddening.