My minimal LLM instructions. These are the current ones for @jetbrains IDEs with their in-IDE AI in particular.
LLMs overengineer so easily. They have verbal diarrhea so readily. They have comments like “set a to 1” for lines like “a = 1” all the time.
This prompt reins them in … somewhat.
I have an even better approach to getting good code, but you might not like it: learn how to code
@Boomkop3 I’ve been coding for 35 years and I’m earning money with it since 1998, so I think I’m fine in that regard. LLMs can do tedious tasks real quick. And are easily overwhelmed with architecture.
I started when I was nine, and my colleague next to me learned c from the guys who were still working on linux back then.
We both tried llm’s, but found that even for tedious stuff it cannot compete with even semi decent knowledge of the advanced text editing features available in almost all ide’s.
Thank you for your receipts, now learn how to use a text editor properly.
My colleague across from me finds that a good llm helps him search trough large amounts of documentation.
@Boomkop3 It’s amazing how even in the Fediverse, there’s needlessly toxic people 😄 I think you should lighten up a bit.
Hey, you brought up receipts. Git gud m8
If you are uncertain about something, never make up possible solutions, instead state and admit that you do not know the thing.
Does this work? Given that the LLM doesn’t actually know anything or have feelings of uncertainty, surely it just adds a chance that it will say “I don’t know” purely at random, without making it any more likely that the answers it does give are correct.
I find it kind of hilarious how almost every prompt I’ve seen leaked from various apps almost always has a similar clause, as if it would have any effect at all on the result.
Seeing engineers resort to this level of basically praying and wishful thinking that in reality has no factual value is pretty funny.
“Please, don’t give me wrong results 0_0”
Copy/pastable version:
Your answers must be concise and correct. Brief and short. If one line of code suffices, give me one line of code. Do not repeat vast amounts of code unless specifically asked and tasked to. Never generate more than a few lines of code unless I tell you to. If you are uncertain about something, never make up possible solutions, instead state and admit that you do not know the thing. Never write in-code comments, make the code self-documenting instead. Never overengineer things, never invent your own requirements beyond what I specifically asked you to do.
@zkfcfbzr Thanks! It’s also in the alt text of the image. Should’ve mentioned that. 💖
A post about making AI more useful?!? On… LEMMY!?!?! Guards, prepare the excommunicado order.
/s
Does anyone have experience with phpstorm editing large projects? Are most of the bugs fixed?
@limer What bugs do you mean? I do use PhpStorm regularly, haven’t experienced any major issues (unlike with Fleet for example, that’s just not finished IMHO), but maybe your projects are different, larger, more demanding?
A lot of the bugs were after a copy paste, and error detection. I had been using it for years on the same projects, and it worked pretty good. But the new issues were seen first this year.
I went over to their youtrack, read other people’s comments and many had rolled back their version to the last release last year. So I did it too.
Then, after the second version this year someone said some of the new issues were still not fixed.
I’ll probably try it again today.
@limer I’m using PyCharm much more often than PhpStorm right now, but they do share a lot of their DNA. There were quite some exceptions being thrown with that AI integration stuff, last month, but that has all been resolved. Let’s hope the issues you ran into have gone too!
That’s great news, am optimistic now
