Why I Chose Technology

It didn't start with a grand plan. It started with curiosity — the kind that makes you pull apart a toy to see what's inside. When I first saw a webpage behave in response to code I had typed, something clicked. I wasn't just consuming the internet anymore. I was making it.

That moment of control — of creating something from nothing but logic and text — was addictive. I wanted more of it.

I could have gone in many directions. But technology kept offering something most fields don't: immediate, tangible feedback. You write code, you see the result. You fix a bug, the thing works. That tight loop between thought and outcome is rare — and I find it deeply satisfying.

Beyond that, technology is one of the few disciplines where a single person, with the right skills, can build something used by thousands. A doctor needs a hospital. A manufacturer needs a factory. A developer needs a laptop and an idea. That leverage is extraordinary.

I gravitated toward the frontend first — the visible layer where design meets interaction. There's a unique challenge in making something that not only works but feels right. Animations that breathe life into a page. Layouts that guide the eye intuitively. Interfaces that disappear because they're so natural to use.

As I grew, the backend pulled me in too. Understanding how data flows from a database to a screen, how APIs mediate between systems, how authentication keeps things secure — all of that deepened my respect for the whole stack. Now I think in systems, not just components.

And then Three.js opened a door I didn't know existed: the web as a 3D canvas. Building interactive 3D experiences in the browser still feels like magic to me. It's the intersection of art, physics, and engineering — and it's where I feel most creatively alive.

I stay in tech because of the people. Watching a student build their first working app — the look on their face when it actually runs — is something I don't want to stop experiencing. Teaching at Digital Fortress taught me that knowledge compounds when shared. What I pass forward multiplies.

I stay because every project is a different problem. A job board, a restaurant site, a finance tracker, an AI assistant. Each one required me to learn something I didn't know the week before. That constant novelty is not a feature of the job description — it's baked into the nature of the field.

I stay because the internet is still young. The interfaces we use today will look primitive in ten years. The patterns we take for granted are being reinvented. And I want to be someone who builds the next version of things, not just consumes the current one.

If I had to distill it: build things that are useful, make them beautiful, and ship them. Not perfect — shipped. A live product with rough edges teaches you more than a perfect prototype that never launches.

I believe good code is respectful. Respectful of the user's time (so it loads fast), respectful of the next developer (so it's readable), and respectful of the business (so it's maintainable). Quality is not a luxury — it's the baseline.

And I believe learning is infinite. There will always be a new framework, a new paradigm, a new approach. The developers who stay relevant aren't the ones who know the most right now — they're the ones who've built the habit of learning fast and adapting constantly. That's the skill beneath all skills.