HN user

ihodes

4,397 karma

Building foundation models, helping to advance science

isaachodes@gmail.com

Posts75
Comments400
View on HN
gregorygundersen.com 9mo ago

A History of Large Language Models

ihodes
7pts0
news.ycombinator.com 4y ago

Ask HN: What Happened to Pinboard (April '22 edition)?

ihodes
78pts44
knowledge.wharton.upenn.edu 8y ago

Universal Basic Income Is Not Feasible

ihodes
59pts103
www.nytimes.com 9y ago

Setting the Body’s ‘Serial Killers’ Loose on Cancer

ihodes
1pts1
blog.interstateanalytics.com 10y ago

Paid User Acquisition for Early Stage Startups – Part 1

ihodes
7pts1
www.youtube.com 10y ago

Vat-based 3D printing

ihodes
2pts0
www.hammerlab.org 11y ago

Complete Visual Testing and Continuous Integration with Seltest

ihodes
1pts0
matt.might.net 11y ago

Low-level web programming in Racket and a wiki in 500 lines

ihodes
135pts28
www.oldnyc.org 11y ago

OldNYC: Mapping historical photos from the NYPL

ihodes
60pts5
et1337.com 11y ago

The Poor Man's Gameplay Analytics

ihodes
1pts0
www.hammerlab.org 11y ago

Testing React Web Apps with Mocha

ihodes
4pts0
j2kun.svbtle.com 11y ago

Why I hate (and love) visualizations of mathematics

ihodes
9pts0
segment.com 11y ago

Segment SQL, Powered by Amazon Redshift

ihodes
86pts10
github.com 12y ago

A rich REPL for Clojure in the notebook style.

ihodes
6pts2
github.com 12y ago

Yesql - Clojure SQL queries rethought

ihodes
2pts0
www.skr.io 12y ago

Show HN: I Made a Web API for Textual Data

ihodes
27pts13
www.copperthoughts.com 12y ago

Build Business Logic in Minutes, Not Weeks

ihodes
51pts24
picoeconomics.org 12y ago

Breakdown of Will

ihodes
2pts0
ngrok.com 12y ago

Secure introspected tunnels to localhost

ihodes
4pts0
copperthoughts.com 13y ago

FinTech Hackathon 2013 and GlobalFX

ihodes
3pts1
www.humblebundle.com 14y ago

The Humble Botanicula Debut

ihodes
1pts0
www.youtube.com 14y ago

Programming Conway's Game of Life in APL

ihodes
2pts0
stackoverflow.com 14y ago

What is the single most influential book every programmer should read?

ihodes
193pts95
www.cs.brown.edu 15y ago

Automata via Macros (Lisp) [pdf]

ihodes
24pts3
www.grymoire.com 15y ago

Compendium of Unix Tutorials

ihodes
3pts0
citeseerx.ist.psu.edu 15y ago

A Gentle Introduction to Category Theory [pdf]

ihodes
93pts14
arstechnica.com 15y ago

The crooks who created modern wiretapping law

ihodes
51pts1
www.nytimes.com 15y ago

Paralyzed Man Stands, Aided by Implant

ihodes
2pts1
www.sciencedaily.com 15y ago

A Single Gene Possibly Responsible for Cortical Tissue Formation

ihodes
2pts0
tapbots.com 15y ago

Tweetbot

ihodes
110pts42

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.

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?"

Clojure MCP 1 year ago

Very cool—It seems to allow access to the page itself, not to the network or console tabs, correct?

Clojure MCP 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?

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.

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.

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...

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.

What to Learn 5 years ago

I think I agree with your argument, directionally, but in the case of the C++ hacker, might it be the case that he needed to find a different role, job, and/or manager to really leverage the power of a 98%tile C++ programmer?

I'm curious if anyone here has compared Postgraphile to Hasura? My personal difficulty in implementing these is that there aren't good source control and code organization tools for SQL and managing rollbacks and rollforwards in a sane way.

(And a way that doesn't require writing rollbacks, which sometimes aren't even possible anyway).