My Master Thesis Was About No-Code Before It Was Mainstream

In 2008, I completed my Master's degree in Software Engineering. Looking back today, what surprises me most is not the technology I used, but the problem I was trying to solve.

At the time there was no ChatGPT, no Copilot, no AI agents and no no-code movement. Yet I spent months working on an idea that sounds remarkably familiar in 2025: making software creation accessible to people who could not write code.

The project was called VisMode.

The Question That Started Everything

Like many software developers, I was frustrated by the gap between business people and software teams. Business experts understood the problem. Developers understood the technology. Translating between those two worlds was often slow, expensive and full of misunderstandings.

I started wondering whether software could be described visually rather than programmed line by line. What if domain experts could model processes, screens and business rules directly without having to learn a programming language first?

What if creating software looked more like designing a process than writing code?

The Inspiration

The idea came from two very different places.

The first was Adobe Flash. At the time, Flash allowed designers and developers to create surprisingly sophisticated applications through visual tools. The second was Lego Mindstorms, where robots could be programmed by connecting visual blocks together instead of writing traditional code.

Both experiences suggested the same possibility: perhaps software could be assembled rather than programmed.

The Vision

VisMode was an attempt to build exactly that. Users could design screens, define workflows and describe business logic using graphical models. The platform would then transform those models into a working application.

Today we would probably call it a combination of no-code, low-code, workflow automation and model-driven development. Back then I simply saw it as a different way of building software.

The Lesson I Was Not Expecting

The most valuable thing I learned was not that the idea was good. It was that the hardest part of software development is rarely the code itself.

I quickly discovered that drawing screens and workflows is easy. The real challenge is representing the complexity of real businesses. Exceptions, approvals, regulations, edge cases and constantly changing requirements do not disappear simply because the interface becomes visual.

Removing code does not remove complexity.

It simply moves complexity somewhere else.

Looking Back Seventeen Years Later

What makes this story interesting to me today is that the industry eventually moved in the same direction. No-code platforms became mainstream. Low-code became an enterprise category. AI is now generating software from prompts and natural language.

Many of the questions I explored in 2008 are still being explored today, just with more computing power, better interfaces and vastly larger investments.

Final Thought

VisMode never became a commercial product. It never raised funding. It never became a startup.

But it taught me one of the most important lessons of my career: sometimes being early is almost indistinguishable from being wrong.

And sometimes an idea needs an entire industry to catch up before people can see what you were trying to build.