Getting Started with AI: What Nobody Tells You

If you're getting started with AI right now, you've probably already read the list. Be specific. Give it context. Assign a role. Iterate. It's all true, and it's also the reason so many beginners stall out after a couple of weeks: the list explains how to write a decent prompt and says almost nothing about what happens after that.

This post is about the after. The stuff people only figure out a few months in, usually by getting burned once or twice first.

The beginner tips have gone stale

A Reddit post titled 'I spent 6 months learning AI prompting so you don't have to' laid out the classic advice: 'Role plus task plus context is the basic formula that most beginners never figure out.' Solid enough. The top replies? 'Thanks ChatGPT for this very basic information.' And: 'What is this? A repost from 2023?'

That reaction tells you something. The basic prompting advice is so saturated that people now recognize it on sight, and they can tell when it was written by the tool it's describing. The same post did have one line worth keeping, though: 'Prompting isn't a technical skill. It's a communication skill.' If you can brief a coworker clearly, you already have most of what you need. You don't have to learn APIs, embeddings or agents before you open a chat window, whatever the more intimidating threads suggest.

How to start using AI: pick a task, not a tool

The 'which AI is best' question eats a lot of beginner energy. The more useful reframe, which keeps coming up in Reddit threads about feeling overwhelmed, is: what task am I trying to make easier? Pick one annoying, recurring thing. A weekly status email. A messy set of meeting notes. Start there and nowhere else.

Nick Simard puts it well on his Substack: 'You don't need to learn AI in order to benefit from it.' His other line is the one we'd tape to a monitor: 'The goal is traction, not genius.' He also says to skip the prompt packs and elaborate automations for now, which is good advice even coming from a site that publishes prompts.

On ChatGPT vs Claude vs Gemini for beginners, the rough consensus across comparison blogs is that ChatGPT is the easy all-rounder, Claude tends to be preferred for long documents and writing, and Gemini makes sense if you already live in Google's apps. Treat that as a starting point, not a verdict. These products change fast, and plenty of those comparison posts earn affiliate money. Our guide on choosing the right AI tool for your task goes further, and it starts from the job, not the brand.

Custom instructions help, until they quietly don't

Here's one of the more confident claims you'll run into. A Reddit post called '10 things about ChatGPT that took me way too long to figure out' declared that 'Custom Instructions are 90% of the game.' That number isn't from a study. It's one user's gut feel. Still, the instinct is right: telling the model who you are and how you want answers saves you from repeating yourself in every chat.

What the same thread shows, if you scroll past the post, is the catch. One commenter pointed out that custom instructions 'don't function like reliable programs.' Over a long chat, they get compressed into a few dominant habits and the rest fades. The original poster also warned that ChatGPT's Memory needs periodic cleanup, because it can save 'preferences' you never actually had. So set instructions up early, then check on them every few weeks. If replies start drifting, our post on personalizing ChatGPT around your workflow has a checklist for figuring out which layer went wrong.

AI mistakes beginners make: trusting it to check itself

A common tip is to finish by asking the model what it's unsure about. It feels responsible. A commenter in that '10 things' thread shot it down in one sentence: 'You can't expect it to quality check itself with the same non-deterministic mechanics.' The thing that produced the error is the same thing grading it.

Two habits work better. First, when an answer is clearly made up, start a fresh chat instead of arguing with it. The bad answer stays in the context and keeps leaking into later replies. Second, if you want critique, ask for a skeptical reviewer instead of 'improve this.' 'Improve' gets you polish. A skeptic gets you problems. Then verify anything that matters yourself, because that part doesn't get delegated.

Another commenter's framing sums it up: treat ChatGPT 'like a junior collaborator, not an oracle.' Tom's Guide's list of beginner mistakes lands in a similar place, treating the first reply as a draft and the whole thing as a conversation rather than a search box.

The real bottleneck is keeping what works

This is the part nobody puts in the beginner guides. After a month or two, writing prompts stops being the hard part. One commenter described the bottleneck moving away from prompting and toward information management. You've written a prompt that nails your status email. Where is it? Buried in a chat from three weeks ago, probably.

The Beginner AI Toolkit blog lists 'no prompt library' as one of its ten beginner mistakes, alongside 'no file or naming system.' It's one of the few points on that list that holds up once you're past week one. Save the prompts that worked. Include an example of the output you want inside the prompt itself, which another Reddit commenter said 'can significantly boost quality.' When something drifts, you can compare against the version that worked instead of rebuilding it from memory. A plain markdown file is enough, or you can shape a reusable template in our Prompt Crafter.

Getting started with AI: a first week that actually sticks

• Choose one recurring task and use AI only for that, every time it comes up.
• Write a short custom instruction: your role, the format you like, phrases you never want to see.
• Treat every first answer as a draft. Ask for one specific change, not 'make it better.'
• When something is wrong, open a new chat rather than correcting it in place.
• Save any prompt that works into one file, with an example of the output you wanted.
• Hold off on paying until you've hit a real limit on the free tier.

References

• Reddit (mirror) - "10 things about ChatGPT that took me way too long to figure out"
• Reddit r/OpenAI (mirror) - "I spent 6 months learning AI prompting so you don't have to."
• Nick Simard (Substack) - "How to Start Using AI Without Getting Overwhelmed"
• Beginner AI Toolkit - "10 AI Mistakes Beginners Make (And What to Use Instead)"
• The Neuron - "So how do you 'do' AI? A beginner's guide to ChatGPT, Claude, and Gemini"
• Tom's Guide - "7 AI mistakes I wish someone had told me about when I started"