This document contains reflections from a technical writer expressed through short passages. It discusses the invisible nature of technical writing work, the challenges of collaborating with developers and help desks, a preference for waterfall methodologies over agile approaches, and tips for effective technical writing including choosing a voice, using short sentences, and removing unnecessary words. The technical writer introduces herself at the end.

1. Confessions of a
technical writer

2. 9.
Nobody notices
what I do
Until I fail
to do it

3. 8.
A game of scrabble
takes 4 days,
7 dictionaries,
and a duel to
the death.

4. 7.
I hate help desk
(But they love me)

5. 6.
I don’t read manuals

6. Users

7. Contributors

8. Developers

9. 5.
Working wit
developers h
i s h ar d

10. 4.
waterf a l l s
I like

11. Information
Plan
(10%)
Content
Specification
(20%)
Release
Writing
(50%)
Translation Review
& (1%)
`
`
Production
(19%)
5 Phase Model by JoAnn Hackos

12. 3.
Sometimes,
things go
BANG!

13. 2. cial
p e
s t
I’m o l
n a
’ m ci
I e
ut sp
B T
H A
T

14. Get
organised

15. Choose
your
voice

16. Say what you mean

17. Use short sentences

18. Try not to be...
A pretentious jerk

19. A word about
passive voice
(and cats)

20. Cut out the cruft

21. Read what you write

22. 1.
I will not stab you
Today.

23. My name is lanabrindley@gmail.com
Lana
Brindley.
@Loquacities
And I am a
technical
writer. 0410 500 659