twoelf

6 ms·

1.
by twoelf 6mo ago
Yes, it does help, when you know exactly what it needs to be doing, then you can see the truth.
2.
by twoelf 6mo ago
https://x.com/twoelf47/status/2038633678277107986
3.
by twoelf 6mo ago
https://x.com/twoelf47/status/2038633678277107986
4.
Ask HN: Is it still worth making "Huge" Language Models for dev tools?
2 points by twoelf 6mo ago|1 comments
5.
by twoelf 6mo ago
I've laid the groundwork to do this locally, but the current crop of LLM agents just can't close the loop. Trying to get them to finish the job inevitably sends me right back into the spiral. Thinking i should do it manually. Read
6.
by twoelf 6mo ago
Fair. “It understands” is probably the emotional description, not the technical one. The practical problem is that it can imitate understanding well enough to get a large project moving, then break down right where durable system memory and
7.
by twoelf 6mo ago
Okay.But if I need three different framings just to converge on one coherent implementation, I’m still doing architecture recovery by hand. That’s a big part of why I started building something local around the codebase itself.
8.
by twoelf 6mo ago
Yes, this is very close to what I meant. They keep reconstructing the codebase from fragments instead of actually carrying the system forward, so you get re-implementation, duplicates, missing edge cases, and slow architectural drift.
9.
by twoelf 6mo ago
Yes, exactly. That’s why it feels so strange in practice. It can mimic understanding well enough to get you moving, but when the project gets deep enough, you find out it was generating plausibility, not actually holding the system in its c
10.
by twoelf 6mo ago
Mine goes a bit further than that. It structures the codebase first, feeds that into local agents, and then uses whichever model is on top with actual system context instead of making it guess from prompts.
11.
by twoelf 6mo ago
Yeah. Sometimes we have to finish ourselves. The vibe gets you started, but it rarely gets you all the way there.
12.
by twoelf 6mo ago
Yeah, but humans can learn, remember, and usually don’t hallucinate. They get better over time on a specific codebase, framework, and system.
13.
Ask HN: Is it just me?
18 points by twoelf 6mo ago|33 comments
14.
by twoelf 6mo ago
https://x.com/twoelf47 , follow for updates
15.
by twoelf 6mo ago
Okay
16.
by twoelf 6mo ago
This isn’t a concept. I rebuilt what I believe the foundation should be and have it working already. Monocod is a live prototype that understands the codebase itself instead of reconstructing context every time.
17.
Monocod
1 points by twoelf 6mo ago|5 comments
18.
by twoelf 7mo ago
Here's Express.js (the npm package, 141 files). Scanned in 551ms on a laptop: - 1,953 components extracted - 17,505 typed dependencies mapped (not just "A calls B" — ownership, injection, weak ref, circular, etc.) - 2
19.
No LLM, No training data, No cloud – Engine that understands architecture
2 points by twoelf 7mo ago|2 comments