A junior dev asked me something recently that actually made me think. He said: "As a software developer or vibe coder, while you're building, what do you usually look out for before moving to production? If you can give me something like a framework or blueprint, it would really help me while I build so I can avoid basic mistakes."
My first answer was simple: understand the basics and fundamentals of the programming language you're using. Then the tools and libraries on top of that. Even if you are a vibe coder, this still applies to you. You can't debug what you don't understand. and you can't secure what you don't know exists.
But the question deserved more than that. So here's the full answer.
First, your code
Before you do anything else, look at your code like a stranger would.
