The Angry Prompt That Built a Real Product

You are supposed to be the smartest AI model in the world. Stop wasting my time with this and make me something useful that actually solves my problem.

That is the exact prompt Brian typed into his AI. Not a carefully constructed instruction. Not a list of requirements. Just frustration, typed out and sent.

Then he walked away. Went swimming with his son. Forgot about it entirely.

When he came back, there was a link waiting. He clicked it. A working application, rough and unfinished, but real. About six hours later, that angry little prototype had become HeyMotion.

Anger Cut Through the Noise

Most prompts are polite. They're careful. They describe what you want in measured, structured language because that's what every guide tells you to do.

But Brian's angry prompt did something different. It stripped away the hedging and the step-by-step instructions and left only the actual problem: make me something useful that solves this.

No scaffolding. No "first do this, then do that." Just the raw ask.

(Turns out the smartest model in the world responds pretty well to being called out.)

The result wasn't polished. It was rough, unfinished, clearly a first draft. But it was working, and it was aimed at the real problem instead of a description of the problem.

Walking Away Was Part of the Process

The other detail worth noticing is what Brian did after he hit send. He didn't hover. He didn't refine the prompt five more times. He left.

That gap, the time spent swimming instead of watching a cursor blink, gave the AI room to actually work through the problem instead of being interrupted every ninety seconds with a tweak.

The prompt that works isn't the one you polish, it's the one that finally tells the AI what you actually need.

This experience reshaped how Brian thinks about what AI is good for. Not as a tool you micromanage through every step, but as something you can hand a real problem to and let run.

That shift, from instructing the steps to naming the problem, is the whole story behind how HeyMotion came to exist. The full account of that six hours, what the first version actually looked like, and how frustration turned into a working process is worth watching in full.

Go watch it. Then take stock of the next prompt you're about to write. Are you describing steps, or are you actually telling the AI what problem you need solved?