About AvdB
AvdB grew out of an interest in development and cybersecurity.
I enjoy building websites up from the code, but also looking further than how something looks. How does it work technically? Is it fast? Is it put together sensibly? And was any thought given to security while it was being developed?
That's what eventually became the foundation of AvdB.
Plenty of websites do what they have to do. And that's where it stops.
You still see sites that feel dated, load slowly, look like a hundred others or are built far heavier than they need to be. And security rarely gets the attention during the build that I think it deserves.
That's exactly where I saw something. I didn't want to treat design, development, speed and security as separate things, but as parts of the same process.
A different logo on the same template isn't custom work
The website is built around the business. Code, layout, components and imagery are made specifically for the character and feel of that one company.
A construction firm doesn't need the same website as a consultancy, a restaurant or an engineering company. The point is that a site not only looks professional, but genuinely feels like it belongs to the business.
Quality lives under the hood too
To me, speed is part of good development. A fast website feels better for your visitor, and at the same time it shows that some thought went into how the thing is put together.
So I keep unnecessary code and dependencies to a minimum. I'd rather work with exactly what a website needs than with a large system full of features nobody ever uses.
Secure by design
At AvdB, security isn't a step that only comes into view at the end of a project. While building I'm already thinking about risks, about the technical structure, and about how a site stays secure and maintainable in the longer run.
My background in cybersecurity plays into that. It means I don't only look at a website as a developer, but with a security eye as well.
No website is untouchable. But you can build with that in mind from the start. That gives you a better technical foundation, and more peace of mind once the site is live.
Only when it adds something
AI is finding its way into more and more websites. That doesn't automatically make anything better. I only use it when it genuinely delivers something.
One example is an assistant that helps visitors with their first questions and points them towards personal contact at the right moment. Not because a website has to have AI, but because in that case it helps the visitor along.
You deal directly with the person building it
During a project you can call, email or message me whenever you have a question, want to know how things stand or want to talk something through. I think it matters that you can be part of the process.
In the end you shouldn't just get a website that had a lot of technical care put into it, but above all something you're enthusiastic about yourself and that feels like it belongs to your business.
What AvdB stands for.
- Quality over quantity
- I'd rather build fewer projects I fully stand behind than as many websites as possible back to back.
- Craft
- Attention to what you see and to what sits behind it technically.
- Client satisfaction
- You should feel heard and know where you stand. That also means I'll say it when something takes longer, or when I don't think a solution is wise.
Web development is the beginning
Over the next few years I want to develop AvdB further towards cybersecurity for small and medium-sized businesses. Not only securing and testing websites, but also thinking along about systems, networks and the wider digital security of an organisation.
From security testing and advice through to designing and implementing practical security solutions. The aim is to grow AvdB into a technical partner that businesses can turn to for their online environment and the security behind it.
A passion for the technical work.
Quality in what gets delivered.
Two things that sum AvdB up best.
Get in touch