Low-Code or Full-Code: Where Should a Beginner Start?

I already wrote about low-code vs full-code in production. This one is different. It’s about where to start. Because the answer isn’t the same for everyone. It depends on where you’re coming from. Already have some notions? Go full-code. 100% If you studied programming, did some coding at school or played with it before, go straight to full-code. Same if you want to learn the details: how things work under the hood, why code is written a certain way, how to structure a real project. Full-code is where you learn that. You already know the basics, so a visual tool would only slow you down. Pick something like React and build. Never touched code? Start with low-code Opening a code editor for the first time is overwhelming. Files everywhere, syntax errors, tools to install, words you’ve never heard. A lot of people quit right there. Low-code removes most of that. You don’t see as much code, but you still see the ideas. And the ideas are what matter. The same ideas, just easier to see Variables: a named box holding a value, that you can click and check Loops: a “for each” block wrapped around the steps it repeats Conditions: an if/else block with two clear paths Fetching data: a query step, with its result right in front of you Returning data: the response your API sends back, field by field API calls: a request to another service, with what goes in and comes out Learn them visually. They’re the same in code. Take an API. In low-code you literally see it: an endpoint, the inputs it takes, the steps it runs and what it returns. The first time, that’s much easier to grasp than reading it in a file. Visual learning is real. For a lot of people, seeing it is how it clicks. When to switch to full-code Low-code isn’t a trap. Once those ideas feel normal, you can move to code, and you’ll be surprised how much you already know. You’re ready for full-code when: [x] you know what a variable, a loop and a condition do [x] you know what an API is and how data comes back [x] you can fix a broken workflow on your own [x] you want more control than the tool gives you [x] you’re curious how it works underneath With AI tools now, the jump is smaller than ever. Just make sure you understand what the AI writes. (I talk about that in low-code or vibe coding.) My honest answer Studied code, or want to learn the details? Full-code, 100%. Never touched code? Low-code first. Learn the ideas visually, then move to code. Either way, the goal is the same: understand what you’re building. The tool is just how you get there. (If you’re choosing a frontend tool, see WeWeb vs React.) I first posted this on my blog, where it’s also in French and Arabic. Curious how others see it: what did you start with, and would you pick the same again?