Designing slides for developers

As a developer you're probably going to have to present something, sometime, to someone. Why not use some simple hacks to pimp out your content, and deliver a striking message.

Transcript

1. DESIGNING SLIDES FOR DEVELOPERS The good, the bad and the ugly
3. SOFTWARE
4. I don’t care It doesn’t matter
5. It just needs to be cohesive
6. COLOURS
9. PROVEN T O W O R K ON PRETTY MUCH ANYTHING
10. DESIGNING SLIDES FOR DEVELOPERS The good, the bad and the ugly DESIGNING SLIDES FOR DEVELOPERS The good, the bad and the ugly DESIGNING SLIDES FOR DEVELOPERS The good, the bad and the ugly DESIGNING SLIDES FOR DEVELOPERS The good, the bad and the ugly
11. TYPE
12. You can’t go too big
13. less with text, > MORE
14. You need to be a cyborg to read this
15. You can’t use too much contrast
16. Keep quiet, the donkeys are doing the deed
17. Keep quiet, the walruses are doing the deed
18. This slide demonstrates the no move rule
19. This slide demonstrates attention to detail
20. YOUR TYPE FORMS PART OF VISUAL HIERARCHY THE
21. class LinetagsSummaryStatusQuery def initialize(linetags, account) @linetags = linetags @account = account end def query linetags.pmap(20) { |linetag| LinetagSummaryStatusQuery.new(linetag, account).query } end private attr_reader :linetags, :account end
22. class LinetagsSummaryStatusQuery def initialize(linetags, account) @linetags = linetags @account = account end def query linetags.pmap(20) { |linetag| LinetagSummaryStatusQuery.new(linetag, account).query } end private attr_reader :linetags, :account end
23. IMAGES
24. use them
25. \o/ | / \ Heeeeeey man, I’m churchill
26. Churchill
27. Churchill
28. Churchill
29. REPETITION
30. Use ‘dividers’
31. Dividers
32. Content
33. 1 - SOFTWARE 2 - COLOURS 3 - TYPE 4 - IMAGES 5 - REPETITION RECAP
34. Thank you!
35. ! @ s i e f i @ s i g h m i n s i m o n @ p l a t f o r m 4 5 . c o m " # Q U E S T I O N S
36. fin