Why this site exists

I'm building my way into robotics and embedded systems — deliberately, in the open, one project and one broken build at a time. My long-term goal is a vocational Ausbildung in Germany, most likely as a Mechatroniker/in, with Elektroniker für Automatisierungstechnik as a secondary path.

Why robotics

I'm drawn to the point where software meets the physical world — where a line of code has to survive contact with a motor, a sensor, a real voltage. Robotics and embedded systems sit exactly there. I don't want to just write software; I want to build things that move, sense, and respond.

Why Germany, why an Ausbildung

The German dual-education system pairs real workplace training with structured technical education, which fits how I actually learn best — hands-on, with a real project or a real employer expectation attached to every concept, rather than abstract coursework disconnected from practice.

Why document all of it publicly

Three reasons. First, honesty: writing something down publicly is a good filter for whether I actually understand it, or just think I do. Second, proof: I'd rather show a paper trail of real problems and real fixes than a polished highlight reel. Third, accountability: a public, dated record is much harder to quietly abandon than a private to-do list.

What you'll find here

A timeline of short daily log entries, a journal of detailed engineering notebook pages, blog posts when I've learned something worth explaining properly, and full project write-ups for anything I've actually built end to end. It's meant to work as both a learning archive for me and an honest look, for anyone evaluating my work, at how I think and how I solve problems.

What's next

Right now that means daily German study toward a B2 level, continued embedded systems and electronics practice, and building freelance income through Notion-based systems work and web development. All three tracks are visible on the Now page.