This site started in a very simple way. I was sitting at DevWorld in Amsterdam, listening to Matt Biilmann, the CEO of Netlify, talk about Agent Experience and how software is moving from a code-centric world to an agent-centric world.
A lot of what he said was technical, but what stayed with me was not only the technical part. It was the human shift behind it.
For a long time, I saw software as something that belonged mostly to developers. I could think about systems, write concepts, map journeys, design services, talk about user needs, and explain what should exist. But when it came to turning those ideas into something working, I always felt there was a gap. I could be the founder, the strategist, the domain person, or the person with the lived experience, but not really the person building the thing.
That line has started to move.
Over the last few weeks, I have been using AI agents and coding tools to build parts of Flux Forward. Not perfectly, and not without breaking things. But enough to test ideas that would have stayed in documents before. I have worked on an Activation Scan, an ecosystem Hub, a small AI companion called Fluxi, and a first attempt to connect these pieces into one activation flow.
I am still not a developer in the traditional sense. I do not want to pretend that I suddenly became one. There is a difference between using AI to build prototypes and having deep technical craft. But something important has changed for me. The distance between thinking and making has become much shorter.
Before, I might have written a document explaining how a system should work. Now I can try to build a rough version of that system. Before, I might have waited for someone technical to translate the idea into an interface. Now I can sit with an agent, describe the logic, test the flow, adjust the page, break it, fix it, and learn while doing it.
That changes the feeling of building.
It is not only about saving time. That is the part of AI that gets talked about a lot. More speed, more output, more efficiency. But for me, the more interesting part is ambition. When the cost of trying goes down, you start asking different questions. Not just “how can I do this faster?”, but “what can I now try that I would not have tried before?”
When the distance between thinking and making gets shorter, ambition changes.
That question matters to me because Flux Forward is not a simple website or a simple service. It is about helping international talent and organizations navigate transition, work, identity, culture, belonging, and hidden systems in the Netherlands. A static directory is not enough for that. A normal landing page is not enough either. The real challenge is helping people understand where they are stuck, what layer they are solving, and what next move makes sense.
That is also why this personal site started to make sense to me. I needed a place outside the formal Flux Forward brand where I can think in public about these changes. A place for reflections on AI, transition, building, founder life, and the strange space between what already exists and what is not fully here yet.
That is why I called it Not Yet.
Not because nothing exists, but because many of the things I care about are still becoming. The work is not finished. The systems are not clear yet. The role I am growing into is not fully defined yet. Even this website is not meant to be a fixed object. I want it to change as my thinking changes.
Matt’s talk gave language to something I was already feeling. The future of building is not only about developers writing code faster. It is also about more people being able to turn their knowledge, questions, and lived experience into working systems. That does not remove the need for real technical skill. But it does change who can participate earlier, test faster, and shape what gets built.
For me, this is the beginning of that shift.
Not yet a developer. Already building.