Skip to main content
BVDNET
Arnhem · websites & automationBVDNET
Moodboard

Who I am,
and how I work.

My interests look like a messy list: music, lathes, drones, telescopes, algorithmic art, broken phones. They are not. It is always the same person doing the same thing: working out the rules something runs on, taking it apart to understand it, and then rebuilding it better or making it anew. Whether it is sound, metal, light or code makes little difference. The approach is always the same.

7 / 13
CAD & 3D printing

A 3D printer is a tool, not a hobby.

I design in CAD and 3D print because it is useful, not because I love it.

to the topic →
Overview · four themes

All interests end up at building with code.

Pick a theme to see only those topics, or hover over the overview.

Node graph of interests, all converging on building with code and AI agentsMusic / DJAlgo artPhotographyPrintingAudio / electronicsCNCCAD / 3D printFPVRepairPhilosophyMetaphorsAstronomyBuilding with code & AI
Building with code & AI agents

This is where all the interests come together.

For your project that means: I start with who the visitor is (music), I choose tools on usefulness rather than price (photography), I build for what can go wrong (CNC), I find the cause first (repair), and I explain what I do in plain language (metaphors).

to the topic →
Music production, performance & DJ

Making music is learning the rules, and knowing when to depart from them.

Composing and producing has two sides. The musical side is a set of rules for harmony, rhythm and structure; you learn them so you can deliberately let them go. The technical side is the signal path from instrument to speaker, in which every link has to pass on exactly the right level.

Besides that, I think about the listener with every track. When preparing a DJ set that is the whole job: who is in the room, what mood are they in, and which next record takes them where I want them to go.

In my work

I do the same with a website. Before I build, I want to know who the visitor is, where they come from and what they need to be able to do. That decides the order of the page, the copy and the buttons. With an AI agent I also start at the receiving end: what does it need to know to do the right thing.

Algorithmic art

Making images by operating a calculation by hand.

I make abstract images with a calculation called convolution: the same operation photo software uses to sharpen or blur an image. I operate it by hand, through a converted cash-register keypad, and repeat it until an image appears that keeps my attention.

The operation itself is nothing special. It runs in every phone camera and in every model that recognises images. The difference is that I steer it myself instead of letting it run automatically.

In my work

Convolution is also the basic operation of the neural networks that recognise images, so I know that building block from the inside. More relevant to your project: I am used to steering an automatic process by hand and choosing critically what stays. That is exactly my role when I write code with an AI model.

bvdart.nl — process
Photo- & videography + editing

Taking a good photo with as little equipment as possible.

For me, photography is capturing a moment with as few means as possible.

At events I shoot with a Canon from 2013 and a wide-angle lens, and the results hold up next to those from far more expensive cameras. Product photos for web shops I take with a Sony Mavica from 1998. It produces small files of 640 by 480 pixels that need no processing at all on a website and still look modern.

After the shoot comes the selecting: from hundreds of photos down to a series of ten.

In my work

That is how I build too. I pick the tool that does the job, not the most expensive one, and keep costs low. That is why FinancieelSlimleven runs on zero euros of hosting per month. And selecting from hundreds of photos is the same skill as judging what an AI agent produces: most of it goes, the best stays.

Print & color correction

Printing digital images without losing anything.

I print my images myself on modified inkjet printers. That came from a requirement: the images are small, from 64 by 64 to 512 by 512 pixels, and on paper every pixel has to stay visible as a sharp square.

A normal printer softens edges when enlarging. For this work that has to be switched off. Then comes colour management: making sure the colour on paper matches the colour on screen. To me that is a necessity, not a hobby, but I do get the most out of it with cheap ink and cheap paper.

I measure colours with a professional colorimeter I bought as defective. With open-source software it works again at the level of a new unit.

In my work

In code I make the same kind of choices: the default setting is not always the right one, and I check what the work needs. And getting a written-off instrument working again with open-source software is how I prefer to build: maximum result from minimal means.

Analog electronics & audio

Electronics in which you can see and measure every part.

Analog audio equipment is fun because you can see and measure everything. Every part has one function, and with a meter you find where the fault is without a manual.

Often there is mechanics in there that solves what software does today. An old cassette deck reverses the tape automatically with a system of levers and gears; a newer deck does the same with a second head and a bit of code.

In my work

In software I want the same visibility: being able to measure at every point what is really happening, without a layer in between that hides mistakes. That is why every site I deliver comes with monitoring and error reporting. And because I have seen the same problem solved in mechanics and in code, I know there is always more than one solution.

CNC machining

Programming machines that produce for days on end without supervision.

As an apprentice machinist I programmed and operated CNC milling machines and the robots that feed them. The real work is the program: it has to keep the machine running for days with as little downtime as possible.

So you plan for what goes wrong. A cutter wears, and the program has to correct for that before the dimensions drift. You measure along the way and adjust. And every second counts: one second per piece is almost three hours on a run of ten thousand.

In my work

That is how I look at software now. A site or automation has to keep running when a connection fails or a vendor changes something, and it has to report that instead of breaking silently. My own monitoring platform, BVDART Ops, is the same problem: keeping production going without someone having to sit next to it.

CAD & 3D printing

A 3D printer is a tool, not a hobby.

I design in CAD and 3D print because it is useful, not because I love it.

It is the fastest way to replace a part or hold an idea in your hands: drawn this afternoon, printed tonight. As with the inkjet printer, I get more out of cheap equipment here than the manufacturer promises.

In my work

In projects I work the same way: quickly make something working that you can look at and adjust, instead of writing a plan for weeks. That is why a first version of your site goes online early, so you can respond to it.

FPV drones (acro)

Flying a drone that cannot stop.

I fly racing drones in manual mode. In that mode the drone does not stop when you release the throttle: it keeps going at its speed, and for a simple turn you operate four axes at once.

So you have to look ahead and correct continuously. That takes full concentration, and that concentration is exactly why I do it.

In my work

You steer a running system the same way. A website with visitors or an automation that runs every night cannot simply be paused; you correct while it runs, and you plan your change ahead. That full concentration is also how I work: one thing at a time, completely.

Repair & refurbishment

First understand why something is broken, only then repair it.

With my own things I repair by feel: open it, look, fix it. That almost always works. I follow a fixed procedure when the stakes are high, as with the Apple repairs I did at Coolblue, or when the cause is not immediately clear.

What I enjoy is finding the cause: why does this device do this. Replacing a screen or battery is routine. Understanding why a device keeps rebooting is the real repair.

In my work

I track down faults in software the same way: first understand why it goes wrong, only then change something. And I weigh the stakes. On a test environment I try things quickly; on a site with visitors and orders I use a fixed check before anything goes live.

Philosophy, psychology & cognition

How a brain works, and what that says about AI models.

What occupies me is the similarity between a brain and a language model. Your thoughts arrive on their own and you only partly steer them, much like the text a model produces word by word. And a mood works like an instruction given in advance: whoever starts out gloomy reads everything that follows as gloomy. A model does the same with the context you give it.

I read about it out of interest, but I use it daily.

In my work

If you understand how a mood colours your own thinking, you also understand why an AI model is so sensitive to what you tell it beforehand. That is why, in automation, I spend most of the time on the instructions and the context, not on the model. That is the difference between an agent that delivers clean work and one that misses.

Metaphors & analogies

Explaining in one sentence what would otherwise take an hour.

I like to explain things with a comparison. The yardstick: my mother has to understand it. The aim is to reduce something complicated to the shortest explanation that is still correct.

I learned that at the service desk at MediaMarkt and Coolblue, where I had to explain to customers why their problem was not covered by the warranty. That only works if you truly understand it yourself.

In my work

For you this means you will not get a technical explanation you cannot follow. I explain what a choice means for your business, in plain language. And an AI model often grasps a good comparison better than a long technical description, so I use them there too.

Astronomy & spaceflight

Looking at something far bigger than your own work.

Astronomy gives me perspective. Everything that exists, from stars to people, comes out of the same natural processes. That is the largest system there is, and I find it calming to look at it now and then.

Spaceflight is the technical side of it. The first probes were controlled from millions of kilometres away with less computing power than a Game Boy. That it worked came down to careful design, not expensive equipment.

In my work

That perspective keeps me focused on what really matters in a project and what is decoration. And early spaceflight is the best proof that you can build something reliable with few means. With that attitude I also run a site on zero euros of hosting per month.

Building with code & AI agents

This is where all the interests come together.

Since mid-2025 I have been building websites, shops and automations full-time, in TypeScript and Python, together with AI models such as Claude. Everything I learned in music, metal, image and language goes into that.

The work consists of the same steps: working out how something works, designing it, building it, checking it critically, repairing it until it is right, and explaining what is happening.

In my work

For your project that means: I start with who the visitor is (music), I choose tools on usefulness rather than price (photography), I build for what can go wrong (CNC), I find the cause first (repair), and I explain what I do in plain language (metaphors).

In short

In short: I work out how something works, take it apart and rebuild it better, and I can explain what I did. Every interest taught me something I now use daily: knowing who you build for (music), building for what can go wrong (CNC), finding the cause first (repair), and explaining the complicated briefly (metaphors). Those are also exactly the skills you need to make good software with AI models: saying precisely what you want, reading critically what comes out, and repairing until it is right.

There is one more thing that comes back everywhere: I assume I can learn to do something myself. I try, make mistakes, and only stop when something genuinely cannot be done, for instance because a vendor locks it away or because it is too expensive. Because the easy solution usually costs money and that was often not there, I learned to get the most out of few means. A cheap camera that matches expensive ones, a written-off colorimeter that works again, and a mortgage platform running live on zero euros of hosting per month.

That is what you can expect from me on your project: first work out how your business and your customers work, then remove what does not hold, and rebuild it better. At as little cost as possible, and in a way you can manage yourself afterwards.