Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I agree to an extent

My project is quite well documented and I created a Prompt a while back along with some mermaid diagrams

https://github.com/tomaytotomato/location4j/tree/master/docs

I can't remember the exact prompt I gave to the LLM but I gave it a Github issue ticket and description.

After several iterations it fixed the issue, but my unit tests failed in other areas. I decided to abort it because I think my opinionated code was clashing with the LLM's solution.

The LLM's solution would probably be more technically correct, but because I don't do l33tcode or memorise how to implement Trie or BST my code does it my way. Maybe I just need to force the LLM to do it my way and ignore the other solutions?





Just looking at PROMPT.md:

The role thing doesn't work anymore ("You are a..."), it's just fanfiction.

Also adding MUST NOT just pollutes the context, it's the "don't think of a pink elephant" but for LLMs

It's enough to say "Use Java 21+", no need to add a negative of "don't use below 21"

And this is just weird: "MUST NOT Change the license from MIT" - did an agent change the license in your code or what prompted you to add this?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: