Before I ever wrote a doc, I was explaining tech to people who didn’t speak its language yet. I spent years in classrooms, live-debugging code, walking through logic errors, and helping others understand systems that often felt overwhelming. Sometimes it was with fellow CS grads, other times with learners coming in from different backgrounds. That’s where I learned that real understanding comes from knowing how to teach, how to break things down clearly, and how to make someone feel like they’re not the only one stuck.
Over the last five years, I’ve grown from a content generalist into a technical writer, developer, and IT trainer. I’ve taught full-stack development, Python, SQL, database design, and Azure cloud to both beginners and working professionals. Along the way, I’ve written technical documentation for SaaS platforms across AI, blockchain, cloud infrastructure, and workplace management. I work closely with engineering teams to design content systems, organise messy information, and create docs that genuinely help people move forward.
At SmythOS, I write with both initiative and empathy. Documentation isn’t just something we check off at the end; it’s part of the product experience. Sometimes, it is the product. That’s why I think about the user before they even arrive: what they’re trying to do, where they might get stuck, and how I can help them keep going. Every section is built to reduce friction and maintain flow. I treat every page like it matters, because it does, to help the user find what they need without thinking twice.
Also, my bookmarks folder is 90 percent tutorials I’ll probably never finish… but I still label each one like it’s going to change my life (the same way I save my favourite poems).