This is a very interesting introduction to a blog post, but... I'm somehow missing the actual blog post. How does this stuff work in practice? What are some concrete examples? How does one get from JavaScript tokenizing things in a commit hook to validating that the LLM didn't disable tests it didn't agree with, or any other helpful property?

▲

gritzko 7 hours ago | parent | next [-]

I am the author. I am trying to limit one post to one page. Most people here are reading reasoning all day, I am afraid. Might get tired.

I also aspire to make one post a day. To be continued.

	▲	dofm 7 hours ago \| parent \| next [-]
		> Most people here are reading reasoning all day, I am afraid. Might get tired. This is well-observed.
	▲	derdi 7 hours ago \| parent \| prev [-]
		Thanks! I actually find human-written text very refreshing compared to what I have to read all day. I'll stay tuned.

▲

chickensong 3 hours ago | parent | prev [-]

You need to always be looking for what can be done deterministically and what can't. If it can, write a script or whatever is needed to make that happen. Your agent can help you figure this out. The agent becomes a glue layer for all your scripts. Use LLM judgement as an extra layer on top of a mechanical baseline.

> validating that the LLM didn't disable tests it didn't agree with

Provide a test runner and force the agent to call it. Have it emit something if you want evidence.