185
this post was submitted on 17 Jul 2026
185 points (92.6% liked)
Fuck AI
8680 readers
989 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.
AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.
Rules:
- Relevant posts only.
- No bigotry.
- No misinformation.
- No NSFW/NSFL content without being labeled NSFW or being in an appropriately-labeled spoiler tag.
- This isn't a place to talk about the cons and (supposed) pros of AI for different use cases. This is /c/fuck_ai .
- Especially no AI advocacy.
- No AI-generated content. If you want to post examples of AI failing hillariously, there are other communities for that like !ArtificialIgnorance@lemmy.ca .
- Venting is part of the purpose of this community, but don't aim frustration or accusations at other users.
- These rules are a living document that may change in the future.
You can help the mod team by making your reports detailed.
Effective reports:
- "The third image is a well-known anti-semitic trope"
- "Claiming that 'agentic AI' can outperform humans at all jobs is misinformation"
Less effective reports:
- "Breaks rules"
- "Misinformation"
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Context engineering is a skill analogous to communicating a problem to fellow maintainers. This typically involves articulating the issue within an issue tracker, pull request, or comment using written text. Therefore, proficiency in "prompt engineering" is essentially a measure of one's articulacy.
So it's not a "useful tool for coding" then, if the quality of the output depends of one's ability to articulate in a way that tickles the LLM "the right way".
Also, no matter how well you articulate, the output is still somewhat random. You can produce two different sections of code with (essentially) the same prompt, which also just means that theres an amount of luck and percieved randomness in a tool.
Imagine you want a piece of software written but you're hiring it out, like a lot of corporations do. You write up a loose specification and hand it to two different dev shops and you'll get two wildly different results. The tighter the spec, the closer the results will be.
It's not much different from that.
Indeed. I agree that it's not a tool, but a type of outsourcing.
Following my analogy with the archer, promting the right way is like accounting for wind. And again, no matter how much the best archers in the world account for wind, they do sometimes miss. Still very impressive how high their skill is, even with randomness involved. And with agentic coding, one can always shoot twice.