Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Why bother with code?

Why bother with code?

Code is scary. Code is hard. Code is worthwhile.

In an increasingly technical world, it’s hard to escape the apparent dominance of code—and, more broadly, of thinking technically. But to so many, code seems either too daunting or too difficult to approach. Why is this? Is this view appropriate? Is code really as scary and as hard as we assume it to be?

Through examining my personal and ongoing journey through learning to code, and proposing a question-oriented process, I attempt to break down the myths surrounding code that portray it as an exclusive art. The end result? A reminder that code isn’t particularly special, and that learning it is simply a matter of training ourselves to solve problems, using a new medium.

Originally presented to Sheridan College’s CCT260 and CCT360 classes, in May 2016.

Lucas Cherkewski

May 18, 2016
Tweet

More Decks by Lucas Cherkewski

Other Decks in Programming

Transcript

  1. Why bother with code?

    View Slide

  2. Why bother with code?
    Playing with, failing at, and
    learning how to code

    View Slide

  3. What is code?

    View Slide

  4. Code is…

    View Slide

  5. Code is… scary?

    View Slide

  6. Code is… scary?
    Code is… hard?

    View Slide

  7. Code is… scary?
    Code is… hard?
    Code is… worthwhile?

    View Slide

  8. Is code scary?

    View Slide

  9. 500 000+

    View Slide

  10. Major industries
    embracing tech

    View Slide

  11. Movie portrayals of
    code

    View Slide

  12. It’s reasonable to feel
    that code is scary

    View Slide

  13. Is code hard?

    View Slide

  14. Code is (literally) an
    unfamiliar language

    View Slide

  15. We try hard to learn,
    but walk away
    confused

    View Slide

  16. Even with practice, it
    can be difficult

    View Slide

  17. I struggle with

    code, too

    View Slide

  18. Is code worthwhile?

    View Slide

  19. Yes!

    View Slide

  20. Thinking technically is
    valuable

    View Slide

  21. We can solve our own
    problems

    View Slide

  22. We can work with
    better coders

    View Slide

  23. Knowing code enables
    us to work in a
    technical world

    View Slide

  24. View Slide

  25. A history of code, play,
    and failure

    View Slide

  26. My own website
    Slow improvement

    View Slide

  27. View Slide

  28. View Slide

  29. View Slide

  30. View Slide

  31. View Slide

  32. Work with/for others
    Always an imposter

    View Slide

  33. View Slide

  34. View Slide

  35. View Slide

  36. View Slide

  37. View Slide

  38. View Slide

  39. View Slide

  40. Personal projects
    Fun failure

    View Slide

  41. View Slide

  42. View Slide

  43. View Slide

  44. View Slide

  45. View Slide

  46. View Slide

  47. View Slide

  48. What is code, really?

    View Slide

  49. VS
    The Product
    The Process

    View Slide

  50. Process > Product

    View Slide

  51. What is code?
    A problem solving
    process

    View Slide

  52. What are some
    practical examples of
    code?

    View Slide

  53. Google search

    View Slide

  54. View Slide

  55. View Slide

  56. View Slide

  57. Formatting text

    View Slide

  58. View Slide

  59. View Slide

  60. View Slide

  61. View Slide

  62. View Slide

  63. =

    View Slide

  64. =

    View Slide

  65. Building spreadsheets

    View Slide

  66. View Slide

  67. View Slide

  68. View Slide

  69. View Slide

  70. View Slide

  71. View Slide

  72. Who can code?

    View Slide

  73. View Slide

  74. Only nerds, definitely.

    View Slide

  75. Only people gifted
    with awesome coding
    power, definitely.

    View Slide

  76. BAH.

    View Slide

  77. Anyone can code.

    View Slide

  78. Anyone can code.

    (If you can

    problem solve.)

    View Slide

  79. Anyone can code.

    This is a good thing.

    View Slide

  80. Why so many
    questions?

    View Slide

  81. View Slide

  82. Socrates

    View Slide

  83. Socrates:
    Not just an
    old dead guy.

    View Slide

  84. Questions are key to
    learning to code.

    View Slide

  85. View Slide

  86. Socrates died for your
    questions.

    View Slide

  87. How do we code?

    View Slide

  88. The Process

    View Slide

  89. 1. Research

    View Slide

  90. 1. Research
    2. Explore

    View Slide

  91. 1. Research
    2. Explore
    3. Create

    View Slide

  92. The key is iteration.

    View Slide

  93. 1. Research

    View Slide

  94. 1. Research
    2. Explore

    View Slide

  95. 1. Research
    2. Explore
    3. Create

    View Slide

  96. Iterate,

    Iterate,

    Iterate.

    View Slide

  97. Demo
    Research, explore, create (and fail!)

    View Slide

  98. Why bother with code?

    View Slide

  99. Code is scary and hard,
    but worthwhile

    View Slide

  100. Code through research,
    exploration, and
    creation

    View Slide

  101. Do it again and again

    View Slide

  102. Thanks!

    View Slide

  103. Thanks!
    Thanks!
    [email protected]
    @lchski

    View Slide