Live data from Hacker News

Applying Brevity and Language Efficiency in Prompt Engineering

prahladyeri.github.io

11–20 of 22 posts

Re: Applying Brevity and Language Efficiency in Prompt Engineering

#11
"Premium models: GPT-4o, Claude Sonnet, Gemini 1.5 Pro"

TFA was written by an AI without even search access, or it would know that all those are OLD deprecated models. AI Slop.

If the author doesn't even bother checking what his AI spit out, why would I read it? Useless article. I'm baffled that this reached the front page.

Re: Applying Brevity and Language Efficiency in Prompt Engineering

#12
post #3

Very interesting read. What jumps out at me is a lot of this is still very task oriented. And each to their own, but anecdotally, I haven't seen great results from task oriented behavior. I don't mean that it does not produce what was asked for. I'm saying that tasks even when created by engineering and product teams are often wrong. I lean very heavily towards outcome based prompting. Say exactly what do you want ac…

Say what you want, followed by how you want it done, which includes unit testing, research (Claude can do research for you) on best practices, etc. I usually also follow up with "Why would I NOT want to do this this way, be critical of this." Usually outlines sensible issues, you give guidance, then the plan is ready to go. Then you test, test, and when you're done testing, you test some more, and review all code. I…

[deleted]

Re: Applying Brevity and Language Efficiency in Prompt Engineering

#14
post #5

A little bit more time and people might finally understand why we have formal deterministic languages, and we'll be back full circle to proper programming.

Exactly. If LLM coding had come first we'd build statues of whoever invented deterministic programming.

Re: Applying Brevity and Language Efficiency in Prompt Engineering

#18
post #11

"Premium models: GPT-4o, Claude Sonnet, Gemini 1.5 Pro" TFA was written by an AI without even search access, or it would know that all those are OLD deprecated models. AI Slop. If the author doesn't even bother checking what his AI spit out, why would I read it? Useless article. I'm baffled that this reached the front page.

Not to mention the very first example.

Before:

> “I want to know why my React app’s state is not updating when I click a button.”

After:

> “React 18. useState. Button click handler sets state but component does not re-render. No error in console. Explain top 3 causes and fix for each. Show code.”

> Notice the transformation: 22 words down from a long conversational sentence, yet more information is packed in because every word carries signal.

It's 27 words up from 17, and would produce poor results on the local models this claims to be targeting. Without some way to iterate and close the loop, models are pretty bad at producing good prompts.

Re: Applying Brevity and Language Efficiency in Prompt Engineering

#20
i'm not a dev and surfing vibe coding. for me is not just a matter of brevity but a matter of clear scope instead. foggy but short prompt is far worste than clear but a little bit longer. just transfer a clear and bright idea, first set it up in your mind, well fixed with the infrastructure you are working with, than try to transfer it in the most direct way
Post reply on HN