Month: July 2017
Why on earth would developers WANT to write documentation?
This week I was at DevOpsDays Minneapolis, which was an amazing, warm, and inclusive event. There were at least three open spaces on documentation, communication, and related problems, and I didn’t propose any of them! The question the devops world keeps asking, over and over again is, How do I get developers to write anything?…
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…
I’ve been doing Agile for too many years to feel like I’ve learned something unless I identify it with a proper retrospective. I’m about to start an FTE job, and my consulting will obviously drop way off (but not entirely). So here we go: What went well I passionately loved the independence. I could fire…
Crosspost from Opensource.com: How Do We Fix the State of Technical Documentation?
If we all agree that open source as a whole has a documentation problem, what can we do to work on addressing and fixing it? How Do We Fix the State of Technical Documentation? We have to talk about why people would be motivated to fix the problem before we can get them to do…
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,…
Full Stack Conference London
Texas Scalability Summit