Industry

img_0743

New job title: Developer Advocate

I've had a lot of job titles in my career: Technical Writing Intern Queen of Documentation (It was 2000, OK?) Technical Writer I, II, III Technical Communicator Senior Technical Writer Technical Writing Consultant Documentation Architect Documentation Mercenary You might notice a theme there. I've been a technical writer for a lot of different companies, because…

Software and pink collars

Software and pink collars

Yesterday, I said this: The real reasons we don't have docs/ux/pm bootcamps/code schools/hack days: 1) They're coded as feminine2) They pay less Code patriarchy. — Heidi @DevOpsDaysYVR (@wiredferret) July 4, 2017 And I want to come back and address it in a bit more depth, because someone called it “a bold statement”, and it is,…

Becoming a welcoming open source project, Mentoring Branch

Becoming a welcoming open source project, Mentoring Branch

Cate Huston (@catehstn) asked what we could do that would get us from “open source” on a project to “welcoming source”.  Codes of conduct, good newbie issues and good onboarding were her initial suggestions, and I said that a good project would also have a really clear goal, because one of my consistent frustrations with…

The Cardinal Virtues? of Technical Writing

The Cardinal Virtues? of Technical Writing

First, a disclaimer: Medium served me this article, but it’s a year old. Weird. Nonetheless, I have things to say about the content. The Virtues of Technical Writing, by a pseudonymous writer Introduction They are gleaned from a Bachelor of Science degree in Scientific and Technical Communication from the University of Minnesota’s Writing Studies Department,…

Upcoming appearances

Velocity Berlin
Minneapolis DevOps Meetup
DeliveryConf