drdrey

well maybe they did reduce supply chain risk, but still need to reduce it some more

wide events feel like structured logs, great for high cardinality data but not so much for time series

96% AI written article btw

the graphs are pretty clearly made and labeled with AI

writing specs is hard. For instance the easiest way to comply with "player should never reach the flag" is to disable movement completely, so then you have to specify "player should never reach the flag while still being allowed to move" and so on (liveness). It's not practical for most programs

you could do edits like crops in a way that preserves the signature using ZK proofs

1.5% of electricity, not energy

that would be 0.3% of global energy use

"that's on me" just sounds like Claude is doing the talking

> The results were achieved by an internal version of Astra, our next major model.

of course it does, but it's still the best thing we have

fires? floods? documents getting lost/misplaced/stolen/destroyed?

the problems are general and abstract, domain specific knowledge and memorization don't help. Figuring out the rules, the goal, the controls, and how to solve in a reasonable budget all indicate some level of general ability.

Counterpoint: don't read the comments

> And it can pay for itself twice: once in real work shipped, and once again in something else you could probably use more of, which is gravity.

what?

as someone who doesn't know how to get better design out of LLMs, can you elaborate?

I have finally embraced squashing PRs and realized I wasted my youth trying to write Good Commits.

it's tribal, it feels good to rally against a common enemy

good luck formally verifying everything

that ship has sailed

for me it's that it works remotely and my kids can access it over Discord

this seems like what MCPs should have been from the beginning. If you think MCPs are better, can you explain why?

the problem with any approach like this based on usage metrics is that it will be abused to death

...but is it good?

have you tried adjusting the reasoning effort?

5.2-codex just came out. You could use codex with regular 5.2 for a week or so.

ok but these are details, the point is that the operators of the database are external, selfish and fluctuating

death before Jenkins

the big difference is the trust assumption, anyone can join or leave the network of nodes at any time

> you don’t have to follow the herd

meanwhile, OP's entire substack post denouncing hustle culture is about plugging his viral tweet and his ebook

it's hard to take the article seriously when the author relies on a fuckgit alias on a regular basis