"How I Stumbled Into Technical Writing (And What I'd Tell My Earlier Self)"

I didn't plan to become a technical writer I stumbled into it out of curiosity, the way most good career decisions actually happen. I had a background in data science, and somewhere along the way I found myself more interested in explaining technical concepts than just working with them. One thing led to another, and before I knew it, I was deep into API documentation, white papers, and developer content. Nobody handed me a roadmap. I took a free online course early on, which helped but honestly, self-learning taught me more than any structured curriculum did. The biggest thing I wished I had? A mentor. Someone who had already walked the path and could tell me what actually mattered versus what I could skip. This post is my attempt to be that for you. If you're considering a switch into technical writing whether you're a developer, a recent graduate, someone from a non-tech background, or just curious like I was. Here's what I wish someone had told me from the start. First, What Is Tec