tominous

Performance and efficiency are important, but we need you to invent the monitoring tools and visualisations that will underpin alignment!

Yes there are metabolic changes in the mother herself during pregnancy but that's not why it's hard to research. The main fear is that drugs will cross the placenta and affect the growing fetus, or similarly be transmitted through breast milk to an infant. Very young humans are uniquely vulnerable to disruption in their growth that can cause life-long problems.

In my case I had hundreds of invoices in a not-very-consistent PDF format which I had contemporaneously tracked in spreadsheets. After data extraction (pdftotext + OpenAI API), I cross-checked against the spreadsheets, and for any discrepancies I reviewed the original PDFs and old bank statements.

The main issue I had was it was surprisingly hard to get the model to consistently strip commas from dollar values, which broke the csv output I asked for. I gave up on prompt engineering it to perfection, and just looped around it with a regex check.

Otherwise, accuracy was extremely good and it surfaced a few errors in my spreadsheets over the years.

If you're trying to say that immunostimulant is a term of art distinct from immune checkpoint inhibitor, then fair point.

But what it seems like you're saying is checkpoint inhibitors don't "enrage/activate" the immune system, and they only target tumours, and both points are misleading if not outright wrong.

I have very quickly picked up the habit of pasting snippets of my code into GPT-4 and simply asking "Why is this not working?" Almost every time, it succinctly explains the apparent purpose of the code, and how it is subtly wrong.

It's so good that I often do this preemptively to avoid a compile/deploy/test cycle.

I was dying on the GPT-4 API waitlist too. I built a proof-of-concept with GPT-3.5, got some ada embeddings, played around with some common patterns for a couple of weeks, spent less than $20. I then applied to the waitlist again with a few short sentences about what I'd done, how GPT-4 would make it better, and how it would enable something new and valuable for a particular market. Approved that day.

It's not exactly a shortcut, and maybe it was just luck, but I suspect the key is just to start building with what you have and show a trajectory. The best part is that coding with ChatGPT-4 as a "colleague" has made the whole thing super fun.

I just spent a month doing an E-Business Suite platform migration and it was very similar: follow the step-by-step instructions to apply patches and run commands. Each patch has a README file with dependent patches or commands which need to be completed first. It works mind-numbingly great until you run into the first of many circular dependencies.

That's one problem with treating the implementer as a machine to run code. The whole procedure can't be tested, so when parts are changed they can break the whole. It relies on the human in the loop to resolve the conflicts, which is not repeatable.

The other problem is the "mind-numbing" part. No-one can maintain 100% perfection all of the time. And in the context of presenting to people who don't know what it all means, I can see why mistakes would be made.

It's ok, because they often make you give your postcode as a second factor.

As a native speaker of English, I didn't know about mass nouns until I was an adult and I was trying to explain to a non-native speaker that they were using "the" too much.

ProxyJump (or the -J option as a shortcut) plus TCP port forwarding (-L/-R) is ridiculously powerful. You can chain jump hosts with commas, threading a port forward deep into (or out of) multiple server hops with a single command.