@alanonai: Here's some good news if you're building software with AI: you do not need to be an engineer to design your system well. The part you're afraid of isn't actually the part that's yours. Most people use their AI like an architect. You describe what you want, it decides how everything fits together, and it hands back finished code with a dozen decisions baked inside that you never saw. The problem isn't that the AI is a bad designer. It's that it's designing for a project it knows nothing about. So stop treating it like an architect, and start treating it like an analyst. An analyst doesn't decide for you. It lays out your options, what each one costs, what each one buys you. Then you make the call, because you're the one who actually knows what you're building. And here's the thing that should take the pressure off. Most design decisions are product decisions wearing engineering costumes. "How should the database handle two people editing at once" sounds technical. But the real question underneath is just: when two of your users edit the same thing, what do you want to happen? You can answer that. You don't need to know a thing about how it works under the hood. Reading a menu is a much smaller skill than cooking. You don't have to generate the options. You just have to recognize the one that fits you. Link to article in comments. #ai #vibecoding #coding #programming #systemdesign

Alan on AI

Open In TikTok:

Region: US

Wednesday 17 June 2026 17:47:58 GMT