Medical staff don't like Epic because it's the kind of software that's sold to administrators, but used by providers. Guess who has the most sway in things like what features are included and how much effort gets invested into making the UX good?
> In each case the doctor's asked, "do you want to give him/her a fighting chance?" Of course, no one wants to say 'no' to that question, because they don't really understand what's possible and don't understand what "winning" actually looks like.
Right, and people don't generally think to ask those questions because, at that point, they're not in an emotional state that is conducive to stopping and asking questions. That said, the phrase "fighting chance" is absolutely terrible here. It's far too loaded to convey what would actually be meant here.
> You know who are the people I can most expect to be actually there for me? My actual family.
I always phrase this as "you don't fire your brother because he's an idiot." Yes, in a severely dysfunctional family, there are valid reasons to cut ties with people, but, for the most part, this is both a true statement, and gets the right sentiment across.
Of course, what you've said is true as far as it goes. But, consider this: if your employer has a product with any sort of search capability, your hobby/side project search engine then falls under the heading of things "relat(ing)... to the employer's business."
If you work for a big enough tech company, like, say, Google or Facebook, it's likely that a lot of things will "relate...to their business." And, note, too, that there's no requirement that you actually know that it relates to a part of your employer's business.
I will second this with my own "I hate working out" example.
In my case, I've figured out that what I actually "hate" about working out is the fact that I'm doing physical activity that seems to have no immediate purpose. I've often said you probably won't catch me running, unless I'm actually running away from something.
I didn't actively seek to accomplish this, but getting a dog is what's lead me to start enjoying a moderate amount of physical activity. She needs to go outside every day, rain or shine, about 3 times a day, and, ideally, needs some time to literally just run around. Walks take up the first need, and trips to the park take up the second. And, when I'm at the park, you can bet you'll see me running around with her, loving every minute of it. :-)
Based on my experience reading academic papers, I would suggest that you would often be better off skimming 3 papers in a week than reading one closely.
I would often do this in grad school:
* Go search for papers that broadly had to do with some structure or other mathematical gadget I was interested in at the time,
* Read the abstracts of those papers to find the ones that looked most interesting,
* Take the most interesting papers, and read the statements of the theorems,
* Finally, devote a little more attention to those papers that had interesting theorems that seemed to fall within the domain of what I was working on.
I did this with math papers, but there's no particular reason you can't generalize this to other fields. CS in particular can use almost the exact same methods. For less mathematical fields, you'd need to make some substitutions, such as "section headers and key topic sentences" for "statements of theorems," but you can make it work there, too.
Doing this, in a decade, you end up reading 1560 abstracts, which is probably more useful in terms of "Oh, wait, I've seen this before" type insights than reading 520 entire papers.
I am one of those people (and, also, coincidentally, typing this at 3:07 AM local time). There was a period of time in which I was forced by circumstances to go to bed every night at 10 PM (by which, I mean lights out, in bed, ready to fall asleep), and wake up at 6 AM. I did not like it, but, eventually my body adapted to it to the point where when 10 PM rolled around, I would be tired, and automatically wake up at 6 AM.
This all went straight to hell when I ended up working a very long shift one day that extended well past my 10 AM working time. From then on, I was going to sleep more like 12-1AM and waking up at 9-10 AM.