The Seven Righteous Fights

Transcription

1 The Seven Righteous Fights You Should Be Fighting

2 Heidi Waterhouse LISA 2016

3 Definition of a Technical Writer: A master of assembling technical clues into a narrative whole

4 This truck is stuck in the mud

5

6 Example

7 Tower of translation Babel

8 5 days Plus two weeks

9 Fingers crossed

10 You cannot fix it later

11

12 The Seven Righteous Fights Localization Security Extensibility Documentation Affordance Acceptance Accessibility

13 Localization Localisation

14 Localization Don't hard code interface elements No words in logos or images Bake in extended character support

15 Security

16 The most successful hackers actually look like auditors

17

18 Security is neither cheap nor easy, But it beats the alternative

19 Encryption

20

21

22 Stop saying that word!

23 Extensibility

24

25

26 Documentation

27 Documentation is not state secrets Documentation is subtle self promotion

28 User Documentation Cupcake ipsum dolor sit amet icing. Lemon drops soufflé gummies danish dragée pastry chupa chups brownie. Cheesecake liquorice cake.

29 Developer onboarding

30 Production scripts and build sequence

31 Secretive build engineers are bad build engineers

32

33 Affordance

34

35 Some people have more privileges

36 Homunculus of sensation

37 Acceptance

38 Not all Legos have the same job

39 Shhhhhh Explain nothing

40 If you can't hire an expert, become a student.

41 Accessibility

42

43

44 8% of men are colorblind

45 Click here. Link. Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link.Click here. Link Screen reader links

46

47 TAB Temporarily Able-Bodied

48 Now what?

49 Tactics Do what you can Start where you are. Use what you have. Do what you can - Arthur Ashe

50 Tactic 1 Write a coding style guide and follow it.

51 Tactic 2 Pair programming for best practices.

52 Tactic 3 Host brown bag lunches.

53 Tactic 4 Ask questions.

54 Tactic 5 Add tests for accessibility and usability.

55 Tactic 6 Learn to write ROI documents.

56 Tactic 7 Cultivate inclusion, diversity, and representation.

57 Money is the root of all business decisions

58 The Seven Righteous Fights Localization - Make users comfy Security - Make users safer Extensibility - Make code usable Documentation - Disaster-proof Affordance - Nudge good behavior Acceptance - Test with users Accessibility - Include people

59 tl;rt Don't build in compounding technical debt that you could trivially avoid.

60 Be productively lazy.

61 Credits Copyright ceridwen and licensed for reuse under this Creative Commons Licence By Dori (Own work) [Public domain], via Wikimedia Commons By Ken Teegardin from Boulder, Boulder (Piggy Bank On Pennies) [CC BY-SA 2.0 ( via Wikimedia Commons By Evan-Amos (Own work) [CC BY-SA 3.0 ( via Wikimedia Commons By Lasart75 (Own work) [GFDL ( or CC BY-SA ( via Wikimedia Commons By Jonathan Joseph Bondhus (Own work) [CC BY-SA 3.0 ( via Wikimedia Commons By Jojhnjoy (Own work, based on the work of Anders) [Public domain], via Wikimedia Commons By User:Bryan Derksen (Own work) [Public domain], via Wikimedia Commons By Jericho [CC BY 3.0 ( via Wikimedia Commons By Bill Bertram (Own work) [CC BY-SA 2.5 ( via Wikimedia Commons Joshua Reynolds [Public domain], via Wikimedia Commons