Engineer by degree.
Developer by compulsion.

I'm a final-year Mechatronics Engineering student at Bells University of Technology, and for the last two years I've been running two careers in parallel: by day (officially), CAD and electrical engineering — piping models, lighting simulations, single-line diagrams, data-center documentation. By night (also officially), mobile and web development — Flutter and React Native apps in production, with real users and real crash reports.

The useful side effect: I've become a translator. Engineering teams and software teams notoriously talk past each other, and I've sat on both sides of that conversation — close enough to the hardware to respect it, close enough to the codebase to ship it. Requirements written in engineer-speak come out the other end as working software, and vice versa.

I once launched a public learning series on LinkedIn called "100 Days of Growth." It lasted four days. In my defence, the growth was real — I just spent it building things instead of posting about building things. The series may return; the consistency arc is still in development.