2,868 karma · joined March 5, 2021
--- EMAIL all complaints and progress reports to admin@__your__url__here.com
...your information though, not the product. They'll sell you out if they get the right MBA.
If we do a bad job building context, they do a horrible job contexting. People who have trouble working with AI have the same problem people have in general: if they can't figure out the context of the direction, then they make random decisions of doing anything. On the flip side, if you can build the proper context around a sufficiently powerful LLM, they can derive the context via the contexting they're good at.
This is why building documents, tests, and code all in some intent pattern via prompting allows them to do a significant amount of work a normal person would have a great effort t
oh. they do. I built that. It's pretty fancy.
But there's still human direction behind most projects in the cybersphere.
38GB of vram resident. more tk/s, more prefill.
The fact that it basically broke open the local model supremacy was just a nice side effect.
I'm running: https://github.com/peonist-ai/halogen-server with a quant4, PLE offloaded, and it's resident VRAM is 36GB at 265k context.
Shave 10 more GB off and the TAM openai and anthropic are targeting is a lost cause. Local models are what 90% of people will need.
If the world governments can get a handle on the memory cartel, then there's no more moat for most normal humans.
So it makes sense, since all you need is compute, that there's a ceiling and specialization is going to be more valuable then some super AGI.
Especially since the worst people seem to be the ones who think they'll all run away with the bag.
Nothing about complexity, simply github setup such an easy automated system but AI cares not about whether their commit+push is going to kcik off a whole rebuild.
Same thing happens when I run docker build loops. The AI gives very little shit, unless I tell it, about not busting cache; so it'll sit there for hours making minor changes just to make a 30 minute build.
AI has not concern about how long anything takes, in general, but it if it's just waiting for it to return, it won't get impatient.
We're sorta in the age of alchemy. Lots of cranks out there, but there are real recipes.
I'm using local models, and they go slow enough that I have no trouble following along with what they're doing; but visually, both go and typescript, along with react native, make me puke. So I wouldn't be able to do this without AI.
I describe how to do it in my comment history, but it's basically a Super-TDD along with some custom engineering harness.
I don't want to say skill issue, but the same way you can give a chain saw to a teenager and one to a skill craftsman, well, AI can obviously create whatever you want it to do.
I think some of the variety is simply how fast SOTA models pump out garbage that you simply have to close your eyes because it's not sensible to just watch characters flow across the screen.
Almost all the coding I'm doing via AI is just faster than readable. But I can see the thinking traces and I stop to model when it's obvious it doesn't understand my intent, etc.
So I'm not doubting you created garbage. I'm just doubting that it's a product of soley AI use.
Context then is: docs, code and tests. Rather than try to build some omniscient agent, the context is built where the agent needs it.
I'm working on javascript, and now I'm only doing this via typescript. I've successfully got this going:
1. Design a feature in plain language with the coding agen (opencode) and write a document for it.
2. Restart the context (or I use /compact to flush any errant details)
3. Pull the new plan into context and ask the agent to revise it follow Test Driven Development.
4. Depending on how big it is, the agent places it into multi stages, each with it's own document.
It then loops through the stages. It might be entirely based on the language you're using, but this loop seems strong enough.
Then when there's bugs, errors, anything, we update the doc, add more tests, then revise the code.
It's quite possible the harness you're using isn't setup properly. For me to do this locally, I had to hack on dynamic context pruning which I described here: https://news.ycombinator.com/item?id=49906637#49907641
I think the conceptualization vs implementation is what you're arguing with. They won't put safety on anything they give to the military industrial complex. They'll sell them whatever they want, whenever they want, because those budgets are greater and the liability less.
And it's quite fascinating. Still dont think there's trillions of TAM out there if Qwen3.8-Flash-Next runs fast enough on $3k (before memory cartel) pricing.
Once qwen3.8-flash-next showed up, it cañ go "forever" with dynamic context pruning.
It's fascinating for local coding.
If they can follow Qwen3.8-Flash-Next, the could draft off the huge reduction in VRAM requirements.
Annnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnyways.