Should Technical Writers Learn to Code? The Honest Answer
About this episode
The episode discusses whether technical writers should learn to code, presenting a balanced view on the topic.
Welcome to episode 227 of the Technical Writing Success podcast from Curt Robbins, where we help you get smarter than your competition. This episode is entitled "Should Technical Writers Learn to Code? The Honest Answer." Hosts Daphne Blake and Fred Jones explore the high-stakes debate over whether technical writers should learn to code, presenting a nuanced middle ground between two polarized perspectives. While some argue that programming fluency is now a mandatory requirement for modern careers, others suggest that writers should focus on becoming developer allies rather than junior engineers. This episode clarifies that both sides actually value technical literacy, but they disagree on the specific educational path writers should take. Instead of following generic software engineering curricula, the hosts advise writers to master the technical layers that directly impact their documentation, such as Git, APIs, and data structures. By focusing on solving specific documentation blockers, writers can achieve independence and professional relevance without the burnout of traditional coding bootcamps. Ultimately, the goal is to leverage technical skills to better serve…
More episodes of Technical Writing Success
- Why Technical Writers Now Spend More Time Editing Than Writing
- The Technical Writer's Guide to Git (Without the Fear)
- How to Interview an SME Without Wasting Their Time (or Yours)
- How to Pass a Technical Writing Interview and Its Writing Test
- The Technical Writer's Portfolio That Actually Gets You Hired in 2026
- The Documentation Job Market in 2026: Where the Hiring Actually Is
Explore listener stats, chart rankings, contacts and more on the Technical Writing Success podcast page.