Components
Separate pieces with clear jobs, stable interfaces, and builds that work on Windows and Linux.
C++20ProtobufLinux / Windows
HOW I WORK
Simple designs are easier to change.
I use clear C++ interfaces, small components, and automatic checks to keep software understandable.
01 / WHAT I DO
The main parts of the work.
Good boundaries help people work on a system without getting in each other's way.
Data pipelines
Code that turns radar detections into tracked and classified objects for customers.
EventsFMIRadar
Reliable software
Checks, reviews, and tests for automotive code where mistakes are expensive.
MISRA C/C++Static analysisADAS
02 / PRINCIPLES
Clarity beats cleverness.
Software is easier to maintain when the next person can understand it.
I try to make the right way to change a system easy to see.
- Clear — Small parts and explicit decisions.
- Testable — Components that can be checked on their own.
- Shared — Simple rules that help the whole team contribute.
That matters even more in automotive software, where dependable behavior is part of the job.
03 / CHECKS
Let the tools catch the easy mistakes.
Automatic checks leave more time for the hard decisions.
Builds and tests
Every change is built and tested automatically.
Code checks
Formatting and C++ rules are checked before review.
Releases
Versions and builds follow a clear, repeatable process.