hsaliak

5 ms·

1.
by hsaliak 10d ago
Nobody is going to read that though, reading will go the way of code reviews. That’s the problem.
2.
by hsaliak 25d ago
Ever since coding agents came out, It felt a little like we were implementing the self improving lisp programs of old. This idea almost gets us there. Could the next step be to make it the program itself?
3.
by hsaliak 27d ago
At least it’s safe
4.
by hsaliak 2mo ago
The state of Agent APIs is bad. completions API (supported indefinitely) but does not support reasoning. OpenAI's reasoning API started out well, but is moving in the direction as described well in the article. Anthropic's message
5.
by hsaliak 2mo ago
yes it does - https://github.com/hsaliak/std_slop/blob/main/system_prompt.... I've added the same thing to the system prompt of the internal agent I wrote for work, which talks to claude models. I h
6.
by hsaliak 2mo ago
Seems to be doing too much, a 1 line in the system prompt is all you need. And it works well enough. “Output tokens are precious, be succinct in your responses. Use ASD-STE100 simplified technical english”
7.
by hsaliak 2mo ago
Let all trust this team to deliver AGI.
8.
by hsaliak 2mo ago
This graph biases outcomes (A| O) it would be interessting to have an others.. so we can view the whole picture
9.
by hsaliak 2mo ago
so the joke was the implication that they are not frontier.
10.
by hsaliak 2mo ago
no, this post was written by Demis from Deepmind.
11.
by hsaliak 2mo ago
I have my own coding harness (std::slop), in that i focus on a vim centric flow. Basically a few commands open. up my $EDITOR which is vim. 1. /edit => opens in editor 2. /feedback => opens the last llm message in an editor
12.
by hsaliak 2mo ago
It's been clear for some time that model tool calling is heavily fit to a few common patterns, it's unsurprising that a tool call that looks the same or has the same name, but works differently, is falling back to priors and causi
13.
by hsaliak 3mo ago
so he's the quintessential brilliant jerk, ok
14.
by hsaliak 3mo ago
Gemini fumbled not on the models but on the basics. Gemini 3.1 flash was actually an amazing model to code with and their 20 dollar AI plans had solid value, but they locked it all behind 429s, needless gatekeeping of clients and poor produ
15.
by hsaliak 3mo ago
Big Monsanto energy
16.
by hsaliak 3mo ago
I’ve been looking for a way to articulate this shift, and your analogy nails it. The value of libraries and infrastructure components in software engineering is eroding fast. I am sure that in many organizations, teams responsible for this
17.
by hsaliak 4mo ago
I have a custom agent that generates patches like you will with kernel development and I review and merge those in. https://github.com/hsaliak/std_slop/blob/main/docs/mail_mode... My agent forces t
18.
by hsaliak 4mo ago
I wrote https://github.com/hsaliak/std_slop/blob/main/docs/mail_mode... to avoid the brain rot from just shooting slop. It has helped me stay sane, review code and make changes step by step. I dont
19.
by hsaliak 4mo ago
Its going to be interesting to see how this holds up in production after a release or two.
20.
by hsaliak 5mo ago
The problem with vibe coded re-writes is that you basically sign off on understanding the generated codebase at that point. Any historical knowledge of the codebase is gone.
21.
by hsaliak 5mo ago
the problem is not the forward pass, its the control/feedback loop when slop is written in response to the forward pass. Perhaps we should give the LLM 2 specs, one designed for the forward pass and another for the acceptance criteria
22.
by hsaliak 5mo ago
nobody knows what to build when everything can be built, there is no moat.
23.
by hsaliak 5mo ago
Using CRDT gossip to inform scaling is a clever idea. You are on to something there. Perhaps extract it as a core library/concept from the runtime? I feel that would be generally useful!
24.
by hsaliak 5mo ago
I have a coding agent https://github.com/hsaliak/std_slop where the sessions are in SQL ledger. So /session [new, clone, deletes, undo] are supported and all sessions are persistent. Cloning lets you 'fork&#x
25.
by hsaliak 5mo ago
I find parallel agents to be an exception rather than a norm. Maybe I’m the problem? For those exceptional cases, opening a few more terminals gets the job done. It’s unclear to me if this needs to be the primary workflow. My brain natural
26.
by hsaliak 5mo ago
I made https://github.com/hsaliak/filc-bazel-template bazel target for people who may want to use these two together to make hermetic builds with it.
27.
by hsaliak 5mo ago
Clojure had lousy error messages, agents deal with this well. Clojure is capable of producing some of the most dense code I’ve ever seen, so manual code reviews really start to feel like a bottleneck unless your goal is to level up.
28.
by hsaliak 5mo ago
I've long had the same idea.. this one has legs.
29.
by hsaliak 6mo ago
Tool output truncation helps a lot and is one of the best ways to reduce context bloat. In my coding agent the context is assembled from SQLite. I suffix the message ID to rehydrate the truncated tool call if it’s needed and it works great.
30.
by hsaliak 6mo ago
This is most certainly vibed with a few optimization focused prompts. Yes - performance is a feature, but so is lack of risk.

More ›