[cube00]

> Conversations contain a bunch of junk anyway

This is what brought me around to doing more agentic coding. I set the task, require tests and the strict linting must pass and then leave it to blow smoke up its own ass about what's going on.

I see glimpses scrolling past of all the conversational language that used to frustrate me so much when using a chat interface and I can just let it flow on past.

I come back when its made everything pass, my life is better now.

The previous match was still too clever for clippy’s type analysis, so I’ve simplified it into a direct borrowed-pattern form and I’m validating once more. I’m replacing that wrapper with a direct, non-transparent error variant so the enum stays explicit and doesn’t rely on a generic anyhow bridge.

[StilesCrisis]

Maybe I am still a novice. When I insist on tests, I get plenty of them, but on close review I'll ask "did you handle [obvious and important thing]" and suddenly it's tearing the code apart and building more stuff. It just loves corner cutting.

[cube00]

> Maybe I am still a novice.

With Boris telling everyone they should throw away their AGENTS.md file this week, I think we're all back to being novices again.

> It just loves corner cutting.

Absolutely, it tried to disable a bunch of lint rules for me calling them "overly stylistic". It also casually dropped some unsafe Rust blocks in an run of the mill CRUD application that definitely had no business needing unsafe.

No, sorry, not good enough, go back to talking to yourself until its done properly.

It eventually got there taking most of my quota with it. I'm hoping once sandboxes is more fine grained we'll be able to lock out configuration files to prevent any edits on them.

[springtimesun]

I have been doing this with opencode. Spend a fair bit of time composing and scoping a ticket. tmux on the server where the local inference lives, start a non-interactive session that starts with “read issue #123, do all your work in a feature branch” and ends with “push and open a PR”. Like not watching someone else load your dishwasher, you appreciate the end result a lot more if you don’t watch the process, even if you rearrange things before you start it.

[cube00]

Local inference can't arrive soon enough. On my inferior hardware the models still struggle to build the correct JSON to be able to call tools. Once either I get better hardware or the local models improve I'll happily leave it chugging away for a few hours to arrive at a solution because I know I'm not going to get token shock from all the looping if I'm running local inference.

[springtimesun]

I have spent way too much on hardware. I’m sure I will look back on that after the eventual price normalization with some regret. I do think we will look back at this shortage and name it as the thing that accelerated innovation at getting quality out of smaller models.

Hang tough. The other day someone posted a solution to get a model running off of SSDs. It won’t be fast, but it will be coming.