For a long time, I thought building software wasn’t for me.
Not because I wasn’t interested - quite the opposite. I spent years working on digital products. Startups, new ideas, features, strategy.
But never actually building it.
I worked with developers, discussed solutions, made product decisions. But at the end of the day, there was always a gap between having an idea and bringing it to life myself.
And I accepted that this is just how it is.
Because I wasn’t “technical” and never will be.
Luckily that assumption turned out to be wrong
My first contact with ‘no-code’ - which was not termed as such at that time - actually dates way back to 2012 when I played around with IFTTT - an early automation tool - to build a simple automation to save email attachments to my dropbox.
I also built a page once with wordpress, and I tried blogging on Blogger about my travels - for about 5 weeks that is.
It took another 8 years and a covid lockdown in Berlin to get reintroduced to no-code while working on the side project with my flatmates.
I picked up Bubble for the first time, but quit it right away. I remember telling my flatmate “I might as well learn to code”.
Then I built my first app on Glide. A simple conference app - that was easy. That was my first lightbulb moment: I can actually build stuff. But after a few weeks I already ‘grew out of it’ as I felt I hit a wall.
But I learned a few important things and felt ready to give Bubble a chance again - because now I wanted more.
Suddenly, it felt easy and after a few weeks I thought I could build pretty much anything - which, in hindsight was laughable. But that was my second lightbulb moment: I can build whatever I want and I even understand how software actually works.
From there on, I went on to use a dozen other no-code tools. They all work kind of the same - it’s all software at the end.
And I could do it from anywhere. A coffee shop, a coworking space, a different city or a different continent.
What changed after that
Instead of just ‘talking’ product, I am now building them:
- my own website
- SaaS MVPs
- a directory
- a mobile app
- small tools like a PDF generator or image compression
- automations - over a hundred of them as of today.
For the first time, I could create without depending on anyone.
The rise of vibe coding had me a bit disoriented at first. Was it replacing no-code? Once I adapted, that was my third lightbulb moment: no-code plus AI make building software easier, faster, and more fun.
The two biggest misconceptions I see today
If you’re just getting into this space, you are probably in one of these camps:
On the one side we have: ”I’m not technical enough” - so you never start because it feels too complex and the daily news are overwhelming.
On the other side you might say: ”AI will do everything anyway” - maybe you build a website using AI, so you skip learning entirely and hit a wall two months in.
Neither path actually works.
Software <> Code
You don’t need to be a developer to build software today.
But you do need to understand what you’re doing - and the best way is by actually building things - first ‘with your own hands’ then with more and more AI-support.
Learning by building changes how you think
As a side-effect, building with no-code changes how you think.
You stop seeing software as something complex and abstract. You start seeing it as a series of small, solvable problems - and most of them are less complicated than they look before you’ve actually touched them.
You learn how to break things down, how to debug, how to ship something valuable.
From:
“I’m not technical enough”
To:
“I can figure this out step by step”
Once you start, things move faster than you’d expect. What feels impossible at the beginning stops feeling that way pretty quickly.
Why no-code and AI work best together
There’s a lot of discussion right now about AI replacing all software.
And yes - AI is incredibly powerful.
But it doesn’t make no-code obsolete. If anything, it makes it more useful.
Because they solve different problems.
| Approach | Strengths | Limitations |
|---|---|---|
| No-code | Structure & control | Can hit some limits in very (and I mean VERY) complex cases |
| AI / coding | Flexibility & speed | Hard to impossible to maintain & debug without understanding |
| Combined | Speed + control + flexibility | You need to know when to use what |
Used together, they complement each other extremely well.
Used in isolation, both can have limits.
Who this is for
This is for you if:
- you’ve never built software before, but want to
- you have ideas and want to bring them to life
- you’re willing to learn by doing
- you’re curious how things actually work
This is not for you if:
- you’re looking for magical outcomes without understanding
- you expect things to work instantly without effort and patience
- you think this is some sort of get-rich-quick scheme
If there’s one idea to take away
Mastering no-code completely changed my professional life.
It opened a whole world of opportunities and freedom.
There’s no reason it should be different for you.
And the best part is: Learning to build software as a non-technical person is very much achievable.
If you want to join me and others on that journey, join the community.
