The Reddit Thread Where Nobody Talked About Prompting

Everyone's in conversation, but Andreas is still waiting.

The scenario: an IT manager posts on Reddit. He’s been using Claude for years and feels like he’s still using it the old way. Wants to know how to catch up.

It’s probably the question you’ve been quietly asking yourself for about eighteen months, so you read every comment. Then you read them again, because something is off about the whole thread and it takes you a second to clock what.

The top answer is two words

“Ask Claude.”

31 upvotes. Three times any other comment. In a thread about how to use Claude, the top reply is “just ask the thing itself.”

Which is, when you think about it, the whole point. If you’re asking strangers on Reddit how to use Claude in 2026, you’ve already answered your own question about whether you’re behind. The tool you’re trying to catch up on is the tool you’d use to catch up.

Cute. But scroll down.

Nobody mentions prompting

Go read the thread. I’ll wait.

The word “prompt” barely appears. Five years of “learn to prompt better, learn to prompt better, learn to prompt better” as the entire genre of AI advice content — and in a thread about leveling up Claude usage, nobody is talking about magic words.

The new vocabulary is memory, context, skills, MCP, CLAUDE.md, knowledge bases, workflows. That’s not prompt-engineer talk. That’s sysadmin talk. Tscssvsavs vhe mental model in the thread shifted from what do I say to it to what environment do I build around it.

If you’ve been using Claude the old way and you’re trying to figure out what the new way is — turns out the answer matters less than what surrounds the answer.

The most upvoted real comment argues against putting things in prompts

The top substantive reply (comment #7) is basically a pitch for getting context out of the chat window.

Progressive disclosure. CLAUDE.md as an index that routes to other files instead of one giant brain dump. Skills as saved templates the agent loads when relevant. Memory as a persistent layer the model pulls from, so you stop re-explaining yourself every conversation.

The whole architecture: stop typing the same things over and over. Let the agent reach into a structured system instead of waiting for you to paste it all back in.

Most people are still in a chat window. Most people are still copy-pasting yesterday’s context into today’s session. Most people, including (until embarrassingly recently) me.

The catch-up isn’t “learn fancier prompts.” It’s “stop prompting so much and start building the environment around the model.”

Casually mentions shipping first app; nobody reacts

This network engineer’s comment mentions in passing that he shipped his first app last week.

Eighteen months ago that would have been a remarkable claim. Worth a whole reply. Worth a follow-up. Worth at least a “wait, what?”

In this thread it’s a throwaway line in a comment about which YouTuber he watches. Nobody asked him about it. Nobody upvoted it. It’s just there.

You can feel the floor shifting in moments like that. Not because the claim is shocking, but because the lack of reaction is. The bar for what counts as noteworthy moved while nobody was paying attention.

The clearest comment in the thread got one point

No CLI stack. No workflow. No tool list. Just:

“I use Claude like an intern... I don’t expect Claude to be perfect so I don’t get too frustrated when it isn’t... It saves me real time in my job, but it doesn’t do my job for me.”

One upvote.

The grand “set up CLI, ask for anything, profit” comment got more attention — and earned the best reply in the thread: “you’re just a straight shooter with upper management written all over you.” Which, fine, made me laugh. But it also tells you everything about which register the room rewards. The room rewards the confident stack. The modest “intern” framing dies in the corner with 1 upvote.

So if you’re reading these threads to figure out what to do: calibrate. Upvotes track confidence, not usefulness.

Here’s the catch-up, for one half of you

If you’re using Claude for your side projects, your notes, your writing, your weekend builds — the catch-up is real and the catch-up is doable.

It’s a switch in mental model. From interlocutor to agent. From what do I say to what does it have access to. From the chat window to the file system. From magic words to plumbing.

Build the environment. CLAUDE.md, skills, memory, MCP servers pointed at your actual stuff. Stop pasting yesterday into today. Let the model reach instead of wait.

That’s the catch-up. The Reddit thread, read carefully, is telling you exactly that.

And then there’s the other half of you

Andreas, the OP, asks the hardest practical question in the thread: how do you use this stuff when your inputs are proprietary, and sanitizing them eats all the time savings?

One person replies “ditto.” Zero solutions. Everyone else goes back to talking about their personal productivity setups.

That silence is the loudest signal in the whole thread. The personal-use case is solved. The enterprise case — where the data is sensitive, where the inputs can’t leave your environment, where sanitization costs more than the workflow saves — is wide open, and nobody on r/claude is even pretending to have an answer.

This is where the YouTubers fail you. You can absolutely build a great Claude workflow for personal stuff. Great. But the minute you try the same setup inside a company with a real compliance posture, you hit a wall no YouTube tutorial gets you over. Different problem. Different vocabulary. Different room, and that room is not on r/claude.

If you’re an experienced tech person feeling behind on AI, and your day job involves data you can’t paste into a chat — you’re not behind. You’re standing exactly where the field still hasn’t figured itself out. The gap is real. It’s not a you problem.

So which half are you in?

If your AI use is personal, the catch-up is environment. Build the plumbing. The Reddit thread is right.

If your AI use is professional and your data can’t leave the building, the catch-up doesn’t exist yet. Not the version that fits your actual constraints. The two-word answer at the top of the thread — “ask Claude” — still works for figuring out the personal-use catch-up. It doesn’t work for figuring out what to do about the data in your company’s S3 bucket that legal said can never see an API.

You and Andreas are in the same room. Nobody’s coming to that room yet.

That’s not a reason to stop trying. It’s a reason to stop measuring yourself against people who don’t share your problem.