←back to thread

548 points kmelve | 6 comments | | HN request time: 0.001s | source | bottom
Show context
swframe2 ◴[] No.45108930[source]
Preventing garbage just requires that you take into account the cognitive limits of the agent. For example ...

1) Don't ask for large / complex change. Ask for a plan but ask it to implement the plan in small steps and ask the model to test each step before starting the next.

2) For really complex steps, ask the model to write code to visualize the problem and solution.

3) If the model fails on a given step, ask it to add logging to the code, save the logs, run the tests and the review the logs to determine what went wrong. Do this repeatedly until the step works well.

4) Ask the model to look at your existing code and determine how it was designed to implement a task. Some times the model will put all of the changes in one file but your code has a cleaner design the model doesn't take into account.

I've seen other people blog about their tricks and tips. I do still see garbage results but not as high as 95%.

replies(20): >>45109085 #>>45109229 #>>45109255 #>>45109297 #>>45109350 #>>45109631 #>>45109684 #>>45109710 #>>45109743 #>>45109822 #>>45109969 #>>45110014 #>>45110639 #>>45110707 #>>45110868 #>>45111654 #>>45112029 #>>45112178 #>>45112219 #>>45112752 #
MangoCoffee ◴[] No.45109684[source]
I've been vibe coding a couple of personal projects. I've found that test-driven development fits very well with vibe coding, and it's just as you said break up the problem into small, testable chunks, get the AI to write unit tests first, and then implement the actual code
replies(3): >>45109837 #>>45111012 #>>45112453 #
yodsanklai ◴[] No.45109837[source]
Actually, all good engineering principles which reduce cognitive load for humans work for AI as well.
replies(2): >>45109935 #>>45110199 #
1. colordrops ◴[] No.45109935[source]
This is the big secret. Keep code modular, small, single purpose, encapsulated, and it works great with vibe coding. I want to write a protocol/meta language similar to the markdown docs that Claude et al create that is per module, and defines behavior, so you actually program and compose modules with well defined interfaces in natural language. I'm surprised someone hasn't done it already.
replies(2): >>45110171 #>>45110483 #
2. drzaiusx11 ◴[] No.45110171[source]
Isn't what you're describing exactly what Kiro aims to solve?
replies(1): >>45111080 #
3. adastra22 ◴[] No.45110483[source]
My set of Claude agent files have an explicit set of interface definitions. Is that what you’re talking about?
replies(1): >>45111085 #
4. colordrops ◴[] No.45111080[source]
Possibly, I've never heard of Kiro, will look into it.
5. colordrops ◴[] No.45111085[source]
Are Claude agent files per module? If so, then I guess so.
replies(1): >>45112394 #
6. adastra22 ◴[] No.45112394{3}[source]
Per source code module?