Software engineer with a focus on backend technologies and a strong foundation in web development and deployment infrastructure. I care about simplicity, maintainability, and owning what I build end-to-end.
I'm a joyful and optimistic engineer, the kind who enjoys pulling on a thread and doesn't stop until I'm knee-deep in some docs. I care deeply about open-source, digital sovereignty and I'm not shy to show my passion.
Problem-based curriculum completed across four years with a formal specialization in Interactive Media, having relocated to Denmark at 18 to study entirely in English. Each semester centered on a team project integrating all concurrent coursework: combining subjects into a single cohesive deliverable rather than treating them in isolation. Core strengths in backend engineering and software design, demonstrated through standout results in object-oriented Java development, UML-driven architecture, and relational database design.
A team project of 9, building an end-to-end IoT monitoring system connecting a physical sensor board to a web dashboard.
An embedded device, with software written in C using an RTOS and firmware provided by the lecturers, collected environmental data over LoRaWAN.
Intermediary Java microservices bridged the gap: one listened to a WebSocket and pushed the data to a MongoDB instance; another service exposed the data via a RESTful API. Everything was deployed within a container to Google Cloud Platform’s Container Engine.
The React frontend deployed to GitHub Pages consumed the API and displayed real-time graphs via polling.
Led backend development and database design, coordinating between the embedded and web subteams. Delivered microservices, CI/CD pipelines, containerized cloud deployment, and a RESTful API serving live sensor data to a publicly accessible website.
In collaboration with a Danish company, a team of 3 designed and built a browser-based visual editor for workflow automation (“Drag and Drop GUI for XML File Generation”), delivered as a React single page application.
Served as the primary contact between the team and the client, translating business requirements into technical specifications and driving several specialized features directly from stakeholder insights.
The project is proprietary and the code unfortunately cannot be shared.
A self-hosted personal dashboard server written in Go. Designed as a configurable start page for day-to-day browsing: lightweight, private, and entirely under the user’s control, with no external services, telemetry, or third-party dependencies.
Configuration is defined in XML, acting as a purpose-built markup language for dashboard content: links, labels, groupings, and layout structure. XML was chosen deliberately for its structural similarity to HTML: familiar enough to be readable at a glance, but stripped of style and structure concerns entirely. The server owns all rendering logic, keeping configuration files focused purely on content.
The server generates HTML, CSS, and JavaScript at request time from the configuration file, serving a fully functional dashboard without requiring a build step or client-side framework. A single binary and a single config file are all that is needed to run a personal instance.
Update Link is a tool built for Podman users who manage containers through Quadlet unit files. It checks the versions declared in those files against upstream registries to surface available updates without requiring manual lookups.
Written in Go, Update Link queries the OCI Distribution tag-listing API and
respects channel pinning: a container tagged stable or bookworm is only ever
compared against tags sharing the same suffix, so updates never accidentally
cross release channels. Registry host aliases let non-standard hostnames be
remapped transparently at parse time.
The project is actively under development and relies on a command-line interface. It is structured as a linear pipeline; each stage is isolated and wired together, providing great building blocks that can be later expanded on.
A personal VPS running multiple self-hosted services, including this site and a Forgejo git forge. Services are managed via Podman Quadlets and selectively exposed to the internet, with full ownership of data and infrastructure.
A hands-on exercise in end-to-end infrastructure ownership: DNS configuration, container orchestration, service isolation, backups and secure public exposure of services.
Rather than a single repository, the link below points to the git forge; itself one of the services hosted on this VPS.