Hi — I’m Timothy.I’m now a software engineer based in Tokyo. But before I ever touched JavaScript seriously, my path started in a very different place: engineering, mechanical systems, and eventually, Building Services Engineering (BSE).

This post is a reflection — not about regret, but about understanding how we end up making the choices we do… and how sometimes, we grow out of them.

The First Shift: Into BSE

Before I studied BSE, I was doing general engineering. I had some exposure to programming early on — C++, MATLAB — and when I moved into mechanical engineering, I picked up more.

But I never thought of software as a career. At the time, the word “developer” to me meant IT support, someone fixing printers or helping you reset passwords. I couldn’t yet imagine that people like Elon Musk or Bill Gates also started with code — and used it to build entire systems and companies.

When it came time to choose a major, I followed the advice around me. People said BSE had good career prospects, it was practical, and in demand. So I transferred universities and committed to the path. I didn’t know much about HVAC systems, fire services, or green buildings — but I was accepted, and I began learning.

It felt like the safe choice.

A Quiet Realization

For two or three years, I tried to make it work. I studied, took internships, and did what was expected — but something always felt slightly off. There was a gap between what I was learning and what I enjoyed.

It wasn’t just that the subject matter was technical — it was the lack of ownership. Most of the work was about maintaining or documenting existing systems, not creating new ones.

I didn’t hate it. But I didn’t feel alive in it either.

A Turning Point: The Final Year Project

Everything changed when I started my final year project.

I chose a topic that involved sensors and Arduino — something more experimental, something I could design myself. For the first time in years, I felt excited about what I was doing. I spent time thinking through the design, building the setup, and troubleshooting the code. I rediscovered what it felt like to work with autonomy and intention.

Looking back, it wasn’t just the tech that drew me in. It was the process of deciding what to build — not just how to follow instructions.

After Graduation: A Quiet Discomfort

After university, I started work as a contractor in BSE. Most days were filled with paperwork, site inspections, and coordination meetings. The pattern was predictable. And maybe that’s what made it difficult.

At some point, I realized:If this continued for the next five years, I might never get back to the kind of work I loved in my final year.

So I left.

A New Start

I signed up for a coding bootcamp.Not because I knew it would change my life, or that I had a grand plan to move to Japan. But because I remembered how I felt when I was building something I cared about — and I wanted more of that.

It was a quiet decision, but it was mine.And that made all the difference.

A Note for Anyone Else in That Space

I don’t think BSE is a bad field. It gave me structure, a way of thinking, and a lot of discipline. But I wasn’t building the kind of future I wanted.

Now, as a software engineer, I feel much closer to the work I enjoy — the building, the problem-solving, the ownership. It’s not always easy, but it feels right.

If you’re at a crossroads — between something that’s “safe” and something that feels more you — I hope this helps you reflect. You don’t need to burn everything down. You just need to give yourself permission to explore what else is possible.

— Timothy

👀 I’ve grown the most from working with teams that value curiosity, speed, and empathy — happy to connect with folks who share that — or you’re just curious about how I made the jump — feel free to check out what I’ve been working on (via LinkedIn, Medium…)