Though WebP would still be nice to have..
1,769 karma · joined November 6, 2013
Though WebP would still be nice to have..
https://www.theverge.com/2017/2/22/14703108/fitbit-bought-pe...
Didn't win the competition, but expanded it over a few years and kept using it as my main blog until it fell aside when I went to university.
But unfortunately since the death of Google Reader, RSS hasn't found a way back into my life.
Just curious about what these look like
Unfortunately, this selected almost only the gallery credits lines (By (name) with (person one, person two))
How should I say to automated things: this html is not important for extraction?
As a follow up, would something like `[^=]=.` be a better capture group regex?
I first learned QWERTY without any training, I needed to type for school and I wasn’t gonna hunt and peck. Then I decided to try out Dvorak for comfort and never looked back. (Though the experience was painful to switch over after years of QWERTY)
I can still type QWERTY, in fact that’s what I use on my tablet with my thumbs, it’s a great layout for thumb typing, rarely do I find my fingers reaching over one another and I can type without looking at my screen.
That said, for physical tacticile button pressing, I much prefer Dvorak, even without labels (typing on a MacBook keyboard for example, I ignore the QWERTY printed layout) I don’t have difficulty. It’s all about the physical sensation and which mode or language or whatever gets invoked in my head.
I cannot type QWERTY effectively on MacBook keyboards or on most mechanical ones now, because of how they feel and what I use that feel for. But if it’s a cheapo Logitech or dell keyboard that you find at public locations and at work, there is barely a moment of conflict.
Aside: would an embeddable redis be a useful thing for apps and other isolated devices?
An example handout from Yale New Haven Hospital about it: https://projectepic.ynhh.org/Epic%20Newsletters%20and%20Fact...
You can also find out more about cross-vendor interchange at https://carequality.org/
I used to work at Epic and have seen in the field the requirements the immediate people need as I listed above. Billing driven documentation is an accurate way to label it. The software is implemented to maximize revenue for the hospitals and organizations, without reliable targeted information coverage agencies won't pay for what was supposedly done. There are whole teams in health care and applications from suites like Epic for such teams just for refining billing. A physician knows what they are ordering for a patient, a temp worker downstream refining billing data doesn't, therefore prioritizing accurate data from the physician will result in better likelihood of obtaining claims downstream. That however competes with the immediate need of the patient.