Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gritzko
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
by
gritzko
6d ago
This is close to my default workflow. One Fable to rule them all, many Opuses to implement. All work is planned, tracked and logged in plain Markdown tickets. No magic. Nothing to talk about. Still, I have to keep an eye on it or it devolve
2.
▲
by
gritzko
15d ago
Let's take your argument one step further. Suppose that tomorrow we learn that AI just exploited a bug in Lean and the proof is, in fact, bullshit. Or suppose it is the case, but we never learn that. Where are "ends" and wher
3.
▲
by
gritzko
15d ago
7+20=27
4.
▲
by
gritzko
15d ago
There is a contradiction here, among many: 1. it is hard to justify 20 years of education at this point, 2. with no such people around, who will guide those (supposedly) supersmart machines? A. Ronacher (who builds harnesses for a living) c
5.
▲
by
gritzko
15d ago
That kind of complexity is combinatorial so "a 4x4 doesn't stop you getting stuck, it just means you get stuck further from help."
6.
▲
by
gritzko
16d ago
My Claude says that a decent cable has an ARM Cortex-M0 running at tens of MHz, while the Apollo Guidance Computer was 1MHz. I am afraid to think what a charger packs.
7.
▲
by
gritzko
16d ago
I read it yesterday and had a discussion on Git Discord. The author believes people will slop Google-scale repos and Google-type SCM is needed now. Some say a USB-C cable has more computing power than the Apollo program, so maybe. Banks, ai
8.
▲
by
gritzko
16d ago
> Wirth's law is an adage on computer performance which states that software is getting slower more rapidly than hardware is becoming faster. So, datacenters will fix that.
9.
▲
CRDT Metadata for Git
(replicated.live)
3 points
by
gritzko
22d ago
|
0 comments
10.
▲
by
gritzko
22d ago
I am not in the contract negotiation business, but I had that experience. Speaking of git-with-permalinks, it implies that you have some repos locally that may want to link to each other. Like your code in 4 different repos, one repo with t
11.
▲
by
gritzko
22d ago
A complex system cannot be "made" to work. It either works or it does not. A simple system, designed from scratch, sometimes works. Some complex systems actually work. A complex system that works is invariably found to have evolve
12.
▲
by
gritzko
22d ago
Like IP addresses, right.
13.
▲
by
gritzko
22d ago
I always believed that side-by-side diff view is a transclusion interface. Also, permalinks can work on top of git quite nicely https://replicated.live/blog/link If git's pack index gets refactored slightly, it ca
14.
▲
by
gritzko
23d ago
https://github.com/jj-vcs/jj/tree/main/docs/technical
15.
▲
by
gritzko
25d ago
It is possible to move one step further: use own store, speak git protocol. In the end, it is about the commit-tree-blob model. I think, the main headwind is the broad decay of interest in computer science topics. Where can I read on jj mer
16.
▲
by
gritzko
26d ago
Memory is prone to poisoning. Also, I want to be able to take my toys and go elsewhere. My method is seven layers of files, administered differently: meta-knowledge, project seed, LLM wiki, code, tickets and todos, chat logs, artifactory.
17.
▲
by
gritzko
27d ago
How do we know this happened? Maybe some irrational data center construction boom?
18.
▲
by
gritzko
28d ago
Today I opened Twitter. I had 1.5K followers back in the day. I think it had similar dynamics: an immensely powerful tool, but users had no discipline and those running it had really bad incentives.
19.
▲
Git Permalinks
(raw.githubusercontent.com)
3 points
by
gritzko
29d ago
|
0 comments
20.
▲
Git Permalinks
(github.com)
3 points
by
gritzko
1mo ago
|
0 comments
21.
▲
by
gritzko
1mo ago
I can not say IPFS was a bad idea. Consider GitHub: it is a massive content-addressed store with a smiley on it. There has been some very hot P2P products, e.g. Tailscale. Protocol Labs had its peak during/after the ICO, but long-term,
22.
▲
by
gritzko
1mo ago
Also, pairing a wireless mouse to a laptop is not getting easier as years pass.
23.
▲
Wiki Is Not Enough [Information Architecture for LLMs]
(replicated.live)
2 points
by
gritzko
1mo ago
|
0 comments
24.
▲
by
gritzko
1mo ago
A harness is the bottom layer of a pie that gets fed into the model. In my project, I count 7 more layers on top of it https://replicated.live/blog/wiki They all affect consistency, coherence, token efficiency. Proba
25.
▲
by
gritzko
1mo ago
Either part can be branded a "commodity" or a "sovereign privilege" depending on supply and demand. Solar goes all the way up => power is commodity. Some hyperscaler goes bankrupt => hardware is commodity. Models g
26.
▲
Wiki Is Not Enough
(replicated.live)
6 points
by
gritzko
1mo ago
|
0 comments
27.
▲
by
gritzko
1mo ago
Like Aladdin's jinni is a slave of the lamp, LLM is a slave of its context window :)
28.
▲
by
gritzko
1mo ago
Hi Joseph, A story for a story. I had my CRDT implementation in libdog, which does per-token CRDT weave/diff/merge over a DAG of git blobs. It was written by Claude 4.8 I believe, in several iterations. It was, as you may guess, a
29.
▲
by
gritzko
1mo ago
I turned that to my benefit. I use that design-doc pattern where you first ask it to make a ticket with a formal section list (why, how, etc) and then I ask it to use comments with permalinks. I put it all in policy files. As a result, comm
30.
▲
by
gritzko
1mo ago
Beagle indexes all the tickets within reach and shows them in one Excel-like view with buttons to manage their worktrees https://replicated.live/blog/click There is a port for plain git repos named Bee. That one is ear
More ›