If you’re brewing from ground you really don’t want boiling 212F water as you’ll burn the grounds. I do my pour over at 185F and get smooth ready to drink hot coffee with no/low acidity.

If you (for some reason) want low-acidity coffee, it’s better to just get a darker roast (if you can stand the taste defects).

Ideal brewing temperature depends on a lot of factors but even ultralight roasts don’t require anything near boiling.

Store all data in one of those nocopy encodings, capnproto/msgpack? Then each language can read the same memory but with the language specific SDK

How are you not learning from reading all the code produced by Claude? Is auditing a new codebase or onboarding to a new project any different from creating a new codebase w/ Claude?

Reading code and understanding it is a very important skill and now might be the most important skill.

Imo reading code is very different to writing it.

It's analogous to reading a textbook and skipping the exercises. The exercises make you think and realize the gaps in your knowledge that you did "read" at the time but didn't fully appreciate.

> reading code is very different to writing it

As I was reading this exchange, I was wondering the same thing, why isn't a person learning the code from reading the code that was produced. I guess people learn differently when it comes to code.

Yeah nix is great for this. Also I can update infrequently and still package anything I want bleeding edge without any big issues other then maybe some build from sourcing.

Packing software with nix is easier than any other system TBH and just seems to be just getting easier.

That layering algorithm is also configurable, though I couldn’t really understand how to configure it and just wrote my own post processing to optimize layering for my internal use case. I believe I can open source this w/o much work.

The layer layout is just a json file so it can be post processed w/o issue before passing to the nix docker builders

We’ve had issues with the centralized DERPs just blackholing traffic when we startup ephemeral nodes in CI. This is despite us ensuring that all important peers can establish direct connections to each other. But there is some bootstrapping that is happening before both peers negotiate.

Having said this, it’s been almost a year since the last incident of this. It’s been rock solid the last months. Ok sure using these new peer nodes will greatly reduce this from even a chance of happening anymore. :hacks away:

That ephemeral node bootstrap issue is a classic 'edge case' that becomes a nightmare in CI. It makes sense that centralized DERP might struggle with the sheer churn of nodes popping in and out of existence. Using a Peer Relay that lives permanently on your internal net as the 'anchor' for those CI nodes seems like it would solve that race condition entirely.

Maybe this is why I’m different. I love reviewing code, it’s a great way to learn about a system, get new ideas. Diffs are great, see how things are interconnected

This one should have been prevented because the Waymo should have been driving at max 10mph