Solo builder feels impostor syndrome after vibe-coding a SaaS app
A systems administrator who has worked at the same MSP company for six years, with beginner-level C/C++ and Python skills and a French master's degree in software/network project management and cloud , decided to build a personal SaaS product. After researching forums and experience reports, they identified a real problem in their field and company, which colleagues confirmed and which they found also existed elsewhere. They studied different s and tech stacks, then planned and prepared the project the way they had learned in school before starting to code using VS Code paired with Claude Code.
Fable 5 launched around the same time, which helped significantly during development. Building feature by feature, testing repeatedly and iterating through failures, they finished the app in about two months. Aware of the common pitfalls of vibe coding, they paid particular attention to typical flaws such as security issues, , chaotic , dead code, and .
The result, they say, is a functional, secure app with no .
Key points
- A six-year systems administrator picked a SaaS idea based on a real problem observed in their industry
- Studied multiple s and tech stacks before starting to code
- Built with VS Code and Claude Code; the Fable 5 release helped during development
- Deliberately guarded against common vibe-coding pitfalls like and
- Finished a working, tested app in about two months