kleyd

7 ms·

1.
by kleyd 2mo ago
If you currently use a 7 day cooldown on a 0 day default. You can just use a 10 day cooldown on a 3 day default. But don't tell anyone...
2.
by kleyd 4mo ago
The wording in the declaration may be a bit romanticized. But the points are valid: Is an 80 year old unsolved problem maybe unsolved because it was never prioritized? Some problems stay unsolved because few people consider them worth worki
3.
by kleyd 5mo ago
Your conclusion touches on this, but I think the brain analogy is stronger than the hardware/software dichotomy. It is also my very uninformed intuition: https://news.ycombinator.com/item?id=44910353 Also interesting t
4.
by kleyd 7mo ago
The main benefit of using XML here seems to be that it forces clearer thinking and formulation from the user.
5.
by kleyd 7mo ago
The cooldown is to allow vulnerabilities to be discovered. So auto update on passing tests, which should include an npm audit check.
6.
by kleyd 7mo ago
Thought experiment: strip a forge down to what plain Git can't do: identity (who?), attestations (signed claims about a ref or actor), and policy (do these claims allow this ref update?). With just those primitives, CI is a service tha
7.
by kleyd 8mo ago
Ha, that's certainly a way to build things fool-proof.
8.
by kleyd 11mo ago
I believe this only works when there are no other uncommitted changes. So you would need to stash after the fixup commit and pop the stash after rebase. Or use autostash.
9.
by kleyd 1y ago
It's not a trade-off of clarity just to save developers some extra typing. It's actually improving the clarity by bringing the thing you care about to the foreground: the getting started page having a table of contents with specif
10.
by kleyd 1y ago
I wouldn't dare say XML is better in this regard, but a good reason to be conservative with the use of annotations is exactly that cmd+clicking them doesn't easily lead to where the behavior is implemented.
11.
by kleyd 1y ago
Current LLMs look a lot like a very advanced 'old brain' to me. While context engineering looks like optimizing the working memory. What's missing is a part with more plasticity that can work in parallel and bi-directionally
12.
by kleyd 1y ago
That matches exactly my experience. Now there are a couple of prototypes to be finished, which still takes time. And higher priority tasks get delayed instead of sped up.
13.
by kleyd 1y ago
Does anyone else find themselves starting projects that wouldn't otherwise be worth the time investment, while avoiding Claude Code for the tasks that actually have high priority? Who has had success using Claude Code on features in ol