“I’m not technical” and other lies

No ratings

Presented at DevOpsDaysDesMoines 2019 by

Documentation should come from a place of empathy - easing someone else’s journey can enable them to do even more innovation. Documentation requires feedback and requires humility. I used to be one of those women who said “but I’m not technical.” Even after I had created technical marketing materials and guides and lead the third largest user group for AWS in North America. Done well, documentation lowers the barriers for others, foster open collaboration, and create adaptive guides for everything from process to product. Building docs always made sense to me. If I can learn it, write down steps, and then lead others through a process it’s less work for the next person. Building the docs I wanted to see helped me lay the groundwork for my own journey from a non-technical marketing specialist to a Solutions Engineer with an AWS Certified Solutions Architect Associate and enthusiastic community member. What finally made me realize that I could be technical and could confidently do technical work was documentation.