The Not-Boring Tech Writer

Kate Mueller
  • 4.9 (14)
  • CAREERS
  • UPDATED MONTHLY

Some people hear the phrase "technical writing" and think it must be boring. We're here to show the full complexity and awesomeness of being a tech writer. This podcast is for anyone who writes technical documentation of any kind, including those who may not feel comfortable calling themselves tech writers. Whether you create product documentation, support documentation, READMEs, or any other technical content—and whether you deal with imposter syndrome, lack formal training, or find yourself somewhere in the gray area between technical communications and general writing—there's a place for you here. Each month, we publish two episodes: an interview with an amazing guest focusing on useful skills or tools that can help you improve your tech writing skills, and a behind-the-scenes solo episode with host Kate Mueller about what she’s working on, struggling with, or thinking about in her daily tech writing life. The Not-Boring Tech Writer is generously sponsored by KnowledgeOwl, knowledge base software built for people who care, by people who care.

  1. SEP 4

    Yoga wisdom for technical writers with Sarah Walker

    🎓 Our host, Kate Mueller, is teaching a 4-session Information Architecture Master Class that starts on September 16th! 🎧 TNBTW listeners can use the coupon code "NOTBORING" during checkout to save 40% off the list price! 🔗 Read more info and sign up: thenotboringtechwriter.com/learning — In this episode, I talk with Sarah Walker, a technical writer and yoga instructor, about how yoga principles like establishing foundations, respecting people’s time, and embracing practice over perfection can transform your approach to technical writing and help you create more mindful, user-centered documentation. Sarah and I discuss her path into technical writing, which began with yoga instructor training where she discovered how much she enjoyed breaking down complex processes into foundational steps. This experience taught her that effective instruction—whether for yoga poses or technical procedures—requires understanding your audience's needs and building from core principles. We explore how yoga's emphasis on establishing solid foundations directly translates to documentation, where starting with fundamental concepts helps both beginners learn and experienced users refresh their understanding. We explore the yoga principle of Asteya (non-stealing), particularly how it applies to respecting readers' time and attention. Sarah explains how this philosophy shapes her approach to writing clear, concise documentation that helps users efficiently get to their goals. We discuss practical applications like using consistent style guidelines to reduce cognitive load and being mindful of which content is essential to include in your docs. Our conversation also covers how yoga's concept of practice over perfection applies to technical writing careers. Sarah shares how documentation evolves alongside products and why embracing this constant change rather than striving for perfect static content leads to better outcomes. We explore the parallels between sequencing yoga poses and sequencing information in documentation, the importance of observing your audience's needs, and how both practices require patience, self-compassion, and continuous learning. About Sarah Walker: Sarah's been writing and crafting stories since she was able to put pencil to a Peanuts 3x5 top-spiral memo pad and record her stories in her own scribbly alphabet. Since personal alphabets scribbled on tiny pieces of paper don't pay the rent, she embarked on her career as a professional writer and editor after graduating from St. Edward's University (Austin, TX) in 1998. As an industry editor with Hoover's for roughly seven years, she covered biotech, pharmaceuticals, health care systems, venture capital, investment firms, and other sectors as a member of the Finance and Health Care editorial team. She earned her Austinite bone fides by getting hired by and, 18 months later, laid off by Dell, where she served as a technical editor for the Global Technical Training and Curriculum Team for products and software for consumers as well as small and midsize businesses. Thanks to the Great Recession and other market forces and personal demands, she bounced around a bit from writing and editing features, self-help book summaries, U.S. Pharmacopeia monographs, and other technical-ish content. She began her technical writing career in earnest at Libre Digital, where she spent much of the second decade of the 21st century documenting procedures for processing various magazine titles as well as a platform for book publishers to distribute their titles to digital marketplaces. After a two-year stint as the managing editor (and lone full-time, non-contract employee) of a local bimonthly magazine targeting affluent residents of "West Austin," at long last (in August 2020), Sarah landed a job that gave her the Technical Writer job title, and she's been writing about the Monetate platform ever since. Sarah's second career as a yoga instructor (and briefly a Pilates mat instructor) began in 2005, after she completed her 250-hour instructor training with Yoga Yoga (now defunct, just like the college in Santa Fe, NM that she attended for the first two years of her undergrad studies). She taught part-time until 2012, when primary job demands and other responsibilities forced her to give it up. Resources discussed in this episode: Garbl’s Writing CenterOn Writing: A Memoir of the Craft by Stephen KingSarah’s Elect a Raccoon Overlord article Join the discussion by replying on Bluesky — Contact The Not-Boring Tech Writer team: We love hearing your ideas for episode topics, guests, or general feedback: Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBluesky Contact Kate Mueller: knowledgewithsass.comLinkedInBluesky Contact Sarah Walker: Bluesky Contact KnowledgeOwl: knowledgeowl.comLinkedIn

    53 min

  2. AUG 21

    Kate sounds off on cognitive capital and learning

    🎓 Our host, Kate Mueller, is teaching a 4-session Information Architecture Master Class that starts on September 16th! 🎧 TNBTW listeners can use the coupon code "NOTBORING" during checkout to save 40% off the list price! 🔗 Read more info and sign up: thenotboringtechwriter.com/learning — In this solo episode, Kate shares an update on her content update progress. She also reflects on Manny Silva’s interview (S3:E14), Ryan Macklin’s interview (S3:E16), and Liz Argall’s interview (S3:E13) and the importance of learning even when we don’t have explicit reasons to do so. I’ve continued my work to update the KnowledgeOwl Support Knowledge Base to align with major navigation and UI changes that were rolled out in December. I updated an additional 15 articles since my last episode, taking my total to 565. 🎉This month’s velocity was a lot lower thanks to prepping for, teaching, and attending KnowledgeOwl’s July 2025 Summer Camp workshop series. While teaching the classes was fun, it also triggered a lot of issues with my chronic illness, so I finished the month quite depleted on every level. This made me think a lot about the ambient and acute stress Ryan and I discussed in relation to empathy advocacy, and about how all documentation makes demands on readers’ cognitive capital. I share five documentation techniques that helped me get use from docs when I was struggling the most cognitively: Provide a summary, synopsis, TL;DR, or 1-2 context-setting sentences at the start of a doc or each section.Use strong page titles and headings, avoiding general catch-alls like “Frequently Asked Questions.”Format your content consistently using semantic elements like sequential headings.Use callouts, warnings, or admonitions sparingly but in consistent ways.Practice screenshot restraint. I also reflect on how tricky it is to actually accommodate learning as a tech writer if I don’t have a pressing need for it. We learn new tools or domains often since it’s required. We learn new tooling or scripting to make our lives easier or because it’s required. We attend classes, conferences, or certifications. But we often don’t take time on less formal, bigger picture learning. I share how doing research to teach a class on style guides led me to find all kinds of flaws and oversights in my existing style guide. I challenge all of us to carve out 2-4 hours in the next month to dig deep on a best practice or concept we want to learn more about. If you lack the time or discipline and have a professional development budget, you can also consider joining me for the Information Architecture Master Class I’m teaching in partnership with KnowledgeOwl in September and October. Use discount code NOTBORING. Resources discussed in this episode: KnowledgeOwl Support Knowledge BaseOur upcoming Information Architecture Master Class Join the discussion by replying on Bluesky — Contact The Not-Boring Tech Writer team: We love hearing your ideas for episode topics, guests, or general feedback: Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBluesky Contact Kate Mueller: knowledgewithsass.comLinkedInBluesky Contact KnowledgeOwl: knowledgeowl.comLinkedIn

    23 min

  3. AUG 7

    Empathy advocacy: Designing docs for all emotional states with Ryan Macklin

    🎓 Our host, Kate Mueller, is teaching a 4-session Information Architecture Master Class that starts on September 16th! 🎧 TNBTW listeners can use the coupon code "NOTBORING" during checkout to save 40% off the list price! 🔗 Read more info and sign up: thenotboringtechwriter.com/learning — Learn how Ryan Macklin's "empathy advocacy" framework helps you design documentation that works for users in all emotional states (e.g. anxious, frustrated, exhausted, and curious/distractible) rather than assuming everyone comes to your docs in a perfect state of clarity. Ryan and I discuss his unique path into technical writing, starting from his early computer hacking days and role-playing game writing background. Ryan explains how writing and editing tabletop games taught him that documentation is harder than technical writing because it requires creating user interfaces for "disconnected, squishy brains" while making content engaging enough that users won't simply abandon it for alternatives. This experience, combined with his personal journey through therapy and understanding neurodiversity, eventually led him to develop the empathy advocacy framework. Our conversation centers around Ryan's empathy advocacy concept, which focuses on writing for users who aren’t calm. These users might be in four key cognitive states: anxious, frustrated, exhausted, and curious/distractible. Rather than designing documentation for the "happy path" or optimal users, Ryan advocates for considering people who may be dealing with high ambient stress, acute stress from urgent problems, cognitive depletion, or distractibility. The "stupid users" developers complain about are often just busy, stressed people whose brains aren't optimally processing information. We explore practical applications of empathy advocacy concepts, including strategic screenshot reduction to minimize cognitive load, restructuring and tightly scoping FAQs to avoid information architecture problems, and understanding that every element in documentation has a "tax" on your user’s mental energy. The episode also includes practical advice on social capital management, documentation stewardship, and the importance of "failing forward" rather than getting stuck in perfectionism. About Ryan Macklin: Ryan splits his cerebral time between tech writing, UXing, coding, and game design. By day, Ryan writes and edits software and hardware requirements. Otherwise, he works on game or tooling projects, light woodworking, and land improvement projects on his homestead in southern Michigan. Warning: Ask him about UX in games, and he may talk your ear off. Resources discussed in this episode: empathyadvocacy.orgRyan Macklin talk: WTD ECQ Nov '22: 7 doc techniques rooted in empathy advocacyRyan Macklin talk: How to avoid "toxic tennis" — empathy in user communicationOther technical communication talks by Ryan Macklin Join the discussion by replying on Bluesky — Contact The Not-Boring Tech Writer team: We love hearing your ideas for episode topics, guests, or general feedback: Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBluesky Contact Kate Mueller: knowledgewithsass.comLinkedInBluesky Contact Ryan Macklin: Ryan's newsletter: buttondown.com/ryanmacklinmacklin.ccLinkedInBluesky Contact KnowledgeOwl: knowledgeowl.comLinkedIn

    53 min

  4. JUL 24

    Kate sounds off on “good” documentation

    🎓 Our host, Kate Mueller, is teaching a 4-session Information Architecture Master Class that starts on September 16th! 🎧 TNBTW listeners can use the coupon code "NOTBORING" during checkout to save 40% off the list price! 🔗 Read more info and sign up: thenotboringtechwriter.com/learning — In this solo episode, Kate shares an update on her content update progress. She also reflects on Nick Graziade’s interview (S3:E12) and Liz Argall’s interview (S3:E13) and the ways these interviews highlight some elements of “good” docs experiences.I’ve continued my work to update the KnowledgeOwl Support Knowledge Base to align with major navigation and UI changes that were rolled out in December. I updated an additional 43 articles since my last episode, taking my total to 550. 🎉 I’m in the middle of updating our Contextual Help Widget documentation—one of the features I’ve been putting off updating—and I’ve been drafting content for our forthcoming AI Chatbot feature, too. Nick and I share a tech writer villain origin story of absolutely adoring LEGO documentation, and it’s gotten me curious how many other tech writers also have this early exposure to documentation. And for some reason I’m seeing tech writing everywhere. I share a detailed story of Bont Cycling’s online shoe fit guidance, which I recently used and which has created a fairly positive product experience for me. Good documentation experiences can help create good product experiences. I also reflect on Liz’s comment that “The best fertilizer is the gardener’s shadow.” She talked about this in the context of just showing up to work on docs, but I extend that metaphor to say showing up working with care. I gave two examples of this. I’ve been struggling with some personal losses, so a lot of my docs work lately has been a blitz of low-hanging docs fruit: a lot of small changes and improvements. None of these updates are substantive, but they’re good iterative improvements and they helped me get back into docs work. I also share a story of building a long-procrastinated-on bench for my entryway, which was more about accepting good rather than great just to get something built. Good docs are dynamic and iterative–they may not be perfect at first, but they’re constantly improving and always striving for a better reader experience. Resources discussed in this episode: Our new merch store!KnowledgeOwl Support Knowledge Base, especially the Contextual Help Widget documentationBont Cycling Shoe Size Finder (The docs I referenced in the episode are hyperlinked in the Print Sizing Page section.) Join the discussion by replying on Bluesky — Contact The Not-Boring Tech Writer team: We love hearing your ideas for episode topics, guests, or general feedback: Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBluesky Contact Kate Mueller: knowledgewithsass.comLinkedInBluesky Contact KnowledgeOwl: knowledgeowl.comLinkedIn

    25 min

  5. JUL 10

    Docs as Tests: Keeping documentation resilient to product changes with Manny Silva

    🎓 Our host, Kate Mueller, is teaching a 4-session Information Architecture Master Class that starts on September 16th! 🎧 TNBTW listeners can use the coupon code "NOTBORING" during checkout to save 40% off the list price! 🔗 Read more info and sign up: thenotboringtechwriter.com/learning — In this episode, I'm talking with Manny Silva, a technical writer who created the "Docs as Tests" concept name and the open-source tool Doc Detective. We discuss how to automatically test your documentation for accuracy, why customer reports of broken docs are actually failed tests, and practical ways to implement automated documentation testing regardless of your tech stack.Manny and I discuss his background as someone who intentionally chose technical writing as a career path, starting with early exposure to computers through his mother's work and developing into roles at Apple, Google, and now Skyflow as Head of Documentation. We explore the core concept behind Docs as Tests—that documentation contains testable assertions about how a product should work, and that customer reports of broken procedures are essentially failed tests that we should catch proactively rather than reactively. We dive deep into how Manny's strategy works in practice, from the "cupcake to wedding cake" approach of starting small and scaling up. We dig into two different approaches to the technical implementation: creating “detected” tests using Doc Detective, which reads the docs directly and uses them as tests, and creating standalone tests in testing tools like Playwright or Cypress, which you’d create and update independently of the docs. Manny explains how his Doc Detective tool can parse markdown documentation, automatically execute the steps described in procedures, capture screenshots for visual regression testing, and even validate API responses against OpenAPI schemas. We discuss the business case for automated documentation testing, including how it prevents customer frustration, builds trust, reduces support overhead, and can catch bugs before they reach production. Throughout our conversation, we explore practical implementation strategies, including how to sell the approach to stakeholders, integrate testing into CI/CD pipelines, handle multifactor authentication challenges, and work with QA teams. Manny also shares his philosophy of creating a "zero trust" relationship between docs and product—not out of disrespect, but to ensure everyone stays honest about the behavioral contract that documentation represents. Docs as Tests also encourages technical writers to embrace their unofficial QA role–as writers, we’re often the first to test a new feature or product, and embracing a Docs as Tests mindset can help legitimize and make visible this role. About Manny Silva: Technical writer by day, engineer by night, and father everywhere in between, Manny wears many (figurative) hats. He's passionate about intuitive and scalable developer experiences, and he likes diving into the deep end as the 0th user. Here are a few things that keep him busy: Head of Docs at Skyflow, a data privacy vault company.Codifier of Docs as Tests, a tool-agnostic strategy for keeping docs and their products in sync by using doc content as product tests.Creator and maintainer of Doc Detective, an open-source doc testing framework.AI development and experimentation.He's always looking for collaborators on projects, and he loves chatting with folks, so don't hesitate to reach out. Resources discussed in this episode: Docs as Tests: A Strategy for Resilient Technical Documentation - Manny's bookDocs as Tests blog - Manny's blog about the strategy and various toolsDoc Detective - Manny's open source tool for testing and validating documentationDoc Detective GitHub action - Official GitHub action for CI/CD integrationDoc Detective Discord server - Public community for users implementing Docs as TestsGood to Great book series - Business development books that Manny recommendsFramework laptop - Repairable laptop that Manny built with his childrenVale - Style guide enforcement tool (mentioned as complementary to Docs as Tests)Playwright - Engineering-level testing tool used by some companies like DockerCypress - Another engineering-level testing toolBen Perlmutter - Unit Test the Docs: Why You Should Test Your Code Examples - A Write the Docs Portland 2022 talk about MongoDB's unit testing documentation approachArazzo specification - Newer OpenAPI initiative specification for workflow testing — Contact The Not-Boring Tech Writer team: We love hearing your ideas for episode topics, guests, or general feedback: Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBlueskyJoin the discussion by replying on Bluesky Contact Kate Mueller: knowledgewithsass.comLinkedInBlueskyContact Manny Silva: Doc DetectiveLinkedIn Contact KnowledgeOwl: KnowledgeOwl.comLinkedIn

    1h 5m

  6. JUN 26

    Connecting permaculture and documentation with Liz Argall

    🎓 Our host, Kate Mueller, is teaching a 4-session Information Architecture Master Class that starts on September 16th! 🎧 TNBTW listeners can use the coupon code "NOTBORING" during checkout to save 40% off the list price! 🔗 Read more info and sign up: thenotboringtechwriter.com/learning — In this episode, I’m talking with Liz Argall, a writer I connected with at Write the Docs Portland 2025. We talk about working on open source projects, developing good qualitative metrics, her work with a permaculture nonprofit in Uganda, and the ways that being interviewed by a technical writer can make hidden expertise shine.Liz and I presented in the same Lightning Talk session at Write the Docs Portland 2025 and subsequently discovered a shared love for spreadsheet tools, qualitative metrics, and permaculture. We discuss her work on Project Aria, a combination of hardware, software, and data collection geared toward solving the problems that augmented reality will need to address. Liz stresses the point of writing for poorly informed and/or sleep-deprived audiences. We also discuss the importance of qualitative metrics and some of Liz’s favorite qualitative metrics that help capture the story of the documentation, including impact and saving engineers’ and SMEs’ time. Liz also tells us about her involvement with Ngombor Community Development Alliance, a non-profit focusing on permaculture development in the West Nile region of Uganda. We also discuss how sometimes just showing up for something–including showing up to work on your docs–has far more impact than we realize. About Liz Argall: Liz Argall creates empowering documentation and processes; where you need it, when you need it. She’s a technical writer, program manager, author, and trainer who delivers humanizing, data informed, accessible, and technically complex projects for a range of organizations, from Fortune 500 companies to a community development organization in Uganda. In a past life, she was a professional artist talent scout and she’s still a professional member of SFWA (now called the Science Fiction and Fantasy Writers Association). She’s a graduate of Clarion Writers Workshop, has been critiqued by multiple New York Times best selling authors, and has critiqued the stories of multiple award winning authors, which is a long way of saying that she likes to give a good portfolio critique! Resources discussed in this episode: Project AriaFabrizio Ferri Benedetti’s Why I became a Documentation Engineer (and what that even means): The source for the phrase “technical therapist”Write the Docs Portland 2025, Lightning Talk session 1Liz's portfolio siteIntroduction to search term analysis: Liz’s blog post about the Lightning Talk she gave, which includes links and instructions for her spreadsheetAttend to the work: A blog post by Liz where she alks about permaculture and Diataxis in the context of technical writingDiátaxis as a guide to workLucy Mitchell's websiteUbuntu Summit 2024 | Open source software between Africa and the West: The YouTube presentation that inspired Liz to get in touch with VinceNgombor Community Development Alliance: a non-profit focusing on permaculture development in the West Nile region of UgandaNgombor Community Development Alliance's sponsor a tree (or chicken) page — Contact The Not-Boring Tech Writer team: We love hearing your ideas for episode topics, guests, or general feedback: Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBlueskyJoin the discussion by replying on Bluesky Contact Kate Mueller: knowledgewithsass.comLinkedInBlueskyContact Liz Argall: Liz's website: includes her blog, which has several awesome spreadsheet matrices you can copy and use for yourselfLinkedInBlueskyContact KnowledgeOwl: KnowledgeOwl.comLinkedIn

    48 min

  7. JUN 12

    Documentation as a creative endeavor with Nick Graziade

    🎓 Our host, Kate Mueller, is teaching a 4-session Information Architecture Master Class that starts on September 16th! 🎧 TNBTW listeners can use the coupon code "NOTBORING" during checkout to save 40% off the list price! 🔗 Read more info and sign up: thenotboringtechwriter.com/learning — In this episode, I'm talking with Nick Graziade, a technical writer and musician who approaches documentation as a creative endeavor. We explore how his early fascination with Lego instructions and synthesizer manuals shaped his philosophy that technical writing doesn't have to be dry or boring, but can be passionate and innovative work that adapts to different audiences and embraces impermanence.Nick shares his two-part "villain origin story" that led him to technical writing. The first part involves his childhood fascination with Lego instructions, which taught him that visual documentation could guide complex building without narration. The second part comes from his music school experience with synthesizers, where he discovered that the best manuals—like those from Moog—don't just explain how to do something, but also why. This combination of visual clarity and deeper understanding became his template for approaching technical documentation. We dive deep into the concept of using different "grammars" for different audiences, drawing from Wittgenstein's language games. Nick emphasizes that effective technical communication requires understanding what assumptions you can make about your readers and adapting your language accordingly. We explore how consistency in style and formatting reduces cognitive load for users, and how deliberately breaking those patterns can create powerful contrast for important information like warnings or alerts. Throughout our conversation, Nick reflects on his philosophy of embracing impermanence in documentation. Rather than being frustrated by constant updates and revisions, he sees the evolving nature of technical writing as aligned with his Buddhist-influenced worldview. We discuss practical approaches to managing documentation workflows, including his use of quarterly revision cycles, just-in-time updates based on development sprints, and how he determines when something is "done enough" to move on to the next priority. About Nick Graziade: Nick is a Senior Technical Writer, instructional designer, knowledge management expert, musician, and philosopher from Upstate New York's Capital District. When not obsessing over the nuances of a web page's navigation sidebar, you can likely find him playing gigs as a professional bassist or practicing Japanese sword arts. Resources discussed in this episode: Moog Music user manuals: https://www.moogmusic.com/downloads/ — Contact The Not-Boring Tech Writer team: We love hearing your ideas for episode topics, guests, or general feedback: Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBlueskyJoin the discussion by replying on Bluesky Contact Kate Mueller:  knowledgewithsass.comLinkedInBlueskyContact Nick Graziade: nicholas.graziade@gmail.comContact KnowledgeOwl: KnowledgeOwl.comLinkedIn

    52 min
  8. Kate sounds off on Write the Docs

    MAY 29

    Kate sounds off on Write the Docs

    🎓 Our host, Kate Mueller, is teaching a 4-session Information Architecture Master Class that starts on September 16th! 🎧 TNBTW listeners can use the coupon code "NOTBORING" during checkout to save 40% off the list price! 🔗 Read more info and sign up: thenotboringtechwriter.com/learning — In this solo episode, Kate shares an update on her content update progress. She also reflects on Sue Brandt’s interview (S3:E10) and on the Write the Docs Portland 2025 conference.I’ve continued my work to update the KnowledgeOwl Support Knowledge Base to align with major navigation and UI changes that were rolled out in December. I updated an additional 50 articles since my last episode, taking my total to 507. 🎉Most of the updates this month were in our payment and plan-related documents, which needed to be updated for a new Billing page user interface and to include changes from migrating to a Merchant of Record. My velocity this month was lower thanks to teaching KnowledgeOwl’s Authoring 101 class and attending the Write the Docs Portland 2025 conference with Chad. Write the Docs is always a deeply inspiring conference for me, and this was my first time attending in person since 2019. This year, I even gave a lightning talk about dogs and docs, too! Much of the episode is spent reflecting on the six things I most love about Write the Docs, which include its support for first-time attendees and presenters, the flexibility and thoughtfulness of its design, and the amazing community of documentarians who form the backbone of this community. This year’s conference had a fantastic selection of talks and speakers, including several previous and upcoming podcast guests. Resources discussed in this episode: KnowledgeOwl Support KB: the Payments & subscriptions and Plans & pricing categoriesWrite the Docs Portland 2025 conferenceKate’s Of docs and dogs lightning talkFull playlist of recorded talks from Write the Docs Portland 2025 — Contact The Not-Boring Tech Writer team: We love hearing your ideas for episode topics, guests, or general feedback: Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBlueskyJoin the discussion by replying on Bluesky Contact Kate Mueller:  knowledgewithsass.comLinkedInBlueskyContact KnowledgeOwl: KnowledgeOwl.comLinkedIn

    29 min
See All (60)

Ratings & Reviews

4.9
out of 5
14 Ratings

About

Some people hear the phrase "technical writing" and think it must be boring. We're here to show the full complexity and awesomeness of being a tech writer. This podcast is for anyone who writes technical documentation of any kind, including those who may not feel comfortable calling themselves tech writers. Whether you create product documentation, support documentation, READMEs, or any other technical content—and whether you deal with imposter syndrome, lack formal training, or find yourself somewhere in the gray area between technical communications and general writing—there's a place for you here. Each month, we publish two episodes: an interview with an amazing guest focusing on useful skills or tools that can help you improve your tech writing skills, and a behind-the-scenes solo episode with host Kate Mueller about what she’s working on, struggling with, or thinking about in her daily tech writing life. The Not-Boring Tech Writer is generously sponsored by KnowledgeOwl, knowledge base software built for people who care, by people who care.

Information

  • Creator
    Kate Mueller
  • Years Active
    2016 - 2025
  • Episodes
    60
  • Rating
    Clean
  • Copyright
    © 2016-2025 KnowledgeOwl
  • Show Website
    The Not-Boring Tech Writer

You Might Also Like