Heidi Waterhouse

Heidi headshot square


Heidi has spent years in the technical communications mines, digging meaning out of words and presenting the polished results to users. She firmly believes that less is more and that no one wants to read documentation, which makes her examine her career choices and avoid wordcount trackers. She has worked in industries such as email security, musical OCR, Medicare billing, and operating systems. No matter where she goes, she still ends up writing the release notes.

Her passions include pseudonymity, the intersection of security and usability, and creating the perfect lemon pound cake. In the evenings she is writing a book on using Agile development methods in making and crafting contexts.

Open Source Bridge 2017

Proposals for this user

* The Hardest Problem in Tech(nical Interviewing) is People: The personal skills in interviewing

Technical interviews can be intimidating, but it’s easier if you have confidence in yourself and your ability to answer complicated questions. The hardest questions are not about sorting algorithms, but how you’ll work in a team, how you’ll resolve conflicts, and what it will be like to manage and work with you. This workshop exists to address the skills and theories of presenting yourself as confident, capable, and coachable.
Culture 2017-03-22 21:30:06 +0000
Carol Smith, Heidi Waterhouse

Open Source Bridge 2013

Sessions for this user

* Search-first writing for non-writers

Search-first writing makes you think about the structure of your document and product as a series of topics, instead of a big book. The days of linear documentation are over, or at least numbered. Users are much more likely to come to documentation through searches. As an open source creator, you may not have a writer to help you out with this, so how can you maximize their return on your minimal investment?
Heidi Waterhouse

Proposals for this user

* Agile Crafting

Estimating the time a project will take is pretty much the hardest thing in software, and I don't think that's any different for any other crafting deliverable. Of course, sometimes we have done something so often that we KNOW it takes 50 minutes to make a batch of raspberry jam, but that's not the same as estimation. So if we can't rely on our own estimation, or that of others, what can we do? We can timebox from the other direction. Instead of trying to figure out how long something will take, we can decide how long we have to spend on it. After all, you are the boss of your creative experiences. If you don't deliver on time, it's disappointing, but probably not the end of your career.
Hacks 2013-03-01 20:20:52 +0000
Heidi Waterhouse