Choose a Simple Stack

Pick boring tools that are supported and have current documentation and examples. You still need to test the generated code. Choose one front end, one place to store data and one place to host it, and don't change them mid-build.

Questions to answer

• Does the tool you picked have a free tier for a prototype?
• Can you deploy with one command or one click?
• Is there good documentation you can paste into the prompt?
• Can you export your code if you leave the tool?

Worked example

Sam picks a common web framework, a hosted database with a free tier and one-click hosting. He pastes the framework's documentation into the prompt when the tool gets something wrong. Because the tools are well documented, the first version needs few fixes, and he still tests every one.

Common mistakes

• Picking a trendy tool nobody has written about.
• Switching frameworks halfway through.
• Choosing hosting you can't afford once people use it.

Exercise

Choose one tool for each of front end, data and hosting. Check the free tier limits and write them down.