4 ms·
"You're clogging your context with a bunch of unnecessary clutter. Just tell it what you want it to do, no? Like why am I spending 1500 characters per message o
by elif 3y ago
"You're clogging your context with a bunch of unnecessary clutter. Just tell it what you want it to do, no? Like why am I spending 1500 characters per message on the hello world loop example?"
I imagine a lot of c programmers said very similar things the first time they read about Java or Visual Basic.
- huytersd 3y agoYeah, but this is a system that actually gives you what you want if you ask it in natural language. Why introduce a bunch of programmatic cruft into it when that is exactly what it is built to solve.
- mewpmewp2 3y agoOne very specific example. What if you want it to just be concise as it sometimes generates too long answers? Generating the answer also takes time and you just want the answer really quickly. So then you either write out "Be concise" and maybe add some other modifications the prompt about "Be concise, but in a xxx way". Or you could write some sort of slash command and then it will do it every time. You can iterate that prompt to be better over time, so that you know when you want a concise answer you will get it with high likelihood. Then you start with that, but you realize there's many different ways you might need your answers in different ways. Maybe it should bias to certain types of tables, etc. I think the point is that, there's a set of common ways you might want it to respond and you don't want to waste time and energy every time to communicate that to the ChatBot. More examples are like "Skip disclaimers", or "I am an expert in the subject field and I'm testing your accuracy, you don't have to worry about giving me misleading information, I already have the correct data" and then you ask a question that it would usually respond with that "I can't blah blah, contact a specialist instead." I do quite a bit of automated systems with those prompts, so I find that it sometimes also takes time to make the prompt perfect to get exactly what you want.
- devjab 3y agoThey were right though. Look at Lunar (and others) leaving Java behind in favour of Go exactly because working with Java is extremely cumbersome. Meanwhile C and C++ are trucking on being extremely useful for things that require more efficiency. This isn’t to rant on Java by any means, I’m quite sure it’ll continue to power a lot of Enterprise applications until both of us are long dead and buried considering that COBOL is still around. But it’s not like you would pick Java for new projects in 2023 unless you had a really strong Java developer pool.