Well, this is unexpected.

If you told me ten years ago I'd be writing for a living, I probably would have laughed and gone back to debugging my code. Let me explain.

Picture this: I started out as an engineer. Deep in the world of logic, circuits, and compilers, trying to make sense of things that operate in hard zeros and ones. It was challenging, sure, but my brain was itching for something more creative.

To keep the lights on (and honestly, to fund my coffee habit), I began teaching coding. I kept studying, kept grinding, and eventually walked away with a shiny master's degree. I was doing all the "right" things a good technical professional is supposed to do.

But the truth? My heart was always scribbling in the margins. Every time I shared a long-winded email, a blog post, or even a highly detailed piece of documentation, someone would inevitably pull me aside and say, "You know, you should really be a writer."

Eventually, I took the hint. I decided to stop fighting the current. I dove headfirst into technical writing—figuring out how to translate complex, headache-inducing jargon into actual human speak. Turns out, explaining hard things simply is a superpower.

That pivot changed everything. It gave me the confidence to launch a full-time writing career, blending my analytical background with my love for storytelling. It's been a wildly non-linear, slightly chaotic journey, and honestly? I wouldn't change a single thing.