01 / About

I'm Amped.

Software developer from the Netherlands. I build web applications for work and spend a lot of my free time building security tools, experimenting with software and figuring out how things work.

2019First IT internship
2023Started security research
2026Software development graduate
02 / Background

From IT support to software development.

I started with IT support and troubleshooting before moving into software development at MBO Utrecht. Early on I was building Discord bots, experimenting with APIs and making small tools for FiveM. Those projects got me interested in automation and backend systems.

Today I work at RV Web Solutions, where I deal with web applications, integrations and the practical side of keeping software running. Outside work I build my own applications, CLI tools and security research projects.

Go, TypeScript and Python are languages I keep coming back to. I like projects where I can understand the entire system, from the API and database to the interface someone actually uses.

03 / Experience

My journey so far.

Work, education and independent research, from my first IT internship to now.

  1. 2026 – PresentWork

    Software Developer

    RV Web Solutions

    Full-time software development, web applications, CMS integrations, APIs, troubleshooting and application security.

  2. 2025 – 2026Internship

    Software Developer Intern

    RV Web Solutions

    Professional practice placement working on real web projects and learning how software is maintained in a production environment.

  3. 2023 – PresentResearch

    Independent security research

    Personal projects

    Exploring malware analysis from a defensive perspective, web security, network monitoring and security-focused software.

  4. 2021 – 2026Education

    Software Developer

    MBO Utrecht

    Software development programme with backend and frontend development, databases, automation and professional practice. Graduated in 2026.

  5. 2020 – 2021Education

    Medewerker ICT support

    MBO Utrecht

    Completed a one-year ICT support programme focused on troubleshooting, user assistance and networking fundamentals.

  6. 2019Internship

    IT Consultant Intern

    Xantion

    My first professional IT experience, helping with support and client-focused technical problems.

04 / Journey

How I got here.

From my first IT internship to the projects I build today. My interest in security didn't start on the defensive side, and I don't want to pretend it did. This is the story of how my curiosity changed direction, and what I want to do with it now.

A change in perspective

From the dark side to helping defend systems.

When I first got interested in cybersecurity, I was drawn to the darker side of it. I wanted to see what was possible, and some of the things I was interested in weren't things I was proud of. Over time I realised that causing disruption or stress for other people wasn't worth it. That isn't the kind of developer or security researcher I want to be.

What I actually enjoy is the technical challenge: understanding a system, noticing what doesn't fit and working out why. I can do that in a way that helps people. These days I want to use what I've learned to help companies secure their networks and applications, identify weaknesses before they become real problems and make software safer for the people using it.

I'm still learning. For me, responsible security research means having permission, respecting scope, verifying findings and reporting them in a way that helps someone fix the problem.

  1. 2019
    The beginning

    Learning how IT works in the real world.

    My first experience in IT was an internship at Xantion. I was interested in computers, but this was my introduction to supporting other people and figuring out why something wasn't working.

    WHAT I TOOK FROM IT

    Start with the problem, not the tool.

  2. 2020
    Foundations

    From troubleshooting to building.

    At MBO Utrecht I started with ICT support. Networking fundamentals, user support and troubleshooting gave me a base to build on. I wanted to go beyond fixing existing software and learn how to make my own.

    WHAT I TOOK FROM IT

    Understand the system before changing it.

  3. 2021
    First repositories

    Bots, websites and the darker side of security.

    I moved into software development and started building websites, Discord bots and APIs. I was fascinated by what I could make a computer do, especially when different systems communicated with each other. Looking back at my private repositories from November and December 2021, this was also when my curiosity started moving towards the darker side of security. I was more interested in what was technically possible than in whether it was a good idea. I didn't have the perspective on permission, responsibility and consequences that I have now.

    • Discord botPrivate early project · October 2021
    • Frontend experimentsPrivate learning project · November 2021
    • API experimentsPrivate backend learning projects · December 2021
    • Early security experimentsPrivate historical projects · November–December 2021
    WHAT I TOOK FROM IT

    Technical curiosity needs boundaries. Being able to do something is not a reason to do it.

  4. 2022
    Automation

    Making tools instead of repeating work.

    FiveM became a big part of my development journey. I spent a lot of time experimenting with game software and its internals, building converters, CLI tools and templates. I wanted to understand how software behaved outside the normal paths a developer intended. Some of my private experiments were things I wouldn't choose to build today. At the same time, the public script converters, my own programming language and licensing experiments taught me about abstractions, automation, reusable code and access control. I was learning a lot, but I was still figuring out what I actually wanted to do with that knowledge.

    WHAT I TOOK FROM IT

    If a task keeps repeating, it might be worth building a tool for it.

  5. 2023
    Security curiosity

    Taking security more seriously.

    By 2023 I was starting to study security more deliberately. PHP and database coursework introduced me to the importance of how input is handled and how data is stored. My game-server privacy experiment was an early attempt at protecting information, even if my understanding of privacy was still developing. I also began independent study of malware behaviour and reverse engineering, and started an early version of Sentinel. I was gradually becoming more interested in why a system was vulnerable and how to protect it, rather than just finding out whether something could be broken.

    • FiveM Secure IP Addresses January 2023 · early privacy experiment
    • PHP / PDO courseworkPrivate school project · January 2023
    • Independent security researchPersonal learning since 2023
    • Early SentinelPrivate historical project · November 2023
    WHAT I TOOK FROM IT

    A feature working as intended is not the same as a feature being secure.

  6. 2024
    Building complete systems

    Thinking about the application as a whole.

    School projects became larger: reservation systems, inventory and scheduling, and database-backed applications. Working on complete applications meant thinking about the people who would actually use them. I also built Anonymous Auth System, an experiment in PHP authentication and privacy. It was a shift from looking at software from the outside to thinking about the decisions developers make on the inside: sessions, identity, database access and how much information should be exposed. The more I built, the more I understood that security is a responsibility that comes with development.

    • Anonymous Auth System January 2024 · public repository
    • Bowling reservation systemPrivate coursework · April 2024
    • Food bank management systemPrivate coursework · June 2024
    WHAT I TOOK FROM IT

    Security belongs in the design of an application, not just at the end.

  7. 2025
    Security engineering

    Turning curiosity into security tools.

    In 2025 my project history started to look very different. Instead of being interested only in what could go wrong, I began building tools around understanding and reducing risk. SecureShield explored defensive middleware, Sentinel-DSTAT and a private network dashboard explored network visibility, ReconX brought asset discovery into authorized research, and Honeypot explored observing suspicious activity in a controlled environment. Later that year I worked on privacy-oriented software and educational cryptography experiments. My RV Web Solutions internship and Orbit CMS project also taught me more about maintaining larger web applications. Security was becoming less about the thrill of breaking things and more about solving problems that matter to the people running those systems.

    • SecureShield March 2025 · defensive middleware
    • ReconX April 2025 · reconnaissance research
    • Sentinel-DSTAT April 2025 · network monitoring
    • Honeypot Public defensive research project
    • Orbit CMSPrivate CMS project · September 2025
    • Network monitoring dashboardPrivate project · March 2025
    • Lava Entropy Wall October 2025 · educational proof of concept
    • Privacy & entropy experimentsPrivate research prototypes · late 2025
    WHAT I TOOK FROM IT

    Good security work needs visibility, context and evidence.

  8. 2026
    Where I am now

    Combining development and security.

    I finished my software development education and moved into full-time development at RV Web Solutions. My projects now reflect what I want to do with my skills: help companies understand and secure their applications and networks, rather than cause problems for them. ShieldPass explores human verification, Penter brings together security research workflows, and Sentinel V5 continues my interest in terminal-based tooling. wcdscan explores web cache security and reproducible findings. I'm also still building general developer tools and desktop software. My ADHD plays a part in how I work: I can spend hours investigating a detail that catches my attention, and I tend to spot patterns quickly. I want to apply that curiosity responsibly, with permission, evidence and useful recommendations.

    • Glint January 2026 · Web Components library
    • ShieldPass February 2026 · public documentation
    • Penter May 2026 · public product website
    • wcdscan October 2026 · web cache research
    • Sentinel V5 October 2026 · public product website
    • PKX October 2026 · developer automation
    • Amped License ToolsPrivate access-management project · June 2026
    • StoreifyPrivate ecommerce platform · March 2026
    • CrateLabPrivate music library project · November 2026
    • Decksplice November 2026 · DJ library tooling
    WHAT I TOOK FROM IT

    A finding is not finished until I can explain it and support it with evidence.

Project months reflect initial commits found in GitHub, not necessarily the first day I worked on them. Older learning milestones come from my education and personal history.

Explore the current tools catalog
05 / Skills

What I work with.

A mix of technologies I use at work and tools I've worked with in personal projects.

Languages

  • TypeScript
  • JavaScript
  • Go
  • Python
  • PHP
  • SQL
  • Lua

Web & backend

  • Next.js
  • React
  • Laravel
  • Node.js
  • Web Components
  • REST APIs
  • CMS architecture

Security research

  • HTTP analysis
  • Web application security
  • Authentication
  • Cache security
  • OSINT fundamentals
  • Defensive malware analysis

Defensive engineering

  • Security middleware
  • Bot mitigation
  • Honeypots
  • Network monitoring
  • Session security

Data & infrastructure

  • PostgreSQL
  • MySQL
  • Redis
  • Prisma
  • Docker
  • Linux
  • Git

Tools & automation

  • Electron
  • CLI development
  • API integrations
  • Discord bots
  • Telegram bots
06 / Security

What interests me about security.

I got interested in security through the less obvious parts of applications. Authentication, request handling, caching and small inconsistencies that can turn into bigger problems.

01 / APPSEC

Web application security

Understanding how applications handle requests, sessions, cache boundaries and access control.

02 / DEFENSE

Detection & hardening

Security middleware, bot mitigation, monitoring and learning how to reduce risk without making software unpleasant to use.

03 / RESEARCH

Systems & automation

CLI tooling, structured evidence, defensive malware research and repeatable workflows in authorized environments.

How I approach security research
07 / ADHD

ADHD is my security superpower.

I have ADHD, and when it comes to security research, it can feel like a superpower. When something catches my interest, I can spend hours digging through code, looking for bugs or trying to understand why something behaves differently. Those hours can feel like minutes.

I tend to recognise patterns quickly and notice small details that don't fit. An unexpected response, a difference in behaviour or something in the source code that just looks out of place can be enough to make me want to investigate further.

ADHD comes with challenges too, but I've learned to use my curiosity, hyperfocus and pattern recognition to my advantage. Spotting something unusual is only the first step. I still want to reproduce it, understand why it happens and back it up with evidence.

08 / Approach

How I like to build things.

Start with the problemGet the core logic working first. Add an interface when it makes the tool easier to use.
Keep it modularPrefer clear APIs, reusable components and tools that can be extended without rewriting everything.
Automate the boring partsIf I keep doing the same thing manually, I usually end up building something for it.
Verify before claimingA scanner result is a starting point. Reproduce it, understand it and document the evidence. Only test systems with permission.
09 / Projects

What I'm building outside work.

Penter and Sentinel V5 are two of my larger projects. I've also worked on security middleware, traffic monitoring, human verification, developer utilities and desktop apps. The tools page separates public source from private projects.

Browse the tools catalog