From Python to Technical Writing: A Cloud-Native Documentation Journey with Michael Uzukwu
Released Wednesday, July 15th 2026·28 min
Show notes
About this episode
In this episode of Knowledge Base Ninjas, host Gowri Ramkumar speaks with Michael Uzukwu, Lead Technical Writer at Opsimate and a 2026 LFX mentee for kgateway, about his unconventional path into technical writing. Michael shares how he started as a Python programmer exploring data analytics before discovering that documenting his projects — not the analysis itself — was what he truly enjoyed.
He explains which analytics skills transferred most usefully into writing, namely structuring information and rigorous attention to detail, and why they underpin strong information architecture. Michael also unpacks what makes cloud-native documentation distinct, from its expert audience of SREs and platform engineers to the fast-moving tooling built on Kubernetes. On AI, he shares that it has already reshaped how docs are written, retrieved, and consumed, while insisting humans remain the essential validators against hallucination.
He closes with resource recommendations, an explanation of LFX mentorships, and encouragement for aspiring writers to simply start.
Thank you for tuning in!
In the meantime, if you're ready to explore Document360, a knowledge base platform that can help your customers and teams get instant answers, we’d love to invite you to try it first-hand.
Simply use this link - https://bit.ly/4ktBnZZ to start your free trial.
In this episode of the Knowledge Base Ninjas podcast, Gowri Ramkumar speaks with Mikhail Ostrogorskiy, an independent technical communication consultant and researcher, about professional standards in technical writing and their role in defining the profession.
Mikhail discusses how professional standards help technical writers understand their roles, identify their skills, and communicate their value within organizations. The conversation explores how technical writing goes beyond creating documentation. It highlights the role of knowledge management, career development, and collaboration within professional communities.
They also discuss how standards can support automation and how the role of technical writers is evolving with AI. Mikhail shares insights into the Armenian technical-writing community and its efforts to develop professional standards for the field.
Thank you for tuning in!
In the meantime, if you're ready to explore Document360, a knowledge base platform that can help your customers and teams get instant answers, we’d love to invite you to try it first-hand.
Simply use this link - https://bit.ly/4ktBnZZ to start your free trial.
In this episode of Knowledge Base Ninjas, Suzanne Rubinstein, a technical writer at TruLogix Software, shares her unconventional journey into technical writing and the mindset that has shaped her career.
Suzanne discusses her transition from government, tourism, and education into technical writing, driven by her curiosity about technology and her ability to explain complex concepts. She explains why curiosity is essential for technical writers, who constantly learn new products, industries, tools, and processes.
The conversation explores the importance of learning by doing. Suzanne shares why she prefers to reproduce a process herself before documenting it, rather than relying solely on subject matter experts. She also discusses burnout, the value of experience, and why understanding your audience is essential to creating useful documentation.
Thank you for tuning in!
In the meantime, if you're ready to explore Document360, a knowledge base platform that can help your customers and teams get instant answers, we’d love to invite you to try it first-hand.
Simply use this link - https://bit.ly/4ktBnZZ to start your free trial.
In this episode of the Knowledge Base Ninjas podcast, host Gowri Ramkumar speaks with Ryan Young, Staff Technical Writer at Stripe, about the fundamentals of technical writing and how they continue to matter in an evolving technology landscape.
Ryan shares his journey into technical writing and explains why clarity, conciseness, and understanding the reader remain essential, regardless of the tools writers use. He also discusses writing for different stages of the user journey, using progressive disclosure, and refining documentation based on real user feedback.
The conversation also touches on AI and LLMs. Ryan believes these tools have powerful use cases, but writers should not outsource their thinking to them. For him, writing is part of the thinking process itself. Human judgment therefore remains essential to producing clear and useful documentation.
Thank you for tuning in!
In the meantime, if you're ready to explore Document360, a knowledge base platform that can help your customers and teams get instant answers, we’d love to invite you to try it first-hand.
Simply use this link - https://bit.ly/4ktBnZZ to start your free trial.
In this episode of the Knowledge Base Ninjas podcast, Gowri Ramkumar speaks with James Beach about how he approaches technical writing from a reader's perspective. James builds a persona for the target user before writing a single word, often testing the product himself through their eyes. Documentation, for him, is written for someone who's already frustrated and just wants a quick answer. He explains how storytelling and narrative thinking quietly shape the way he structures troubleshooting guides and walkthroughs. Getting something wrong is treated as discovery, not failure, and that mindset shapes how his teams grow. James also walks through how he'd approach documenting a completely unfamiliar product for users he's never met, by building a persona and picking a specific use case he can personally relate to.
Thank you for tuning in!
In the meantime, if you're ready to explore Document360, a knowledge base platform that can help your customers and teams get instant answers, we’d love to invite you to try it first-hand.
Simply use this link - https://bit.ly/4ktBnZZ to start your free trial.
In this episode of Knowledge Base Ninjas, host Gowri speaks with Gareth Brinn, Documentation Manager at Gravitee, about what changes in a documentation team when AI enters the workflow.
Gareth says that AI is an optimisation tool, not a replacement. He reframes manual documentation as manual context building: understanding user journeys, talking to solutions engineers and support teams, and structuring information so agents can use it. Human-generated content, he argues, is AI-optimised content — if docs read well to an AI, it's because someone did the manual work to get them there.
He explains why the "one agent to rule them all" idea fails, and why he builds chunked, node-based workflows with a human backup at every break point. On making docs AI-readable, his advice is that the craft hasn't changed: plain language, topic-based writing, self-contained pages — and now self-contained paragraphs.
He also covers governing decentralised content production, why quality beats speed in AI workflows, and his rapid-fire picks for technical writers.
Thank you for tuning in!
In the meantime, if you're ready to explore Document360, a knowledge base platform that can help your customers and teams get instant answers, we’d love to invite you to try it first-hand.
Simply use this link - https://bit.ly/4ktBnZZ to start your free trial.
This podcast, its content and its artwork are not owned by, affiliated with, or endorsed by Castquire.
