Based in Cambridge, Pythonista for about a decade. Professionally interested in natural language and data mining, unprofessionally interested in experimental music, beer and mountains. Head of R&D at Transversal.
The best advice I've been given on technical communication is "understand what you want to achieve before you think about what you want to say". I'm going to discuss why I think this is important, with examples ranging from planning meetings to writing documentation.