ihodes
Joined 16 years ago
Karma
4,397
Submissions
525
Member since
Mar 19
Recent submissions
Comment · 4 months ago
Regarding information sharing, not quite. Covered entities (term of art in HIPAA), which include providers (and also payers!) including both the lab and your doctor, do not need your permission to share information between them for the purposes of treatment, payment, or operations (commonly, "TPO"). A BAA between a covered entity and a vendor (like an EHR or PACS [viewer for your imaging]) also does not require any patient consent.
There are sometimes things you might not like hidden in the releases you're signing, beyond the run of the mill acceptance of financial responsibility / assignment of benefits, notice of privacy policy acknowledgment, consent to treat.
Comment · 7 months ago
That's good—you guys should come out to visit sometime!
Comment · 7 months ago
I agree that programming language can be a better (denser, more precise) encapsulator of intent than natural language. But the converse is more often true; natural language is a denser and more precise encapsulator of intent than programming language.
I think there's some irony in using Russell's quote being used this way. My intent will often be less clear to a reader once encoded in a language bound inextricably to a machine's execution context.
Good abstraction meaningfully whittles away at this mismatch, and DSLs in powerful languages (like ML-family and lisp-family languages) have often mirrored natural(ish) language. Observe that programming languages themselves have natural language specifications that are meaningfully more dense than their implementations, and often govern multiple implementations.
Code isn't just code. Some code encapsulates intent in a meaningfully information and meaning-dense way: that code is indeed poetry, and perhaps the best representation of intent available. Some code, like nearly every line of the code that backs your server vs client time example, is an implementation detail. The Electric Clojure version is a far better encapsulation of intent (https://electric.hyperfiddle.net/fiddle/electric-tutorial.tw...). A natural language version, executed in the context of a program with an existing client server architecture, is likely best: "show a live updated version of the servers' unix epoch timestamp and the client's, and below that show the skew between them."
Given that we started with Russell, we could end with Wittgenstein's "Is it even always an advantage to replace an indistinct picture by a sharp one? Isn't the indistinct one often exactly what we need?"
Comment · 1 year ago
Very cool app. Is there a way to periodically import from a Google Sheets spreadsheet? I track a bunch of things there on a daily basis and would love to have those pulled into this application.
Comment · 1 year ago
"(…) They can be used to make containers because they are thicker than conventional cellulose-based materials. The new material is expected to replace plastics for this purpose, as plastics are a source of ocean pollution."
Comment · 1 year ago
Very cool—It seems to allow access to the page itself, not to the network or console tabs, correct?
Comment · 1 year ago
If there were an MCP to connect to, say, a running Chrome tab with your frontend running on it, that would allow an agent to both visually inspect and interact with the webpage as well as look at the network and console tabs, etc. That would be hugely helpful. Is there something like that today?
Comment · 1 year ago
1. Fracking tech allows us to drill horizontally, and enhanced geothermal systems rely on this to get that surface area exposure at 7+ km below the surface
2. The steam's extremely (225C+) hot, so there are losses but doesn't make it infeasible.
Below a certain depth, the earth gets 1º hotter per 40m of depth.
Comment · 3 years ago
Greg's blog is a great example of Katex in the wild: http://gregorygundersen.com/
Comment · 3 years ago
My take (as a paying subscriber to both, largely because I want to support this world and think both teams are insanely talented and great) is that they're solving similar problems, with some different features.
I wish I could use both with a sync between them until I figure out which one I'd want to stick with. Or stick with both.
Comment · 4 years ago
It's absolutely declined, no question. Further, the advanced search tools have been all but eviscerated, so it's even more difficult to find what you want even if you know what you're looking for.
Comment · 4 years ago
This is great, and love that making apps like this is getting progressively easily.
Curious for your take on the recently-released https://github.com/Tensegritics/ClojureDart
Comment · 4 years ago
I think this is a great summary of some of the main challenges nurses are facing.
I'd add to #1 that travel (temp) nurses are making 4x+ more than staff nurses, I've heard as high as $13-17k per week in high-demand areas. This exacerbates the problem, as staff nurses hear this, and if they can, they leave. Travel nurses can be great, but they won't know the facility and workflows and people as well as staff nurses: staff nurses now pick up more slack, all while getting paid 1/10th what their new colleagues are. This is more than most doctors.
For #3, this problem is made worse by additional compliance burden. Nurses need to document more and more, click more and more, read more and more… with less and less time. And on systems that are unpleasant to use. Among other issues, this leads to problems like these[0], which drive more and more nurses away.
I'm working with a badass team on solving some parts of these problems, particularly relating to technology and workflows. If you're interested (across basically any role, but product designers, engineers, product managers are top of mind right now), let me know (email in bio)!
[0]: https://www.cbsnews.com/news/radonda-vaught-nurse-guilty-dea...
Comment · 4 years ago
Same, I have a free account from having signed up when it was something like $8 for life, the core features actually seem to work pretty well (though I have had some documented search issues where tags weren't being searched; I think that was resolved and one-off).
I pay for the archiving service partially to support Pinboard because I want it to stay solvent, partially because it soothes me to know I can refer back to websites (at least the page I archives) that I found valuable in the past.
[email protected]