31–40 of 60 posts
Don't use tech with deep, unresolved flaws and you won't get fucked. Would you find it acceptable if Postgresql occassionally hallucinated and returned gibberish? Fuck no. Wny is this okay with ANY software? Answer, it's not. AI IS NOT READY.
The only way to make something better is to use it more
Some things that I know how to do, I just run myself. If starting the tests is a bash command, I asked the AI to create bash script that does this, and then I run it myself. Same, with the build, deploy and other similar tasks. For some no so important tasks, I use different model, like GLM, which is cheaper. Then I save the result of the, let's say bug analysis, or code review, and ask my main model (Opus) to read t…
[flagged]
Eternal September 2.0: the LLM edition.
cost control is a policy problem - we certainly don't need to use opus 4.6 for a simple test refactor, but many people (including myself) default to it anyways. we need a way to measure cost / performance for agents on individual repos, with individual types of tasks, to get a better sense of what tasks can be trusted to cheaper agents, and what tasks must be routed to the SOTA
Earlier quoted context omitted.
I'm working on a fun project I call OpenFAST, which essentially tries to solve the context transitioning - but its still in early days and haven't released anything yet. I think one of the bigger issues, is the o(n) orchestration to agent calls that often feels uncontrolled .. ending up making the orchestrator of sub-agents the main bottleneck due to the large context it sometimes ends up with. I'm working on an idea…
This is interesting and I would love to understand more on this..is there a GitHub which I can look at? Here's something which would help you with another perspective on the contexts https://authority.bhaviavelayudhan.com/journal/35