AI Built a URL Shortener in Seconds. Would You Ship It? A developer compared an AI-generated URL shortener prototype against a production-grade implementation, showing that the vibe-coded version stores links in an in-memory Map, skips URL validation, uses Math.random for short codes without collision handling, and ignores abuse prevention. The rewrite adds SQLite persistence, HTTP/HTTPS-only input validation, and cryptographically random identifiers, arguing that working code is not the same as reliable software. Vibe Coding vs. Real Programming — One Real Project, Two Very Different Approaches. Imagine building your own version of Bitly. A user pastes a long URL, clicks a button, and gets a short link. For example: Original URL: https://example.com/blog/how-to-learn-programming-in-2026 Short URL: https://short.ly/a8f92b Simple, right? Now imagine opening an AI coding assistant and typing: "Build me a URL shortener using Node.js and Express. Users should be able to submit a URL and receive a shortened link. When someone visits the shortened link, redirect them to the original URL." A few seconds later, AI generates the code. You run it. It works. Congratulations You've built a URL shortener. But here's a question: Would you actually deploy that code for real users? This is where the difference between Vibe Coding and Programming becomes interesting. Let's build the same application twice, compare the code, and discover what separates a working prototype from reliable software. Vibe Coding is an AI-driven approach to software development in which you describe what you want using natural language and let AI generate much of the implementation. Instead of manually writing every function, you focus on communicating your ideas. "Build me a login page." "Connect this application to a database." "Add a payment system." "Fix this error." "Make the dashboard responsive." AI handles much of the code generation. You test the result, give feedback, and ask AI to improve it. It's an exciting way to turn ideas into working prototypes, especially for beginners. However, there is an important distinction between using AI to generate code and blindly accepting code you don't understand. The latter is where problems begin. Let's imagine a quick AI-generated prototype. A simplified implementation might look like this: js const links = new Map