DEV Community

Cover image for Low-Code or Full-Code: Where Should a Beginner Start?
Abdelmoula Bilel
Abdelmoula Bilel

Posted on Edited on Originally published at bilelabdelmoula.dev

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

I already wrote about low-code vs full-code in production. This post is about something else: which one to start with when you’re learning. The answer depends on your background.

If you already know some code, go full-code

If you studied programming, coded a bit at school or tried it before, go straight to full-code. Same if you want to learn the details, like how things work under the hood, why code is written a certain way and how to structure a real project.

You already have the basics, so a visual tool would mostly slow you down. Pick something like React and start building.

If you’ve never touched code, start with low-code

Opening a code editor for the first time can be a lot: files everywhere, syntax errors, tools to install and words you don’t know yet. Many people give up at that point.

Low-code removes most of that. You see a lot less code, but you still work with the same concepts:

Concepts you learn in low-code

  • Variables: a named box holding a value, that you can click and check
  • Loops: a “for each” block around the steps it repeats
  • Conditions: an if/else block with two 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 what comes out

Take an API. In low-code you see the endpoint, the inputs it takes, the steps it runs and what it returns. The first time, that’s easier to understand than reading it in a file. A lot of people learn better by seeing things, and low-code works well for that.

When to switch to full-code

Once those concepts feel normal, moving to code is much easier, because you already understand most of what the code does.

Signs you’re ready:

  • [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

AI tools make that switch easier too, as long as you understand what the AI writes. (More on that in low-code or vibe coding.)

In short

If you studied code or want to learn the details, go full-code.

If you’ve never coded, start with low-code, learn the concepts, then move to code.

In both cases the goal is to understand what you’re building. (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. What did you start with, and would you pick the same again?

Top comments (0)