jauco

We’re on azure and a surprisingly good choice has been to use their eventhub to ingest the telemtry and then to consume it in batches of a few seconds using a consumer. Time series is hard because it is a lot of data that comes in all the time, this allows you to relax those requirements a bit.

After eventhub we’re using ducklake. But I’m not at the point where I’d flat out advise it to other people (just code immaturity that tk their credit is being worked on)

Also, if you’re evaluating postgres, check out timescaledb.

Yep, they made the spec 1.0 but it isn’t 1.0 software. Browse the bugs before use.

When it works well it’s really nice. And it beats handrolling a multi level parquet store.

Given that the author mentions both using helix and zig encouraging larger files with more content I’d be curious to know how they navigate these files in helix. The thing that keeps me from using it is lack of code folding, which I notice I use a lot when navigating larger files to zoom out.

I don’t think openai decided to have the us attack iran in order to attack anthropic?

So no. This is not a war between our corporate overlords.

It serves you.

The lawnmower exists, you might disagree, but it’s not your lawnmower, you can’t uncreate it. But you can and should take care never to put your hand near it.

Ah sorry. I thought it was just saying tesla wasn’t overvalued.

But it’s 2026 now

This would be HTR (Handwritten Text Recognition) not OCR and HTR is a lot harder than OCR especially for modern scripts (i.e. student's scrawls). And at every error the reviewer now needs to check if it was due to an error in the code or due to a bad HTR somewhere in the code.

I'd say compared to just typing the code on a disconnected computer: Not worth it.

He said copyright infringement. The company tfa is about literally trained its models using massive copyright infringement.

You’re not disagreeing with gp.

I like the law because you can quite easily formulate it without bias.

Large enough orgs will indeed get people whose job is more closely aligned with the goal vs people whose job is more closely aligned with the existence of the org. _Because_ you need to keep investing energy to keep the org in existence. You can’t just do the goal only.

But being responsible for keeping the org in existence is not the same as responsible for the goals that the org was created for in the first place.

_and_ I can see how the people whose job it is to ensure the org keeps existing will gain the majority vote.

It’s like a law of nature: the way things fall out if you’re not consciously working to have them fall out differently.

(So it can be good for google to fire them from a “let’s keep existing standpoint” even though it might be contrary to having the easiest/optimal to use product. And if that is so, the keep existing vote will have the power) I don’t use google products really that much so I can’t speak to the merits of this example.