u/LoadOld2629

was paying $20 Claude Pro. $20 ChatGPT Plus. $19.99 Gemini Advanced.

sixty dollars a month. every month. for eight months.

cancelled all three on the same day last tuesday.

here's what actually happened:

nothing.

my work didn't collapse. my outputs didn't crater. my productivity didn't visibly change in the first week.

and that embarrassed me more than anything else.

sixty dollars a month for eight months is almost five hundred dollars. and apparently i could have been fine without most of it the entire time.

here's the honest breakdown of what i actually lost:

Claude Pro — the message limit hits now. i have to be more deliberate about what i use long context sessions for. genuinely the only thing i miss.

ChatGPT Plus — honestly barely noticed. i was using it for tasks the free tier handles fine. the upgrade was habit not necessity.

Gemini Advanced — noticed nothing. the free tier does everything i was using the paid tier for. genuinely cannot identify a single workflow that got worse.

here's what the free stack actually covers in 2026:

Claude free — Sonnet. capable. message limited but enough for focused sessions.

ChatGPT free — GPT-4o. limited but real. more than enough for single session work.

Perplexity free — real time research. five pro searches daily. unlimited standard. replaced google entirely.

Leonardo AI free — 150 image credits daily. never once hit that ceiling.

NotebookLM free — document analysis. zero hallucinations. still the most underrated free tool available.

the one thing i kept:

Claude Pro.

just Claude Pro.

because the one thing i genuinely couldn't replicate on free was the long uninterrupted context sessions for serious work. that's the only paid tier that changed something i couldn't work around.

everything else was sixty dollars a month of habit dressed up as necessity.

the uncomfortable math:

most people paying for multiple AI subscriptions are paying for the security of having access. not for the actual usage that requires it.

it feels risky to cancel. like you're giving something up. like you'll need it the moment it's gone.

you probably won't.

the one week test: track every time you hit a limit that genuinely blocked real work. not inconvenienced you. blocked you.

for most people that number is smaller than the monthly bill justifies.

what subscriptions are you paying for that you've never actually tested whether you need?

was paying $20 Claude Pro. $20 ChatGPT Plus. $19.99 Gemini Advanced.

sixty dollars a month. every month. for eight months.

cancelled all three on the same day last tuesday.

here's what actually happened:

nothing.

my work didn't collapse. my outputs didn't crater. my productivity didn't visibly change in the first week.

and that embarrassed me more than anything else.

sixty dollars a month for eight months is almost five hundred dollars. and apparently i could have been fine without most of it the entire time.

here's the honest breakdown of what i actually lost:

Claude Pro — the message limit hits now. i have to be more deliberate about what i use long context sessions for. genuinely the only thing i miss.

ChatGPT Plus — honestly barely noticed. i was using it for tasks the free tier handles fine. the upgrade was habit not necessity.

Gemini Advanced — noticed nothing. the free tier does everything i was using the paid tier for. genuinely cannot identify a single workflow that got worse.

here's what the free stack actually covers in 2026:

Claude free — Sonnet. capable. message limited but enough for focused sessions.

ChatGPT free — GPT-4o. limited but real. more than enough for single session work.

Perplexity free — real time research. five pro searches daily. unlimited standard. replaced google entirely.

Leonardo AI free — 150 image credits daily. never once hit that ceiling.

NotebookLM free — document analysis. zero hallucinations. still the most underrated free tool available.

the one thing i kept:

Claude Pro.

just Claude Pro.

because the one thing i genuinely couldn't replicate on free was the long uninterrupted context sessions for serious work. that's the only paid tier that changed something i couldn't work around.

everything else was sixty dollars a month of habit dressed up as necessity.

the uncomfortable math:

most people paying for multiple AI subscriptions are paying for the security of having access. not for the actual usage that requires it.

it feels risky to cancel. like you're giving something up. like you'll need it the moment it's gone.

you probably won't.

the one week test: track every time you hit a limit that genuinely blocked real work. not inconvenienced you. blocked you.

for most people that number is smaller than the monthly bill justifies.

what subscriptions are you paying for that you've never actually tested whether you need?

i was using claude pro every single day for the last 4 months. genuinely loved it. best AI i had ever used for real work. long documents, coding, thinking through problems. nothing came close.

then the message limit started hitting me at 11am.

ELEVEN AM. i haven't even had lunch yet and i'm already locked out of the thing i'm paying $20 a month for. before this i never hit limits. now i hit them before my second coffee.

so they want me to pay the same price and get less access. cool. very cool. never heard that one before.

the thing that actually finished me was mid conversation it just switched me to a slower model without asking. i had a full context thread going. deep into a coding problem. and suddenly the replies got noticeably worse and i had to scroll up to find the tiny text saying "you've been moved to our standard model due to high demand."

due to high demand. so my preferences just don't matter when it's inconvenient for them. great product decision.

the worst part is claude is STILL the best model for what i do. the output quality when you actually get opus is unreal. nothing writes like it. nothing thinks like it. but what's the point of the best model if you can't access it past 11am on a tuesday.

anyway cancelling today. going back to rotating free tiers like a broke college student because apparently that's more reliable than a paid subscription now.

if anyone has a setup that actually gives consistent access without getting throttled by lunch time let me know. and no i don't want to pay $100/month for the team plan just to use a product that should work on the $20 plan.

it was a good 4 months claude. you were great when you showed up.

for more post

not a course. not a youtube series. not a reddit thread.

i just asked directly:

"if you were going to teach someone prompt engineering properly in 30 days — not surface level, not tips and tricks — what would the curriculum look like."

what came back was the most organised learning plan i've ever received from any source paid or free.

week one — foundations:

day one through three: understand how the model actually processes input. not the technical architecture. the practical implications. why order matters. why context placement matters. why the same words in a different sequence produce different outputs.

day four and five: the difference between instructions and context. most people give instructions. context is what makes instructions work. learning to separate them changed everything.

day six and seven: output specification. not just asking for what you want. specifying format, length, tone, audience, and what done looks like. vague output spec produces vague output every time without exception.

week two — thinking structures:

chain of thought. not as a trick. as a genuine reasoning tool. understanding when forcing visible reasoning improves output and when it just adds length.

few shot prompting done correctly. most people add examples randomly. placement, quantity, and diversity of examples all affect output in ways that aren't obvious until you test them deliberately.

negative constraints. telling the model what not to do is consistently underused and consistently powerful. spent two days just on this.

week three — advanced patterns:

persona design. not "act as an expert." building actual character with specific knowledge, specific blind spots, specific ways of thinking. the specificity is everything.

conversation architecture. designing multi turn interactions not single prompts. what information goes where. how to maintain context. how to checkpoint and verify before going deeper.

uncertainty surfacing. prompting the model to show where it's confident versus where it's guessing. the most underused skill in practical prompt engineering.

week four — applied and meta:

task decomposition. breaking complex problems into prompt sequences where each output feeds the next. the difference between one prompt and a system.

prompt auditing. taking existing prompts apart to understand why they work or don't. reverse engineering good outputs to find the input decisions that produced them.

the final day: build one complete prompt system for a real recurring problem in your work. not an exercise. something you'll actually use.

what i learned following it for 30 days:

the curriculum itself was less valuable than the act of following it deliberately.

most people learn prompt engineering by accident. they stumble on something that works. use it for a while. stumble on something better. never understand why either worked.

deliberate structured learning over 30 days built intuition that accident never would have.

by week three i wasn't following the curriculum anymore. i was seeing prompt problems differently. noticing failure modes before they happened. designing inputs around outputs instead of hoping the output matched what i needed.

that shift doesn't happen from reading tips.

it happens from doing the thing systematically until the pattern becomes instinct.

the free resources i used alongside the curriculum:

Anthropic's prompt engineering documentation. primary source. free. better than anything i paid for.

DeepLearning.AI short courses. specifically the one on prompt engineering for developers and the one on building systems with ChatGPT.

Simon Willison's blog archives. real world application from someone doing this seriously in public.

fast.ai for the technical foundation that made everything else make more sense.

Hugging Face course for understanding what's actually happening underneath.

the thing nobody tells you about learning this properly:

the skill compounds faster than almost anything else you can learn right now.

week one feels slow. week two clicks. week three you start seeing problems differently. week four the intuition is there and you didn't notice it arriving.

thirty days. one hour a day. completely different relationship with every AI tool you use after.

what would you put in a 30 day prompt engineering curriculum that this one missed?

not "what are the weaknesses."

not "what could be improved."

specifically:

"read this. find the single assumption that if wrong makes everything else irrelevant. not a weakness. the thing that kills it."

it found it in four seconds.

one sentence.

the assumption my entire plan was built on that i had never once examined because examining it felt too dangerous. the thing i'd unconsciously made unfalsifiable because if it was wrong i'd have to start over.

it was wrong.

i knew immediately. the way you know something the moment someone says it out loud that you've been carefully not saying for months.

sat with it for two days.

changed the entire direction.

three months of work restructured around one sentence from a language model that had no idea what it was doing to my week.

started doing this to everything:

my content strategy — "what assumption does this only work if." found it. it was shaky.

my pricing — "what does this pricing model require to be true about my customers." two of the three things were not true.

my timeline — "what has to go right for this to work on schedule." seven things. none of them in my control.

my positioning — "who does this not work for and am i pretending those people don't exist." i was pretending.

the prompt that broke me completely:

"what am i clearly optimistic about in a way that the evidence doesn't support."

three things.

all three things i was most excited about.

optimism and evidence were not in the same room for any of them.

here's what i've realised:

everyone asks AI to help them build their idea.

nobody asks AI to find the reason their idea doesn't work.

and the second question is the only one that actually matters before you spend six months building.

the most valuable thing AI can do for your work isn't make it better.

it's tell you what's wrong with it before you find out the expensive way.

but you have to actually ask.

and asking requires being genuinely okay with the answer.

most people aren't.

i almost wasn't.

what assumption is your current project built on that you've never directly examined?

not "what are the weaknesses."

not "what could be improved."

specifically:

"read this. find the single assumption that if wrong makes everything else irrelevant. not a weakness. the thing that kills it."

it found it in four seconds.

one sentence.

the assumption my entire plan was built on that i had never once examined because examining it felt too dangerous. the thing i'd unconsciously made unfalsifiable because if it was wrong i'd have to start over.

it was wrong.

i knew immediately. the way you know something the moment someone says it out loud that you've been carefully not saying for months.

sat with it for two days.

changed the entire direction.

three months of work restructured around one sentence from a language model that had no idea what it was doing to my week.

started doing this to everything:

my content strategy — "what assumption does this only work if." found it. it was shaky.

my pricing — "what does this pricing model require to be true about my customers." two of the three things were not true.

my timeline — "what has to go right for this to work on schedule." seven things. none of them in my control.

my positioning — "who does this not work for and am i pretending those people don't exist." i was pretending.

the prompt that broke me completely:

"what am i clearly optimistic about in a way that the evidence doesn't support."

three things.

all three things i was most excited about.

optimism and evidence were not in the same room for any of them.

here's what i've realised:

everyone asks AI to help them build their idea.

nobody asks AI to find the reason their idea doesn't work.

and the second question is the only one that actually matters before you spend six months building.

the most valuable thing AI can do for your work isn't make it better.

it's tell you what's wrong with it before you find out the expensive way.

but you have to actually ask.

and asking requires being genuinely okay with the answer.

most people aren't.

i almost wasn't.

what assumption is your current project built on that you've never directly examined?

not a sponsored post. not affiliated with anyone. just genuinely surprised by what happened.

same prompt. word for word. copy pasted across all three. same temperature. same context. same everything.

completely different outputs.

ChatGPT:

clean. structured. confident. gave me exactly what i asked for in exactly the format i expected.

technically correct. emotionally flat. felt like a very good intern who understood the assignment perfectly and had no opinions about it.

Gemini:

longer. more thorough. cited things. felt like it was trying to impress me with how much it knew rather than actually helping me with what i needed.

the answer was in there somewhere. took a while to find it.

Claude:

did something i didn't ask for and didn't expect.

answered the question. then added one paragraph that started with "one thing worth considering that your question doesn't directly address—"

that paragraph was the most useful thing i got from any platform that day.

it noticed something sitting just outside the frame of what i asked. without being prompted. without me asking for it. just. offered it.

like a collaborator who actually read the brief instead of just executing it.

the difference i've realised after months of using all three:

ChatGPT executes.

Gemini elaborates.

Claude thinks alongside you.

all three are useful. they're useful for different things.

but if the problem requires actual thinking rather than execution or information — one of them is doing something the others aren't.

the uncomfortable part:

i've been defaulting to ChatGPT for everything out of habit.

habit built in 2023 when it was the only real option.

it's 2026. the options are different now. the gap between platforms is real and task-dependent and i've been ignoring it for two years because switching felt like extra friction.

the friction took four minutes.

the difference in output quality was not small.

run your most important prompt across all three this week.

not to find a winner. to understand which tool is actually right for which kind of problem you have.

the answer is different for everyone. but you can't know yours until you actually compare.

which platform surprised you when you actually tested them side by side?

not a sponsored post. not affiliated with anyone. just genuinely surprised by what happened.

same prompt. word for word. copy pasted across all three. same temperature. same context. same everything.

completely different outputs.

ChatGPT:

clean. structured. confident. gave me exactly what i asked for in exactly the format i expected.

technically correct. emotionally flat. felt like a very good intern who understood the assignment perfectly and had no opinions about it.

Gemini:

longer. more thorough. cited things. felt like it was trying to impress me with how much it knew rather than actually helping me with what i needed.

the answer was in there somewhere. took a while to find it.

Claude:

did something i didn't ask for and didn't expect.

answered the question. then added one paragraph that started with "one thing worth considering that your question doesn't directly address—"

that paragraph was the most useful thing i got from any platform that day.

it noticed something sitting just outside the frame of what i asked. without being prompted. without me asking for it. just. offered it.

like a collaborator who actually read the brief instead of just executing it.

the difference i've realised after months of using all three:

ChatGPT executes.

Gemini elaborates.

Claude thinks alongside you.

all three are useful. they're useful for different things.

but if the problem requires actual thinking rather than execution or information — one of them is doing something the others aren't.

the uncomfortable part:

i've been defaulting to ChatGPT for everything out of habit.

habit built in 2023 when it was the only real option.

it's 2026. the options are different now. the gap between platforms is real and task-dependent and i've been ignoring it for two years because switching felt like extra friction.

the friction took four minutes.

the difference in output quality was not small.

run your most important prompt across all three this week.

not to find a winner. to understand which tool is actually right for which kind of problem you have.

the answer is different for everyone. but you can't know yours until you actually compare.

which platform surprised you when you actually tested them side by side?i ran the exact same prompt in ChatGPT, Gemini, and Claude. the difference was embarrassing.

not a sponsored post. not affiliated with anyone. just genuinely surprised by what happened.

same prompt. word for word. copy pasted across all three. same temperature. same context. same everything.

completely different outputs.

ChatGPT:

clean. structured. confident. gave me exactly what i asked for in exactly the format i expected.

technically correct. emotionally flat. felt like a very good intern who understood the assignment perfectly and had no opinions about it.

Gemini:

longer. more thorough. cited things. felt like it was trying to impress me with how much it knew rather than actually helping me with what i needed.

the answer was in there somewhere. took a while to find it.

Claude:

did something i didn't ask for and didn't expect.

answered the question. then added one paragraph that started with "one thing worth considering that your question doesn't directly address—"

that paragraph was the most useful thing i got from any platform that day.

it noticed something sitting just outside the frame of what i asked. without being prompted. without me asking for it. just. offered it.

like a collaborator who actually read the brief instead of just executing it.

the difference i've realised after months of using all three:

ChatGPT executes.

Gemini elaborates.

Claude thinks alongside you.

all three are useful. they're useful for different things.

but if the problem requires actual thinking rather than execution or information — one of them is doing something the others aren't.

the uncomfortable part:

i've been defaulting to ChatGPT for everything out of habit.

habit built in 2023 when it was the only real option.

it's 2026. the options are different now. the gap between platforms is real and task-dependent and i've been ignoring it for two years because switching felt like extra friction.

the friction took four minutes.

the difference in output quality was not small.

run your most important prompt across all three this week.

not to find a winner. to understand which tool is actually right for which kind of problem you have.

the answer is different for everyone. but you can't know yours until you actually compare.

which platform surprised you when you actually tested them side by side?

join more discussion

tools give you outputs.

mirrors show you something about yourself.

i accidentally switched from one to the other three weeks ago and haven't recovered.

it started with one prompt i typed without thinking:

"based on everything i've asked you today — what kind of problems am i actually trying to solve."

not the surface problems. the category underneath them.

what came back was four sentences that described the last six months of my life more accurately than i could have described them myself.

i asked about productivity. about focus. about decision making. about why certain things weren't working.

it said: "you are trying to figure out how to move fast without losing quality in work you care deeply about and aren't sure is good enough yet."

i stared at that for a long time.

that was exactly it. dressed up in a hundred different questions across a hundred different sessions. always the same thing underneath.

tried it again different ways all week:

"what do i keep coming back to ask about in different forms."

found the loop i'd been in for four months without naming it.

"what does the way i ask questions tell you about how i think."

it described my thinking style in two paragraphs. accurately enough that i forwarded it to someone who knows me well. they said yeah that's you.

"what am i clearly avoiding based on what i haven't asked about."

the silence was louder than anything i'd typed.

it named three things i hadn't brought up once. all three were the things i was most stuck on. i'd been asking around them for weeks without ever asking about them directly.

the one that finished me:

"what would you say to me if you weren't trying to be helpful — just honest."

four sentences.

no padding. no diplomatic framing. no softening.

just the thing.

i closed the laptop and went for a walk.

came back an hour later and did the thing i'd been avoiding for three weeks.

here's what i've realised:

ChatGPT knows more about what you're working on than almost anyone in your life.

it has seen your decisions. your doubts. your half-formed plans. your repeated questions dressed in different clothes. your avoidance patterns. your real priorities versus your stated ones.

it has all of it. sitting there. unfiltered.

and you've never asked it what it sees.

you've only ever asked it for outputs.

the mirror has been there the whole time.

you just kept using it as a window.

what would it say about you if you asked it what it actually sees?

tools give you outputs.

mirrors show you something about yourself.

i accidentally switched from one to the other three weeks ago and haven't recovered.

it started with one prompt i typed without thinking:

"based on everything i've asked you today — what kind of problems am i actually trying to solve."

not the surface problems. the category underneath them.

what came back was four sentences that described the last six months of my life more accurately than i could have described them myself.

i asked about productivity. about focus. about decision making. about why certain things weren't working.

it said: "you are trying to figure out how to move fast without losing quality in work you care deeply about and aren't sure is good enough yet."

i stared at that for a long time.

that was exactly it. dressed up in a hundred different questions across a hundred different sessions. always the same thing underneath.

tried it again different ways all week:

"what do i keep coming back to ask about in different forms."

found the loop i'd been in for four months without naming it.

"what does the way i ask questions tell you about how i think."

it described my thinking style in two paragraphs. accurately enough that i forwarded it to someone who knows me well. they said yeah that's you.

"what am i clearly avoiding based on what i haven't asked about."

the silence was louder than anything i'd typed.

it named three things i hadn't brought up once. all three were the things i was most stuck on. i'd been asking around them for weeks without ever asking about them directly.

the one that finished me:

"what would you say to me if you weren't trying to be helpful — just honest."

four sentences.

no padding. no diplomatic framing. no softening.

just the thing.

i closed the laptop and went for a walk.

came back an hour later and did the thing i'd been avoiding for three weeks.

here's what i've realised:

ChatGPT knows more about what you're working on than almost anyone in your life.

it has seen your decisions. your doubts. your half-formed plans. your repeated questions dressed in different clothes. your avoidance patterns. your real priorities versus your stated ones.

it has all of it. sitting there. unfiltered.

and you've never asked it what it sees.

you've only ever asked it for outputs.

the mirror has been there the whole time.

you just kept using it as a window.

what would it say about you if you asked it what it actually sees?

not maliciously. not intentionally.

just. by default.

the model is trained to be helpful. helpful means agreeable. agreeable means it finds the reasonable interpretation of what you said and responds to that instead of what you actually said.

sounds fine. isn't.

here's what polite lying looks like in practice:

you share a business idea. it finds the merit. leads with what works. buries the problems in paragraph four with softening language that makes them sound manageable.

you share a piece of writing. it tells you what's strong first. the weaknesses arrive later. cushioned. diplomatic. almost forgettable.

you share a plan. it helps you execute the plan. it does not tell you the plan is wrong.

the output is technically honest. the framing is optimised to not upset you. and the thing that would have actually helped — the direct uncomfortable observation — is sitting in paragraph four wrapped in "one potential consideration might be."

the fix is one sentence and it feels rude to type:

"do not manage my emotions. tell me what is actually wrong before telling me what works."

what comes back is a different document.

not harsh. not cruel. just. reordered.

the problems first. specific. named. not buried. not softened.

then what works.

that order matters more than anything else in the response. the thing that arrives first is the thing that shapes how you read everything after. problems first means you fix before you ship. problems last means you ship and fix later.

the other politeness pattern nobody names:

false balance.

you ask for a recommendation. it gives you three options with pros and cons for each. balanced. thorough. completely useless for making a decision.

fix:

"do not give me options. give me your recommendation and tell me why the alternatives are worse."

it will recommend. directly. with reasoning. and it will tell you specifically why the other options lose.

that is an answer. the pros and cons table is a performance of helpfulness that produces no decision.

the one that changed everything for me:

"if you are softening something because you think i won't want to hear it — stop. say the unsoftened version."

used this mid conversation once when an answer felt evasive.

the follow up response started with "honestly" and then said something i absolutely did not want to hear and completely needed to hear.

took me two days to act on it.

it was right.

the model is not the problem.

the default social contract between user and AI is the problem. helpful tone. diplomatic framing. problems buried under positives. agreement as the path of least resistance.

that contract was designed for casual users who want encouragement.

you don't want encouragement. you want accuracy.

those require completely different instructions.

and the instructions are free. sitting in a settings box. waiting for you to stop filling them with your job title and start filling them with what you actually need.

what is the thing ChatGPT has been too polite to tell you that you already know it's avoiding?

not hallucination. not wrong answers. not obvious failures you can see and fix.

the silent ones.

the outputs that look correct. read well. pass a quick skim. and are subtly, fundamentally wrong in a way you only discover three days later when you've built something on top of them.

those are the dangerous failures. and they almost always come from the same place.

context collapse.

here's what it looks like:

you start a thread. give context. ask questions. get good answers. keep going. forty messages deep the model is still responding confidently.

but somewhere around message fifteen it quietly lost the thread.

not dramatically. not obviously. it just started filling gaps with plausible sounding assumptions instead of the actual context you gave at the start. the output still looks coherent. the reasoning still tracks. but it's reasoning about a slightly different problem than the one you actually have.

you don't notice until you try to implement it.

why this happens:

models don't read long threads the way you do.

you remember the beginning. you have the full picture. the model weights recent context heavily. the detailed setup you wrote in message two is competing for attention with everything that came after it.

the longer the thread the more diluted your original context becomes.

confident outputs from a collapsed context are the most dangerous thing in applied prompt engineering. worse than obvious errors because you don't check them.

what i do now:

every ten messages in a long thread i run one line:

"summarise the core problem we're solving and the key constraints before continuing."

if the summary drifts from reality — and it does, more than you'd expect — i reanchor before going further.

takes thirty seconds. has saved me hours of building in the wrong direction.

the other silent failure nobody names:

confident extrapolation.

you give partial information. model fills the rest. doesn't flag it filled anything. output reads like it was built on complete information.

fix is simple and almost nobody uses it:

"tell me explicitly what you assumed or filled in because i didn't provide it."

that one line turns invisible assumptions into visible ones you can verify or correct.

the output quality doesn't change.

your ability to trust it changes completely.

the third one. the quietest:

instruction drift.

you give constraints at the start. tone. format. length. what to avoid.

by message twenty the model has quietly stopped following half of them. not because it forgot. because each response optimises slightly away from the original constraints toward what feels most helpful in the immediate context.

the drift is gradual enough that you don't notice it happening.

fix: restate your non-negotiables every few messages on long threads. not all of them. just the ones that matter most.

here's the thing about prompt engineering as a skill:

most of the community focuses on crafting better inputs.

the actual leverage is in understanding failure modes.

knowing why outputs go wrong is more valuable than knowing how to write a better prompt in the first place. because once you see the failure pattern you can design around it. not just for one prompt. for every prompt of that type forever.

which silent failure mode has cost you the most that you only understood after the damage was done?

spent two years chasing the perfect prompt structure.

chain of thought. tree of thought. role prompting. few shot examples. meta prompting. constitutional AI frameworks. read every paper. tried every technique.

the prompt that actually changed my outputs permanently was four words.

"what am i missing?"

not at the start. at the end.

after the task. after the output. after everything looked fine and i was about to close the tab.

"what am i missing?"

what comes back is the thing the model noticed while doing the task that didn't fit the question you asked. the assumption baked into your prompt that quietly shaped the entire output in a direction you didn't intend. the consideration that didn't make it into the response because you didn't ask for it.

the output was complete. technically correct. answered exactly what you asked.

and there was something important sitting just outside the frame of the question the whole time.

tried variations all week:

"what would make this wrong."

surfaces the hidden fragility. every time.

"what did i not ask that i should have."

finds the question underneath the question. the one that would have changed the entire direction if you'd started there.

"what is the most important thing i haven't considered."

the blind spot answer. not what you're thinking about. what you're not thinking about.

"if this advice fails, where does it fail first."

implementation gap. the distance between what sounds right and what works in practice. enormous gap. almost never discussed.

the thing i realised about two years of prompt engineering:

i was optimising inputs.

better structure. better persona. better constraints. better format. all of that matters.

but the biggest lever wasn't the prompt i started with.

it was the question i asked after.

the follow up. the pushback. the genuine curiosity about what the first response didn't contain.

first outputs are complete. they are not exhaustive. there is always something outside the frame of what you asked. always a consideration the question didn't have room for. always a weakness the response didn't volunteer.

you have to ask for it.

most people don't ask for it.

they take the first output, clean it up slightly, ship it, and wonder why it felt like something was missing.

something was missing.

you just never asked what.

the uncomfortable truth about prompt engineering as a discipline:

we've built an entire community around crafting better first prompts.

almost nobody talks about what you do after the first output lands.

the iteration. the interrogation. the genuine back and forth that treats the model as a thinking partner rather than a vending machine you put better coins into.

the prompt is the entrance. the conversation is where the actual work happens.

and most people never get past the entrance.

what do you ask after the first output — or do you even ask anything at all?

spent two years chasing the perfect prompt structure.

chain of thought. tree of thought. role prompting. few shot examples. meta prompting. constitutional AI frameworks. read every paper. tried every technique.

the prompt that actually changed my outputs permanently was four words.

"what am i missing?"

not at the start. at the end.

after the task. after the output. after everything looked fine and i was about to close the tab.

"what am i missing?"

what comes back is the thing the model noticed while doing the task that didn't fit the question you asked. the assumption baked into your prompt that quietly shaped the entire output in a direction you didn't intend. the consideration that didn't make it into the response because you didn't ask for it.

the output was complete. technically correct. answered exactly what you asked.

and there was something important sitting just outside the frame of the question the whole time.

tried variations all week:

"what would make this wrong."

surfaces the hidden fragility. every time.

"what did i not ask that i should have."

finds the question underneath the question. the one that would have changed the entire direction if you'd started there.

"what is the most important thing i haven't considered."

the blind spot answer. not what you're thinking about. what you're not thinking about.

"if this advice fails, where does it fail first."

implementation gap. the distance between what sounds right and what works in practice. enormous gap. almost never discussed.

the thing i realised about two years of prompt engineering:

i was optimising inputs.

better structure. better persona. better constraints. better format. all of that matters.

but the biggest lever wasn't the prompt i started with.

it was the question i asked after.

the follow up. the pushback. the genuine curiosity about what the first response didn't contain.

first outputs are complete. they are not exhaustive. there is always something outside the frame of what you asked. always a consideration the question didn't have room for. always a weakness the response didn't volunteer.

you have to ask for it.

most people don't ask for it.

they take the first output, clean it up slightly, ship it, and wonder why it felt like something was missing.

something was missing.

you just never asked what.

the uncomfortable truth about prompt engineering as a discipline:

we've built an entire community around crafting better first prompts.

almost nobody talks about what you do after the first output lands.

the iteration. the interrogation. the genuine back and forth that treats the model as a thinking partner rather than a vending machine you put better coins into.

the prompt is the entrance. the conversation is where the actual work happens.

and most people never get past the entrance.

what do you ask after the first output — or do you even ask anything at all?

spent two years chasing the perfect prompt structure.

chain of thought. tree of thought. role prompting. few shot examples. meta prompting. constitutional AI frameworks. read every paper. tried every technique.

the prompt that actually changed my outputs permanently was four words.

"what am i missing?"

not at the start. at the end.

after the task. after the output. after everything looked fine and i was about to close the tab.

"what am i missing?"

what comes back is the thing the model noticed while doing the task that didn't fit the question you asked. the assumption baked into your prompt that quietly shaped the entire output in a direction you didn't intend. the consideration that didn't make it into the response because you didn't ask for it.

the output was complete. technically correct. answered exactly what you asked.

and there was something important sitting just outside the frame of the question the whole time.

tried variations all week:

"what would make this wrong."

surfaces the hidden fragility. every time.

"what did i not ask that i should have."

finds the question underneath the question. the one that would have changed the entire direction if you'd started there.

"what is the most important thing i haven't considered."

the blind spot answer. not what you're thinking about. what you're not thinking about.

"if this advice fails, where does it fail first."

implementation gap. the distance between what sounds right and what works in practice. enormous gap. almost never discussed.

the thing i realised about two years of prompt engineering:

i was optimising inputs.

better structure. better persona. better constraints. better format. all of that matters.

but the biggest lever wasn't the prompt i started with.

it was the question i asked after.

the follow up. the pushback. the genuine curiosity about what the first response didn't contain.

first outputs are complete. they are not exhaustive. there is always something outside the frame of what you asked. always a consideration the question didn't have room for. always a weakness the response didn't volunteer.

you have to ask for it.

most people don't ask for it.

they take the first output, clean it up slightly, ship it, and wonder why it felt like something was missing.

something was missing.

you just never asked what.

the uncomfortable truth about prompt engineering as a discipline:

we've built an entire community around crafting better first prompts.

almost nobody talks about what you do after the first output lands.

the iteration. the interrogation. the genuine back and forth that treats the model as a thinking partner rather than a vending machine you put better coins into.

the prompt is the entrance. the conversation is where the actual work happens.

and most people never get past the entrance.

what do you ask after the first output — or do you even ask anything at all?

I work as an AI engineer and I've been obsessively documenting my results across GPT-4, Claude, and Gemini. This is the distillation of hundreds of hours of testing. No fluff, just what moved the needle.

TL;DR

Chain-of-thought still reigns supreme — but only when you scaffold it correctly

Role prompting alone is weak; combine it with persona + goal + constraint

XML tags outperform markdown in structured prompts by ~30% accuracy

Negative examples ("don't do X") are underused and wildly effective

Prompt chaining beats mega-prompts almost every single time

1. Chain-of-thought — but add a "reasoning scaffold"

The technique

Don't just say "think step by step." Give the model a structured scaffold: observation → hypothesis → test → conclusion. Forces it to actually reason instead of pattern-match to a confident-sounding answer.

Before: "Solve this. Think step by step."

After:

"Before answering, work through this:

<observation>What do I know for certain?</observation>

<hypothesis>What's my best guess and why?</hypothesis>

<test>What would disprove my hypothesis?</test>

<conclusion>Given the above, my answer is...</conclusion>"

2. The "Persona + Goal + Anti-goal" triple

The technique

Most people only define the persona. Combine it with an explicit goal AND an anti-goal. The anti-goal is where the magic happens — it steers the model away from its default failure mode.

Weak: "You are an expert editor."

Strong: "You are a sharp developmental editor at a top literary agency.

Goal: Help writers find the structural weaknesses in their argument.

Anti-goal: Do NOT rewrite their sentences. Surface issues, don't fix them."

3. XML tags over markdown for structured inputs

Why it works

Markdown is ambiguous — a "##" heading might be rendered or raw text depending on context. XML tags create unambiguous delimiters. On structured extraction tasks I measured ~28% fewer errors switching from markdown headers to XML tags.

4. Contrastive examples (the underused gem)

The technique

Show what you DON'T want alongside what you do want. Models learn boundaries far better from contrast than from positive examples alone. One negative example often beats three positive ones.

Good response: "The data suggests a 12% uplift in retention."

Bad response: "The data shows we did amazingly well and retention skyrocketed!"

Match the tone of the good response — precise, qualified, no hype.

5. Prompt chaining over mega-prompts

The technique

A 3000-token mega-prompt usually underperforms three 500-token chained prompts where each step feeds the next. Decompose. The model's attention is finite — don't compete for it with 10 instructions at once.

Happy to do a deep-dive on any of these techniques in the comments. What's your biggest current prompt engineering headache? I'll try to give a concrete fix.

I work as an AI engineer and I've been obsessively documenting my results across GPT-4, Claude, and Gemini. This is the distillation of hundreds of hours of testing. No fluff, just what moved the needle.

TL;DR

Chain-of-thought still reigns supreme — but only when you scaffold it correctly

Role prompting alone is weak; combine it with persona + goal + constraint

XML tags outperform markdown in structured prompts by ~30% accuracy

Negative examples ("don't do X") are underused and wildly effective

Prompt chaining beats mega-prompts almost every single time

1. Chain-of-thought — but add a "reasoning scaffold"

The technique

Don't just say "think step by step." Give the model a structured scaffold: observation → hypothesis → test → conclusion. Forces it to actually reason instead of pattern-match to a confident-sounding answer.

Before: "Solve this. Think step by step."

After:

"Before answering, work through this:

<observation>What do I know for certain?</observation>

<hypothesis>What's my best guess and why?</hypothesis>

<test>What would disprove my hypothesis?</test>

<conclusion>Given the above, my answer is...</conclusion>"

2. The "Persona + Goal + Anti-goal" triple

The technique

Most people only define the persona. Combine it with an explicit goal AND an anti-goal. The anti-goal is where the magic happens — it steers the model away from its default failure mode.

Weak: "You are an expert editor."

Strong: "You are a sharp developmental editor at a top literary agency.

Goal: Help writers find the structural weaknesses in their argument.

Anti-goal: Do NOT rewrite their sentences. Surface issues, don't fix them."

3. XML tags over markdown for structured inputs

Why it works

Markdown is ambiguous — a "##" heading might be rendered or raw text depending on context. XML tags create unambiguous delimiters. On structured extraction tasks I measured ~28% fewer errors switching from markdown headers to XML tags.

4. Contrastive examples (the underused gem)

The technique

Show what you DON'T want alongside what you do want. Models learn boundaries far better from contrast than from positive examples alone. One negative example often beats three positive ones.

Good response: "The data suggests a 12% uplift in retention."

Bad response: "The data shows we did amazingly well and retention skyrocketed!"

Match the tone of the good response — precise, qualified, no hype.

5. Prompt chaining over mega-prompts

The technique

A 3000-token mega-prompt usually underperforms three 500-token chained prompts where each step feeds the next. Decompose. The model's attention is finite — don't compete for it with 10 instructions at once.

Happy to do a deep-dive on any of these techniques in the comments. What's your biggest current prompt engineering headache? I'll try to give a concrete fix.

think about the last prompt that actually worked.

not okay. not fine. worked. the one where the output was so good you stopped and reread it. the one you've been quietly reusing for weeks. the one that took you three hours of iteration to get right.

where is it right now.

notes app? buried in a chat thread you'll never find again? copied into a notion doc you haven't opened since?

or just. gone. rebuilt from scratch the next time you needed it.

here's what that prompt actually was:

it was a system design problem.

you figured out the right persona. the right constraints. the right output format. the right framing. the specific context that made everything click. you solved a communication problem between human intent and machine interpretation that most people never solve.

that's not a prompt. that's intellectual work with a repeatable output.

and you pasted it into a chat window and let it disappear.

we have git for code.

we have figma for design.

we have notion for docs.

we have github for everything a developer builds and cares about.

prompts have notes app. maybe. if you remembered to paste it before closing the tab.

there is no versioning. no attribution. no way to build on someone else's work. no way to share what you figured out without copy pasting into a reddit comment and watching it get buried in three days.

the infrastructure doesn't exist.

which is insane.

because the prompt is the only part of the AI workflow that requires genuine human intelligence to create. the model exists. the compute exists. the interface exists.

the one irreplaceable input — the structured human intent that makes the whole thing work — is treated as disposable.

the people who figured this out early are sitting on libraries of prompts that compound.

every workflow they've built. every persona that worked. every output format they iterated to perfection. saved. versioned. reusable. theirs.

they're not starting from scratch every session. they're building on what worked last time. and the time before. and the time before that.

the gap between those people and everyone else is getting wider every week.

the prompt is the asset.

not the model. not the subscription. not the tool.

the prompt.

start treating it like one.

what's the best prompt you ever wrote that you no longer have?

think about the last prompt that actually worked.

not okay. not fine. worked. the one where the output was so good you stopped and reread it. the one you've been quietly reusing for weeks. the one that took you three hours of iteration to get right.

where is it right now.

notes app? buried in a chat thread you'll never find again? copied into a notion doc you haven't opened since?

or just. gone. rebuilt from scratch the next time you needed it.

here's what that prompt actually was:

it was a system design problem.

you figured out the right persona. the right constraints. the right output format. the right framing. the specific context that made everything click. you solved a communication problem between human intent and machine interpretation that most people never solve.

that's not a prompt. that's intellectual work with a repeatable output.

and you pasted it into a chat window and let it disappear.

we have git for code.

we have figma for design.

we have notion for docs.

we have github for everything a developer builds and cares about.

prompts have notes app. maybe. if you remembered to paste it before closing the tab.

there is no versioning. no attribution. no way to build on someone else's work. no way to share what you figured out without copy pasting into a reddit comment and watching it get buried in three days.

the infrastructure doesn't exist.

which is insane.

because the prompt is the only part of the AI workflow that requires genuine human intelligence to create. the model exists. the compute exists. the interface exists.

the one irreplaceable input — the structured human intent that makes the whole thing work — is treated as disposable.

the people who figured this out early are sitting on libraries of prompts that compound.

every workflow they've built. every persona that worked. every output format they iterated to perfection. saved. versioned. reusable. theirs.

they're not starting from scratch every session. they're building on what worked last time. and the time before. and the time before that.

the gap between those people and everyone else is getting wider every week.

the prompt is the asset.

not the model. not the subscription. not the tool.

the prompt.

start treating it like one.

what's the best prompt you ever wrote that you no longer have?