1. Recording of Tech Comm Trends Presentation (STC Puget Sound chapter)

  2. ClickHelp -- a flexible online platform for authoring and publishing technical documentation

  3. My documentation project plan template

  4. How to avoid inefficiencies even with context switching

  5. Reader question: Am I specializing too much by limiting my focus to docs only?

  6. Crash course in API documentation -- a one-hour video

  7. Reader question: Is it a red flag in the hiring process if they tell you that you'll be the only tech writer, with complete control over everything?

  8. Reader question: Recommended setup for docs-as-code tooling?

  9. Upcoming conference: The Tech Comm Roundup, by The Content Wrangler

  10. Season of Docs -- opportunities for both tech writers and open-source organizations to benefit from each other

  11. Technical writer position for Amazon Appstore team in Seattle or Irvine

  12. My slide links and presentation descriptions at the 2019 STC Summit

  13. The essence of technical writing, and my five stages of review for documentation

  14. First look at Document360 -- an authoring/publishing tool that satisfies both KB and tech pubs needs

  15. New video recordings of Raleigh API documentation workshop now available

  16. How I record audio and video in workshops — all the technical details, equipment, software, post-production techniques, and publishing methods

  17. Flare adds micro content feature, taking steps toward content management for AI scenarios

  18. When you're in the business of complexification

  19. Why I decided not to become a grasshopper expert, or, Not deciding your focus based on where readers are clicking

  20. A hypothesis on how to exert more influence and visibility inside the corporation

  21. Upcoming API workshops in Raleigh (April 6) and Denver (May 5)

  22. Recognizing Research Realities Across Technical Communication -- guest post by Kirk St. Amant

  23. WTD Episode 21: On career growth, leadership, and mentoring in Tech Writing

  24. Master's in technical writing at Mercer — FAQ

  25. Results from survey about engineers who write documentation

  26. My documentation takeaways from the Boeing disaster -- two essential doc questions to ask for any project

  27. Biking at Alviso County Park (Santa Clara)

  28. Should you get a degree in a tech comm program? Two considerations to keep in mind

  29. How to encourage risk-taking and idealism without falling prey to cynical attitudes born from experience

  30. XML Documentation for Adobe Experience Manager (AEM) — Integrating documentation and marketing content into a seamless whole

  31. How to design API documentation for opportunistic (active, experiential) learning styles

  32. Confronting the fear of growing older when you're surrounded by young programmers

  33. Write the Docs Podcast Episode 20: Minimum requirements for good tech docs, with Matt Reiner

  34. Corporate exodus narratives: A close look at the tension between the corporation and academia

  35. Recording and slides for my trends presentation at the Symposium for Communicating Complex Information (SCCI)

  36. Asserting your expertise as a SME in the workplace: Q&A with Jennifer Mallette and Megan Gehrke

  37. How to become a 10X technical writer in the workplace

  38. How to motivate users to provide feedback: Show that you're listening to their input

  39. Write the Docs Podcast Episode 19: Static site generators, with Jessica Parsons

  40. Recording of Trends presentation on The Content Wrangler BrightTALK channel

  41. Site analytics from Jan 1 to Dec 31, 2018 -- are more engineers writing docs now?

  42. Employment and salary outlook for technical writers based on the 2017-2018 STC Salary Database

  43. The absolute worst that can happen in 2019, or, Imagining a dystopian corporatocracy emerge after a permanent government collapse