How not to give advice (about Markdown)

A short talk given at the Sydney Ruby or Rails Meetup on 12 September, 2017

Transcript

1. How not to give advice (about Markdown) Keith Pitty @keithpitty @ConversationEDU
2. How not to give advice?
3. A story …
4. One day I was asked …
5. for advice
6. A colleague was struggling …
7. Eleanor
8. Indonesian launch
9. i18n yml
10. id.yml
12. Markdown
13. nested lists?
14. a. outer 1 i. inner 1 ii. inner 2 b. outer 2
16. Markdown
17. How could I help?
18. subset of HTML
19. type attribute
20. <ol type=“a”> <li>outer 1 <ol type =“i”> <li>inner 1 <li>inner 2 </ol> </li> <li>outer 2</li> </ol>
21. not supported by markdown
23. I was focussed
24. on Markdown
26. my advice?
27. Markdown
28. HTML
29. type attribute
31. …
33. …
35. Done!
37. merged PR
39. but then …
40. Mark
41. CSS
42. list-style
43. ul { list-style: lower-alpha; li:before { display: none; } ul { list-style: lower-roman; } }
44. CSS + Markdown
48. I apologised
49. profusely!
50. time to reflect
51. Where had I gone wrong?
53. tunnel vision?
54. lateral thinking?
55. comfort zone?
56. tools?
57. Teamwork?
59. learning opportunity
60. next time …
61. meanwhile …
62. Teamwork!
63. @conversationEDU
64. @keithpitty