▲ | js2 5 hours ago | ||||||||||||||||
After decades of writing software, I feel like I have a pretty good sense for "this can't possibly be idiomatic" in a new language. If I sniff something is off, I start Googling for reference code, large projects in that language, etc. You can also just ask the LLM: are you sure this is idiomatic? Of course it may lie to you... | |||||||||||||||||
▲ | NitpickLawyer 4 hours ago | parent | next [-] | ||||||||||||||||
> You can also just ask the LLM: are you sure this is idiomatic? I found the reverse flow to be better. Never argue. Start asking questions first. "What is the idiomatic way of doing x in y?" or "Describe idiomatic y when working on x" or similar. Then gather some stuff out of the "pedantic" generations and add to your constraints, model.md, task.md or whatever your stuff uses. You can also use this for a feedback loop. "Here's a task and some code, here are some idiomatic concepts in y, please provide feedback on adherence to these standards". | |||||||||||||||||
▲ | woodruffw 5 hours ago | parent | prev [-] | ||||||||||||||||
> If I sniff something is off, I start Googling for reference code, large projects in that language, etc. This works so long as you know how to ask the question. But it's been my experience that an LLM directed on a task will do something, and I don't even know how to frame its behavior in language in a way that would make sense to search for. (My experience here is with frontend in particular: I'm not much of a JS/TS/HTML/CSS person, and LLMs produce outputs that look really good to me. But I don't know how to even begin to verify that they are in fact good or idiomatic, since there's more often than not multiple layers of intermediating abstractions that I'm not already familiar with.) | |||||||||||||||||
|