I’m not a long-time emacs user, but as a new one, my enthusiasm is really growing.
Like everyone, I’m finding that I’m in an increasingly disparate set of tools with diverging interface design choices to get my jobs done. The cognitive dissonance that all these different interfaces presents me with feels like it’s getting out of hand, and is growing non-linearly.
Emacs is a arcane tool, and is dated in so many ways, but I don’t know that I can find another solution that allows me to counter the ever-growing complexity of software productivity solutions that I presented with both in my personal and professional life. I know I’m not alone.
As someone who’s not a developer nor a full-time product person, (actually a doctor that wandered into tech), I often wonder why I can’t choose my own front end, and why am forced to use interfaces that don’t work very well for me. Emacs helps me escape some of that (at the cost of a huge relative learning curve, granted)
MD here. There is an inhalation and exhalation tube for each patient; the exhalation tubes would be in continuity using the described configuration. However, at least for part of the transmission route, viral particles would have to move against flow. So there is likely some cross-contamination.
All that being said in the situation where this is deployed I think it would be a risk most providers would take.
Included in the list of perhaps not totally intended consequences: I think this may allow some MD students to think twice about practicing and take less traditional (potentially less secure) career routes. I may be biased, having effectively not practiced for a couple years now myself, but I think this could be a good thing to an extent.
I work with 3-4 MDs that chose not to practice who are now working on defining software/ML product feature requirements; their MD experience makes them solid product specialists for clinical solutions that hopefully will help a lot of people...not having to stare down the barrel on loan payments may help people make these kind of career moves that may ultimately progress the system.
All that being said, we (obviously) need good docs at the bedside.
Like everyone, I’m finding that I’m in an increasingly disparate set of tools with diverging interface design choices to get my jobs done. The cognitive dissonance that all these different interfaces presents me with feels like it’s getting out of hand, and is growing non-linearly.
Emacs is a arcane tool, and is dated in so many ways, but I don’t know that I can find another solution that allows me to counter the ever-growing complexity of software productivity solutions that I presented with both in my personal and professional life. I know I’m not alone.
As someone who’s not a developer nor a full-time product person, (actually a doctor that wandered into tech), I often wonder why I can’t choose my own front end, and why am forced to use interfaces that don’t work very well for me. Emacs helps me escape some of that (at the cost of a huge relative learning curve, granted)