Posts
-
Meeting another reader
-
Questioning assumptions
-
Release notes for smartphone apps
-
Why no blog updates for over a year
-
On dropping a stone down a well
-
Technical writers are not helicopters
-
Giving thanks
-
Feeling appreciated
-
Break's over
-
Hiring process gaffe
-
Naming for the future
-
On not telling everything you know
-
Writing-sample ethics
-
Are technical writers 'slow'?
-
Hiring process subtext and oblique signals: what's in a form?
-
In praise of the accuracy of subject matter experts
-
Five duties of a technical writer
-
Everyone knows THAT!
-
Allow me to introduce myself
TAGS: autobiography | persuasive-writing | deadlines | scheduling | communication | Agile | rules | suggestions | guidelines | duties | duty | coders | programmers | developers | software-developers | software-engineers | non-writers | experts | subject-matter-experts | SMEs | errors | mistakes | employment | hiring | job | job-search | pre-interview | recruitment | staffing | flow-state | string-review | user-interface-review | speed | slowness | samples | copyright | ethics | intellectual-property | research | screenshots | screen-shots | names | naming | parent-child | class | instance | interview | recruiter | screening | Twitter | teabag | praise | feedback | reading | gratitude |
subscribe via RSS