The AI answered like an engineer. That was the problem.

Recently I was talking with someone who had used Guide me to get started. They had done the hard part well. They had named their user and they knew what they were trying to make.

Then they asked the obvious next question. How do I actually build this?

They put it to the AI and the AI did what AI does. Did they want Python or Node? How did they want to handle sockets? What about REST and APIs? All fair questions if you are an engineer. They are not an engineer. Within a few minutes a good idea had turned into a wall of jargon and they felt stuck.

None of that was the next question.

When you ask an AI how to build something, it answers like an engineer, because that is the shape of the question. But "how do I build it" quietly skips the question that comes first. Does this need building at all?

That is idea 2.2.2 in the framework. Buy versus build is a strategy choice, not an engineering one.

Think about it this way. If what you need is a place to publish your writing, you do not build a blogging application. There are already brilliant blogging platforms and most are cheap or free. Building your own would be like milling your own flour to bake a pie. The flour is not where the pie gets good. The filling is. Your effort belongs in the content and the strategy, not in rebuilding something that already exists and works.

So we did not talk about Python or Node. We talked about what they actually understood. Their users. Their content. The one thing that would make what they make theirs. Everything else, the parts they did not understand and did not enjoy, is a candidate to buy or reuse.

Then came the real test. Could they put their name on it? That is idea 3.3.3. Would you stand behind this build in front of real users and mean it?

This is where trust comes in and trust turned out to be simple. You can only trust the part you know you can do well. If you build the thing you do not understand, you cannot stand behind it, because you cannot tell whether it is right. Build the one part that is truly yours and you can put your name on it. Buy the rest and trust the people who already do it well.

We did not set out to, but that conversation walked the three corners of the framework. Name the user, 1.1.1. Build only what is yours, 2.2.2. Put your name on it, 3.3.3. One idea from Shape, one from Build, one from Launch. A straight line through the middle.

The confusion at the start was never a sign they were not technical enough. It was a sign they were answering the wrong question. Move the question from which technology to where the value lives and what you can stand behind. Then it gets simple again.

That is the whole point of building with AI. Not to build everything, but to build the part that is yours and trust what you make.

Thoughts?