Summary: There is a romance to technical communication, because there is a romance to all useful things. But don’t expect the romance of technical communication to be apparent to everyone. Technical communication is a romantic profession. No, really. There is a romance to any profession if you love it. But why would anyone love a… Read More »
During my recent Webinar with MadCap (recording here), I said something in response to a question that the twitterverse took to: "It's not documentation's job to repeat what the UI is saying. The UI is techcomm." Preach, @mbakeranalecta! #techcomm — Karen Mulholland (@kemulholland) August 27, 2014 After Karen tweeted it, it bounced around for quite… Read More »
The best job I ever had spanned the full spectrum of technical communication. In a response to a comment in a discussion related to my post Content Engineering is not Technical Writing, Scott Abel said: Who cares what tech writers do. There’s no future (read: great paying careers) in documenting things. That ship sailed a… Read More »
Content jobs are never strictly defined because they are the mortar that holds the bricks of the enterprise together. I’m attending LavaCon, and here, as everywhere, content people are debating the definition of their roles, the names of those roles, the boundaries and intersects between them, and the responsibilities and qualifications pertinent to them. Newer… Read More »
The discussion around Larry Kunz recent blog post The Salt of the Earth raises some interesting questions about the part that those of us who call ourselves “Technical Writers” (or some cognate thereof) can and should play in the wider world of technical communication. In the comments, Larry says: As technical communicators, we need to… Read More »