5. Audience
Who are you writing for?
Engineers looking for help on a particular topic
Engineers interested in TES's tech stack
Engineers interested in TES's way of doing things
Engineers at TES
Engineers interested in joining TES
5 / 19
6. Ideas come from your every day work. What you do is interesting.
Something new you've used / tried
A difficult problem you've solved
A technique you've used to do something others
struggle with
Your reaction to a framework / coding style / opinion
/ trend
Something you've taught someone
Something someone's taught you
6 / 19
7. Ideas come from your every day work. What you do is interesting.
An idea or mindset you'd like others to consider
A question you're considering
Defining something new / pointing out things you've
noticed
A conference or knowledge sharing talk or idea
Something you've hacked on
...
7 / 19
10. Formats
Argument for / against something
Outline an approach
Definition
Answering / asking a question
List of tips / ideas
Interview
Comparison
Proof of concept
10 / 19
12. Jot down key points
Bullet list
Mindmap
Write and then extract structure
12 / 19
13. Stuck?
Lists aren't scary
List of examples
Steps to get library X working with framework Y
7 things you need to remember when...
4 signs you're doing ... wrong
13 / 19
15. Tips
Remember you write all the time
Flesh out each key point in turn
If you get stuck on one point, move to the next
Have a spot to jot down new ideas as they come to
you
Use a tool with built-in versioning
Move things around
Don't self-censor or edit too early
15 / 19
16. Stuck?
Imagine yourself explaining to someone
Actually explain it to someone
Notice the key points you have to cover
Look at conversations you've already had on
HipChat or GitHub
16 / 19