ABOUT / APPROACH

About

I am interested in how the layers of software connect — and what happens when they do not.

I like following a system to the point where one of its assumptions stops holding.

I started with low-level programming. Back then, a bug could come down to a register, a timing issue or a single bit.

In GPS:NO, my work spans C++ firmware, UWB positioning, testing and evaluation. BO-Tracker was a team project where the boundary moved further out: microcontroller, cellular link, cloud processing and a web application. My contribution was in firmware and AWS IoT/Lambda integration.

Backends, interfaces and infrastructure then became further parts of the same system. I do not only want to know that something works. I want to understandwhy — and what happens when one layer fails.

I prefer understandable architectures, measurable results and documentation that explains why a system was built the way it was.

And I like the point where a project stops being a prototype and starts becoming a real system.

ENGINEERING JOURNEY

  1. 01

    Bare Metal

    Understanding the machine

    Setting bits, reading registers, understanding memory and timing. Abstractions are useful — I still want to know what is underneath.

  2. 02

    Embedded Systems

    A device becomes a system

    UWB, IMU, Wi-Fi and MQTT brought protocols, data quality, failures and timestamps into the picture.

  3. 03

    Software Systems

    Data becomes an application

    Backends, APIs and databases became applications that people could actually use.

  4. 04

    Operations

    What happens after git push?

    Builds, deployments, load, failures and metrics are the next layer of the same problem.