drdrey

3 ms·

1.
by drdrey 9d ago
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 allo
2.
by drdrey 17d ago
you could do edits like crops in a way that preserves the signature using ZK proofs
3.
by drdrey 1mo ago
1.5% of electricity, not energy that would be 0.3% of global energy use
4.
by drdrey 2mo ago
"that's on me" just sounds like Claude is doing the talking
5.
by drdrey 2mo ago
> The results were achieved by an internal version of Astra, our next major model.
6.
by drdrey 2mo ago
of course it does, but it's still the best thing we have
7.
by drdrey 2mo ago
fires? floods? documents getting lost/misplaced/stolen/destroyed?
8.
by drdrey 3mo ago
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.
9.
by drdrey 4mo ago
Counterpoint: don't read the comments
10.
by drdrey 4mo ago
> 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?
11.
by drdrey 4mo ago
as someone who doesn't know how to get better design out of LLMs, can you elaborate?
12.
by drdrey 4mo ago
I have finally embraced squashing PRs and realized I wasted my youth trying to write Good Commits.
13.
by drdrey 4mo ago
it's tribal, it feels good to rally against a common enemy
14.
by drdrey 5mo ago
good luck formally verifying everything
15.
by drdrey 7mo ago
that ship has sailed
16.
by drdrey 7mo ago
for me it's that it works remotely and my kids can access it over Discord
17.
by drdrey 8mo ago
this seems like what MCPs should have been from the beginning. If you think MCPs are better, can you explain why?
18.
by drdrey 9mo ago
the problem with any approach like this based on usage metrics is that it will be abused to death
19.
by drdrey 9mo ago
...but is it good?
20.
by drdrey 9mo ago
have you tried adjusting the reasoning effort?
21.
by drdrey 9mo ago
5.2-codex just came out. You could use codex with regular 5.2 for a week or so.
22.
by drdrey 10mo ago
ok but these are details, the point is that the operators of the database are external, selfish and fluctuating
23.
by drdrey 10mo ago
death before Jenkins
24.
by drdrey 10mo ago
the big difference is the trust assumption, anyone can join or leave the network of nodes at any time
25.
by drdrey 11mo ago
> 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
26.
by drdrey 1y ago
it's hard to take the article seriously when the author relies on a fuckgit alias on a regular basis
27.
by drdrey 1y ago
not every line is read from a file
28.
by drdrey 1y ago
counterpoint: a lot of people around me just type "zillow" in google to access it, so maybe it's not absurd to refer to it by name in a chat interface
29.
by drdrey 1y ago
> Keep your oxidative stress low and you will not get heart disease. if you take this advice literally, you should stop exercising
30.
by drdrey 1y ago
> A while ago, I collaborated on angulartics2, a shared repository where multiple people still had admin rights. That repo still contained a GitHub Actions secret — a npm token with broad publish rights. This collaborator had access to p

More ›