logoalt Hacker News

NilMostChilltoday at 2:09 PM1 replyview on HN

> You have a lot of control over what the LLM creates.

No, you don't, you have "influence" or "suggestion".

You can absolutely narrow down the probability ranges of what is produced , but there is no guarantee that it will stick to your guidelines.

So far, at least, it's just not how they work.

> You don't have 100% control over what your LLM devs are doing, but more than you think. Just like normal managers don't micromanage every action of their team.

This overlooks the role of actual reasoning/interpretation that is found when dealing with actual people.

While it might seem like directing an LLM is similar in practice to managing a team of people, the underlying mechanisms are not the same.

If you analyse based on comparisons between those two approaches, without understanding the fundamental differences in what's happening beneath the surface, then any conclusions drawn will be flawed.

---

I'm not against LLM's, i'm against using them poorly and presenting them as something they are not.


Replies

akotoday at 2:34 PM

I think i have enough control, probably more than when working with developers. Here's something i recently had claude code build: https://github.com/ako/backing-tracks

If you check the commit log, you'll see small increments. The architecture document is what i have it generate to validate the created architecture: https://github.com/ako/backing-tracks/blob/main/docs/ARCHITE...

Other than that most changes start with the ai generating a proposal document that i will review and improve, and then have it built. I think this was the starting proposal: https://github.com/ako/backing-tracks/blob/main/docs/DSL_PRO...

This started as a conversation in Claude Desktop, which it then summarized into this proposal. This i copied into claude code, to have it implemented.

show 1 reply