EPISODE · Jul 17, 2026 · 10 MIN
Should Technical Writers Learn to Code? The Honest Answer
from Technical Writing Success · host Curt Robbins
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 the audience while maintaining the unique value of the writer's perspective._________________________________"It will not be AI that takes away the job of a technical writer, but rather another technical writer with deep AI skills," said Robbins. — Curt Robbins_________________________________>> Preserve your job with AI coaching from Curt Robbins: https://tinyurl.com/mr3m5fdz>> Read the Robbins article "The Year AI Went Nuclear: Six Largest M&A Deals of 2025": https://tinyurl.com/2vys3mrm>> Read the Robbins article "The Global AI Race: America vs. China": https://tinyurl.com/2uckj7wy>> Read the Robbins article "Understanding AI Hallucinations in Technical Writing": https://tinyurl.com/bdeyd64t>> Read the Robbins article "Yale Study: Impact of AI on the Job Market": https://tinyurl.com/f3cuvvxn>> Read the Robbins article "Why Large Language Models are Changing the World": https://tinyurl.com/bdfv63ca>> Read the Robbins article "Understanding Anthropic: Rising Star in AI": https://tinyurl.com/46btw22z>> Read the Robbins article "Comparing ChatGPT, Gemini, Copilot, & Grok": https://tinyurl.com/3zwttxhk>> Read the Robbins article "AI Job Replacement Fears Are Good. Here's Why.": https://tinyurl.com/p5t27t7d>> Join the LinkedIn group AI for Career Success: https://tinyurl.com/mr28u7td>> Subscribe to the Technical Writing Success podcast: https://tinyurl.com/uu9hpyzt>> Subscribe to the YouTube channel AI for Career Success: https://tinyurl.com/29t4x5xu#TechnicalWriting #documentation #AIJobs
What this episode covers
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 the audience while maintaining the unique value of the writer's perspective._________________________________"It will not be AI that takes away the job of a technical writer, but rather another technical writer with deep AI skills," said Robbins. — Curt Robbins_________________________________>> Preserve your job with AI coaching from Curt Robbins: https://tinyurl.com/mr3m5fdz>> Read the Robbins article "The Year AI Went Nuclear: Six Largest M&A Deals of 2025": https://tinyurl.com/2vys3mrm>> Read the Robbins article "The Global AI Race: America vs. China": https://tinyurl.com/2uckj7wy>> Read the Robbins article "Understanding AI Hallucinations in Technical Writing": https://tinyurl.com/bdeyd64t>> Read the Robbins article "Yale Study: Impact of AI on the Job Market": https://tinyurl.com/f3cuvvxn>> Read the Robbins article "Why Large Language Models are Changing the World": https://tinyurl.com/bdfv63ca>> Read the Robbins article "Understanding Anthropic: Rising Star in AI": https://tinyurl.com/46btw22z>> Read the Robbins article "Comparing ChatGPT, Gemini, Copilot, & Grok": https://tinyurl.com/3zwttxhk>> Read the Robbins article "AI Job Replacement Fears Are Good. Here's Why.": https://tinyurl.com/p5t27t7d>> Join the LinkedIn group AI for Career Success: https://tinyurl.com/mr28u7td>> Subscribe to the Technical Writing Success podcast: https://tinyurl.com/uu9hpyzt>> Subscribe to the YouTube channel AI for Career Success: https://tinyurl.com/29t4x5xu#TechnicalWriting #documentation #AIJobs
NOW PLAYING
Should Technical Writers Learn to Code? The Honest Answer
No transcript for this episode yet
Similar Episodes
No similar episodes found.