Journey

It did not begin with a career plan

My technical journey didn't begin with a career plan. A lot of it grew naturally from the environment around me, especially from watching my father work, build our family business, and find solutions when problems appeared. That mindset became the starting point, but the direction it eventually took became my own.

When programming became physical

Programming was the first field that really pulled me in. I joined the robotics team at school and became its programmer, which introduced me to the connection between software and physical machines.

From there, I started learning on my own—first programming, then Arduino, and eventually the electronics behind the systems I was controlling.

Field Note — One subject kept exposing another

Learning rarely stayed inside the boundary where it began. Code led to controllers; controllers led to circuits; circuits led to the devices and physics underneath them.

Going below the abstraction

That progression took me deeper into embedded systems, communication, electronics, and eventually power electronics.

When learning had to produce a working machine

At some point, learning stopped being mostly experimental and became practical. I opened my own electronics repair lab and began working on real equipment, where understanding a circuit was no longer enough—the diagnosis had to lead to a working machine.

Field Note — Reality became the final test

A convincing explanation was not the result. The equipment working again was the result.

Outside the lab

My first experiences outside that environment expanded the scale again. During an internship in Georgia, I worked on electrical-panel assembly and began seeing more structured engineering practices.

At Robot Pi Shop (May 2025–August 2025), the different skills I had been collecting started coming together: electronics, programming, design, prototyping, fabrication, and complete project execution.

Larger systems, larger consequences

That path eventually led me into industrial machinery at Douaihy pour le Bois. The systems became larger, the consequences of mistakes became more serious, and troubleshooting increasingly meant understanding how electrical, mechanical, control, software, and process problems interact.

Field Note — Separate subjects becoming one discipline

It feels less like the end of a journey than the point where all the separate things I learned began becoming one discipline.