I ask llms things like I would spec it out for my team, which is to say, when I write a task, I would not include things about the sport, I would explain the lo

I ask llms things like I would spec it out for my team, which is to say, when I write a task, I would not include things about the sport, I would explain the logic etc one would need to write. No one needs to know what it is about in abstract as I see the same issue with humans; they get confused when using real world things to see the connection with what they need to do. I mean I don't flesh it out to the extend I might as well write the code, but enough that you don't need to know anything about the underlying subject. We are doing a large EU healthcare project and things differ per country obviously; if I would assume people to have a modicum of world knowledge or interest in it and look it up, nothing would get done. It is easier to deliver excel sheets with the proper wording and formulas and leave out what it is even for. Works fine with LLMs. Disclaimer; the people in my company know everything about the subject matter; the people (and LLMs) that implement it are usually not ours: we just manage them and in my experience, programmers at big companies are borderline worthless, hence, in the past 35 years, I have taken to write tasks as concrete as I can; we found that otherwise we either get garbage commits or tons of meetings with questions and then garbage commits. And now that comes in handy as this works much better on LLMs too.