1. Follow-up to 4 Technical Writing Tests Post

  2. 4 Technical Writing Tests to Screen Candidates

  3. WTD Episode 25: Researching how developers use API docs, with Andrew Head

  4. Long-term strategies for project productivity

  5. Matching documentation review practices to company culture

  6. Some specifications docs I've been working on -- and thoughts on strategies and techniques for managing specs

  7. Podcast with Jacob Moses on the Not-Boring Tech Writer: Skill #26: Getting Started with API Documentation

  8. Podcast: Dealing with Project Overload -- Strategies to Manage Overflowing Documentation Tasks

  9. Podcast: 10 myths about API documentation

  10. Expanding embedded Swagger UI instances in your docs

  11. WTD Episode 24: Conference chatter and the Australian scene, with Swapnil Ogaler

  12. WTD Episode 23: How to write inclusive tech documentation, by Lucie Le Naour

  13. An inside look at DeveloperHub -- hosted documentation portals for API docs

  14. Upcoming API Documentation Workshop in San Francisco, Calif., on November 19, 2019

  15. What I learned from organizing and running my first API documentation workshop from end to end

  16. New topic in API course: Following agile scrum with documentation projects

  17. Can you collaborate on doc projects in Git with other writers?

  18. New topic in API course: Five strategies for documenting code

  19. New topic in API course: Research on documenting code

  20. New topic in API course: Why documenting code is so difficult

  21. WTD Episode 22: Managing multiple doc projects across Git repositories, with Giles Gaskell

  22. Single-sourcing data into table templates in Jekyll

  23. Upcoming API Documentation Workshop in Mountain View, Calif., on August 30, 2019

  24. Every project is a monster you battle and slay

  25. If I am learning to write developer documentation, should GraphQL be on my radar? -- guest post by Casey Armstrong

  26. If the current trend in software development is independent agile teams, does enterprise content strategy have any chance of realistic adoption?

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

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

  29. My documentation project plan template

  30. How to avoid inefficiencies even with context switching

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

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

  33. 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?

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

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

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

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

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

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

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

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

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

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

  44. When you're in the business of complexification

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

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

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

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

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

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

  51. Results from survey about engineers who write documentation

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

  53. Biking at Alviso County Park (Santa Clara)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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