A static site generator should be your next language learning project
•
0 likes•2,458 views
The document recommends that a static site generator should be someone's next language learning project. It discusses how building a basic static site generator allows one to learn fundamental programming concepts and provides an iterative, incremental way to learn a new language. Static site generators can then be expanded upon to learn more advanced topics like templating, conditional logic, and building full-fledged websites and apps. Regularly learning new languages through such projects is important for lifelong learning.
Recommended
More Related Content
Similar to A static site generator should be your next language learning project
Similar to A static site generator should be your next language learning project (20)
More from John Anderson
More from John Anderson (20)
Recently uploaded
Recently uploaded (20)
A static site generator should be your next language learning project
- 1. A static site generator should be your next language learning project john sj anderson | @genehack | ! seagl 2017 why&how2learn — SeaGL 2017 — @genehack 1
- 2. hi, i’m john. a/k/a @genehack why&how2learn — SeaGL 2017 — @genehack 2
- 3. vp, technology infinity interactive why&how2learn — SeaGL 2017 — @genehack 3
- 4. ex-biologist perl tribe polyglot coder why&how2learn — SeaGL 2017 — @genehack 4
- 5. a static site generator should be your next language learning project why&how2learn — SeaGL 2017 — @genehack 5
- 6. the why and the how of learning a new programming language why&how2learn — SeaGL 2017 — @genehack 6
- 7. premise: lifelong learning is critical. why&how2learn — SeaGL 2017 — @genehack 7
- 8. the only constant thing is people telling you over and over that the only constant thing is change. why&how2learn — SeaGL 2017 — @genehack 8
- 9. “Learn at least one new language every year.” — David Thomas & Andrew Hunt, “The Pragmatic Programmer”, 1999 why&how2learn — SeaGL 2017 — @genehack 9
- 10. “Learn at least one new JavaScript framework every month” — Me, This Talk, Right Now. why&how2learn — SeaGL 2017 — @genehack 10
- 11. some of the languages i’ve “learned” basic pascal applescript why&how2learn — SeaGL 2017 — @genehack 11
- 12. some of the languages i’ve “learned” perl ruby python why&how2learn — SeaGL 2017 — @genehack 12
- 13. some of the languages i’ve “learned” javascript php cwhy&how2learn — SeaGL 2017 — @genehack 13
- 14. some of the languages i’ve “learned” lisp clojure scalawhy&how2learn — SeaGL 2017 — @genehack 14
- 15. some of the languages i’ve “learned” node swift c♯why&how2learn — SeaGL 2017 — @genehack 15
- 16. how do you learn a language? why&how2learn — SeaGL 2017 — @genehack 16
- 17. read books and docs why&how2learn — SeaGL 2017 — @genehack 17
- 18. dopractice exercises why&how2learn — SeaGL 2017 — @genehack 18
- 19. learning projects why&how2learn — SeaGL 2017 — @genehack 19
- 20. my language learning project of choice: static site generatorswhy&how2learn — SeaGL 2017 — @genehack 20
- 21. whatis a static site generator? why&how2learn — SeaGL 2017 — @genehack 21
- 22. ssgwhy&how2learn — SeaGL 2017 — @genehack 22
- 23. some inputs ➡ a websitewhy&how2learn — SeaGL 2017 — @genehack 23
- 24. nodatabase! why&how2learn — SeaGL 2017 — @genehack 24
- 25. can be very simple why&how2learn — SeaGL 2017 — @genehack 25
- 26. why&how2learn — SeaGL 2017 — @genehack 26
- 27. single pagewhy&how2learn — SeaGL 2017 — @genehack 27
- 28. part of a larger sitewhy&how2learn — SeaGL 2017 — @genehack 28
- 29. regenerated every day why&how2learn — SeaGL 2017 — @genehack 29
- 30. wrote ~10-15 years ago why&how2learn — SeaGL 2017 — @genehack 30
- 31. or can be kinda complicated why&how2learn — SeaGL 2017 — @genehack 31
- 32. why&how2learn — SeaGL 2017 — @genehack 32
- 33. company sitewhy&how2learn — SeaGL 2017 — @genehack 33
- 34. weblog with tags, archive, et cetera why&how2learn — SeaGL 2017 — @genehack 34
- 35. so why are ssgs great for learning? why&how2learn — SeaGL 2017 — @genehack 35
- 36. iterative & incremental why&how2learn — SeaGL 2017 — @genehack 36
- 37. they hit on all the classicswhy&how2learn — SeaGL 2017 — @genehack 37
- 38. hello world as a ssg why&how2learn — SeaGL 2017 — @genehack 38
- 39. o hai there why&how2learn — SeaGL 2017 — @genehack 39
- 40. 1. read input from file 2. process the input 3. write output to file why&how2learn — SeaGL 2017 — @genehack 40
- 41. why&how2learn — SeaGL 2017 — @genehack 41
- 42. let’s pause herewhy&how2learn — SeaGL 2017 — @genehack 42
- 43. 1. read input from file 2. process the input 3. write output to file why&how2learn — SeaGL 2017 — @genehack 43
- 44. in those 3 steps we just did a whole bunch of stuffwhy&how2learn — SeaGL 2017 — @genehack 44
- 45. writing some code and getting it to build/run why&how2learn — SeaGL 2017 — @genehack 45
- 46. reading & writing files why&how2learn — SeaGL 2017 — @genehack 46
- 47. getting data into a variable why&how2learn — SeaGL 2017 — @genehack 47
- 48. interpolating a variable into output why&how2learn — SeaGL 2017 — @genehack 48
- 49. o/ yay!why&how2learn — SeaGL 2017 — @genehack 49
- 50. next: two input files why&how2learn — SeaGL 2017 — @genehack 50
- 51. as well: templates! why&how2learn — SeaGL 2017 — @genehack 51
- 52. which means: figuring out packages why&how2learn — SeaGL 2017 — @genehack 52
- 53. note: probably don’t write your own template engine why&how2learn — SeaGL 2017 — @genehack 53
- 54. also: loops & conditional logic oh my why&how2learn — SeaGL 2017 — @genehack 54
- 55. after that…why&how2learn — SeaGL 2017 — @genehack 55
- 56. the sky’s the limitwhy&how2learn — SeaGL 2017 — @genehack 56
- 57. add a weblogwhy&how2learn — SeaGL 2017 — @genehack 57
- 58. add other processors why&how2learn — SeaGL 2017 — @genehack 58
- 59. add a subcmd-style appwhy&how2learn — SeaGL 2017 — @genehack 59
- 60. and then you can get fancy… why&how2learn — SeaGL 2017 — @genehack 60
- 61. HTTP serverwhy&how2learn — SeaGL 2017 — @genehack 61
- 62. automatically rebuild output when input is modified why&how2learn — SeaGL 2017 — @genehack 62
- 63. only rebuild output when necessary why&how2learn — SeaGL 2017 — @genehack 63
- 64. finallywhen you think you’re “done”… why&how2learn — SeaGL 2017 — @genehack 64
- 65. go back & take another look why&how2learn — SeaGL 2017 — @genehack 65
- 66. don’twrite your $oldlang in your $newlang why&how2learn — SeaGL 2017 — @genehack 66
- 67. so, to sum up: why&how2learn — SeaGL 2017 — @genehack 67
- 68. continuing to learn is vital!why&how2learn — SeaGL 2017 — @genehack 68
- 69. figure out how to make that happen why&how2learn — SeaGL 2017 — @genehack 69
- 70. both in terms of “maintain interest in it” why&how2learn — SeaGL 2017 — @genehack 70
- 71. and in terms of “be good at it” why&how2learn — SeaGL 2017 — @genehack 71
- 72. disclaimer: this talk is based on my opinions and experiences why&how2learn — SeaGL 2017 — @genehack 72
- 73. your mileage will vary why&how2learn — SeaGL 2017 — @genehack 73
- 74. thanks! why&how2learn — SeaGL 2017 — @genehack 74
- 75. special thanks @qedunham why&how2learn — SeaGL 2017 — @genehack 75
- 76. special thanks @vmbrasseur @garethgreenaway why&how2learn — SeaGL 2017 — @genehack 76
- 77. seagl organizers why&how2learn — SeaGL 2017 — @genehack 77
- 78. you! why&how2learn — SeaGL 2017 — @genehack 78
- 79. why&how2learn — SeaGL 2017 — @genehack 79
- 80. questions? why&how2learn — SeaGL 2017 — @genehack 80