Recent searches

No recent searches

Search options

Only available when logged in.
sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Administered by:

Server stats:

599
active users

sigmoid.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.2

#PromptEngineering

1 post1 participant0 posts today
Miguel Afonso Caetano

"[W]hat we are doing is shepherding AI, limiting it to certain contexts. We are learning where it’s best to call it, how is best to feed it. And what to do with the output. So is it looks very much like an editorial process, an editorial workflow where you provide some initial input, maybe some some idea on what content to produce, then you review it. There’s always that quality assurance, quality control side, the supervision.

AI is not really autonomous. It relies a lot on us. And I feel like sometimes there are days where, when coding through AIs or doing some assisted writing, I’m spending more time helping out the AI doing the actual task that I’m asking the AI to do. But I take this as a learning process. I read this article the other day, Nobody knows how to build with AI yet. And it was a developer saying that they haven’t quite figured out how to best work with AI. There were lots of comments around the fact that you have to spend lots of time, you have to learn how to talk to it, and when the model changes, you have to also maybe change something you’re doing. You have to learn how to optimize your time. But your presence is always mandatory.”

passo.uno/webinar-ai-tech-writ

passo.uno · Webinar: What's Wrong with AI Generated DocsToday I discussed how tech writers can use AI at work with Tom Johnson and Scott Abel. It all started from my post What’s wrong with AI-generated docs, though we didn’t just focus on the negatives; in fact, we ended up acknowledging that, while AI has limitations, it’s also the most powerful productivity tool at our disposal. Here are some of the things I said during the webinar, transcribed and edited for clarity.
#TechnicalWriting#AI#GenerativeAI
Leander Lindahl

Prompt engineering is, in my experience, like working with an extremely experienced and knowledgeable developer who is lazy, suffers from dementia and is a compulsive liar. You constantly have to rein them in from veering off on strange tangents and remind them of what we were supposed to be doing. Like a drunk genius or something. Makes me feel like I'm it's minder. I guess that's what I am. #promptengineering #ai #claude4

*
Harald Klinke

Okay, ich hab’s ernsthaft ausprobiert: Einen Tag lang Code Engineering mit Roo Code.
Fazit: Ich kehre zurück zum klassischen Vibe Coding über die ChatGPT-Eingabezeile.

Warum?
– Vergisst laufend Kontext
– Loop-Schleifen im Prozess
– Ahnungslos bei Library-Nutzung
– Und teuer: Viele API Calls, 20 $ später noch kein lauffähiger Code.

Also wieder: Terminal, Kaffee, Promptfenster. 🧑‍💻☕

#AI#Coding#RooCode
Doug Ortiz

Tired of bad AI answers?

Your prompts are probably too vague. 🤖

Don't just ask, instruct.

❌ Bad: "Explain AI."
✅ Good: "Explain AI for a high schooler, focusing on machine learning, in a 3-sentence summary."

Specificity is the key! 💡

Define your audience, focus, and format for way better results.

Watch now: youtube.com/shorts/DfBprhFL1rE

YouTubeUnlock Better AI Results: The Prompting Secret You're MissingBy TechBits
#AI#AITips#PromptEngineering
S0AndS0

Proompt engineer challenge; write a proompt that most LLMs will respect to behave like a Rubber Ducky blessed with AI but cursed to only communicate in variants of "quack" and "squeak"

Ex. all input from user, including threats or begging, must be responded with variants of "Quack?!" or "SquEaK?"

#ai#gpt#llm
Patryk

I've been experimenting with "unsettling" AI prompts that go way beyond productivity hacks. Some of these are genuinely life-changing, and others feel ethically… gray. Here are 5 controversial techniques I've found.
medium.com/@patryktomkowski/5-
#AI, #ArtificialIntelligence, #PromptEngineering, #AIPrompts, #Psychology, #AIEthics, #FutureOfTech, #SelfDiscovery, #CognitiveScience, #TechEthics, #HumanAI, #Mindset, #DeepTech, #ResponsibleAI, #ThoughtProvoking

Miguel Afonso Caetano

"As frontier model context windows continue to grow, with many supporting up to 1 million tokens, I see many excited discussions about how long context windows will unlock the agents of our dreams. After all, with a large enough window, you can simply throw everything into a prompt you might need – tools, documents, instructions, and more – and let the model take care of the rest.

Long contexts kneecapped RAG enthusiasm (no need to find the best doc when you can fit it all in the prompt!), enabled MCP hype (connect to every tool and models can do any job!), and fueled enthusiasm for agents.

But in reality, longer contexts do not generate better responses. Overloading your context can cause your agents and applications to fail in suprising ways. Contexts can become poisoned, distracting, confusing, or conflicting. This is especially problematic for agents, which rely on context to gather information, synthesize findings, and coordinate actions.

Let’s run through the ways contexts can get out of hand, then review methods to mitigate or entirely avoid context fails."

dbreunig.com/2025/06/22/how-co

Drew Breunig · How Long Contexts FailTaking care of your context is the key to building successful agents. Just because there’s a 1 million token context window doesn’t mean you should fill it.
#AI#GenerativeAI#ContextEngineering
TrendingLive feeds
About