42 Discovery
Started at 42 London and fell deeply into low-level programming, systems thinking, problem solving, and C development.
A personal engineering archive descending from orbital-scale systems and technical abstraction toward grounded more grounded, personal development, and the increasingly human side of building things.
Orbit / LEO / atmosphere / ground
A curated archive of realtime systems, embedded sensing, visualization, signal processing, rendering, and data engineering experiments documented through mission-style technical dossiers.
Started at 42 London and fell deeply into low-level programming, systems thinking, problem solving, and C development.
Continued the curriculum while working at 42, developing confidence with debugging, tooling, APIs, and technical independence. Won my first Hackathon at Greenhack 2024.
Moved to Germany and continued at 42 Heilbronn, where my interests began shifting toward aerospace systems, realtime software, and applied engineering.
Began building projects involving sensors, telemetry, visualization, drones, IMUs, and realtime embedded systems.
Started documenting projects publicly through C Labs, combining engineering, education, visualization, and technical storytelling.
I've always been fascinated by understanding how things work. Not just using them, but taking them apart mentally until I can explain every piece of the system to myself. And crucially, to others.
Most of my projects start with a question rather than a plan. Sometimes that question is technical: how does a gyroscope know which way it's pointing? Sometimes it's architectural: how do you even get the data to the point where you can "just use ai"? More recently I've found myself drawn to the space between software and the physical world, where sensors, electronics, visualization, and realtime systems all meet.
I learn best by building and teaching. Many of the projects in this archive began with little more than curiosity and a notebook full of bad assumptions. Somewhere between the first prototype and the final result, those assumptions usually get replaced by a much deeper understanding of the underlying system.
When I'm not building things, I'm usually trying to explain them. Reverse engineering, visualization, and technical education have become just as interesting to me as the engineering itself. The goal isn't simply to make something work; it's to understand it well enough that someone else can follow the journey too. More often than not, teaching it ends up reinforcing my own understanding aswell.
This archive is a collection of those journeys.
If you'd like to get in touch, the communication channels are just below.