$30 off During Our Annual Pro Sale. View Details »

Reflections from 52 weeks, 52 projects

Reflections from 52 weeks, 52 projects

My new years resolution was to do one project a week for the entire year. This is a presentation on how it's been going, and what I've learned thus far.

Jefferson Lam

May 11, 2015
Tweet

More Decks by Jefferson Lam

Other Decks in Education

Transcript

  1. Reflections From
    52 WEEKS, 52 PROJECTS
    Jefferson Lam
    May 11th, 2015

    View Slide

  2. 2014 2015

    View Slide

  3. 2014 2015

    View Slide

  4. View Slide

  5. What do I want to do in 2015?
    I want to continue to hone my skills in development.
    I’m gonna make it a New Years Resolution to develop
    a small project every week, and post it online every
    week, Saturday at or before noon. It can be big, or
    small. It needs to be something meaningful that
    challenges me and shows my skills.

    View Slide

  6. THE GOAL:
    52 PROJECTS IN 2015

    View Slide

  7. View Slide

  8. Weathery
    January 11th
    1

    View Slide

  9. 52
    January 19th
    2

    View Slide

  10. 52
    January 19th
    2

    View Slide

  11. 3
    Messengerbot
    January 25th

    View Slide

  12. 4
    Eightball
    January 31st

    View Slide

  13. 5
    Keyfighter
    February 9th

    View Slide

  14. 6
    Peeps
    February 25th

    View Slide

  15. 7
    Rollaball
    February 28th

    View Slide

  16. 8
    Flapper News
    March 12th

    View Slide

  17. 9
    Project Euler
    April 1st

    View Slide

  18. 20 weeks in, and I have 9 “projects”.
    What happened?

    View Slide

  19. REASON #1 :
    TIME

    View Slide

  20. started dating someone
    • work
    • sleep
    • friends
    • driving and being stuck in traffic

    View Slide

  21. REASON #2 :
    PROJECT IDEAS

    View Slide

  22. View Slide

  23. REASON #3 :
    NOT MAKING PROGRESS

    View Slide

  24. time
    skill
    Expectation
    time
    skill
    Reality

    View Slide

  25. Some reflections…

    View Slide

  26. REASON #1 :
    TIME

    View Slide

  27. 24 Hours

    View Slide

  28. 24 Hours Sleep

    View Slide

  29. 24 Hours Sleep
    Work

    View Slide

  30. 24 Hours Sleep
    Work
    Commuting

    View Slide

  31. 24 Hours Sleep
    Work
    Commuting
    Friends, hobbies, errands, etc.

    View Slide

  32. 24 Hours Sleep
    Work
    Commuting
    Friends, hobbies, errands, etc.
    Code

    View Slide

  33. Not having time is no longer an excuse.
    You have to make time, and you have to make
    sacrifices.
    Lesson Learned #1

    View Slide

  34. View Slide

  35. REASON #2 :
    PROJECT IDEAS

    View Slide

  36. View Slide

  37. It’s hard to build something out of nothing.
    Build your projects around content.
    Lesson Learned #2

    View Slide

  38. “Project”?

    View Slide

  39. Q
    Why am I doing this Project 52?
    A
    To become a better developer.
    To give myself opportunities to code.

    View Slide

  40. “Project”? Project.
    Code snippets are fine.
    In fact, anything is fine.
    Just make something.

    View Slide

  41. View Slide

  42. It’s OK to discard old goals if they are no
    longer helpful. Constantly re-assess your
    goals and move them as needed.
    Lesson Learned #3

    View Slide

  43. Big projects are daunting. It’s easier to get
    things done if you keep your scope small.
    Lesson Learned #4

    View Slide

  44. REASON #3 :
    NOT MAKING PROGRESS

    View Slide

  45. time
    skill
    Expectation
    time
    skill
    Reality

    View Slide

  46. time
    skill
    How Skill Acquisition Works
    discover task-runners!
    discover CSS animations!

    View Slide

  47. time
    happiness
    How Skill Acquisition Feels

    View Slide

  48. Kathy Sierra: Making Badass Developers

    View Slide

  49. Kathy Sierra: Making Badass Developers

    View Slide

  50. I was trying to hit too many targets.

    View Slide

  51. Develop a specific toolkit, and focus on
    mastering those skills. You won’t learn
    anything if you try to learn everything.
    Lesson Learned #5

    View Slide

  52. “Jack of all trades, master of none.”
    - Unknown

    View Slide

  53. Kathy Sierra: Making Badass Developers

    View Slide

  54. I was getting really good at being mediocre.

    View Slide

  55. View Slide

  56. View Slide

  57. I was coding in a vacuum.
    I wasn’t reading or learning from others.

    View Slide

  58. I was trying hard to create cool stuff.
    But as I read more, the quality of my work
    naturally improved.

    View Slide

  59. View Slide

  60. View Slide

  61. Learning by doing is great, but don’t forget
    to take in new information. Read, and get
    other people’s feedback. This will help you
    stay up-to-date.
    Lesson Learned #6

    View Slide

  62. You can only create what you know. Your
    work is a direct reflection of your knowledge.
    Lesson Learned #7

    View Slide

  63. “Nothing of me is original. I am the combined
    effort of everybody I’ve ever known.”
    - Chuck Palahniuk, Invisible Monsters

    View Slide

  64. WHAT HAVE I
    ACHIEVED?

    View Slide

  65. My Github
    activity blew up.
    Repos
    ~2 ➞ 18
    Streak
    ~2 ➞ 15
    Contributions
    0 ➞ 436
    Pull Requests
    0 ➞ 2

    View Slide

  66. I started using
    Twitter more.
    Followers
    ~12 ➞ 59
    Tweets
    ~10 ➞ 85

    View Slide

  67. I started using
    CodePen.
    Projects
    0 ➞ ~6
    Followers
    0 ➞ 1

    View Slide

  68. I started redesigning my website.

    View Slide

  69. I have a ton more
    dev stickers and
    t-shirts.

    View Slide

  70. I’ve done 2 talks.
    This is my 3rd.

    View Slide

  71. I’ve started
    working out more.

    View Slide

  72. I’ve developed more
    of a toolkit.
    - Gulp
    - Sass
    - Linters
    - Normalizer
    - Reset
    - Pesticide
    - Sublime Settings
    - Codepen

    View Slide

  73. My New Favorite Resources:
    • Github (other people’s repos)
    • Codepen
    • Twitter
    • Panda
    • Medium
    • A List Apart
    • HackReactor YouTube Channel
    • The FED interview question list
    • http://h5bp.github.io/Front-end-Developer-Interview-Questions/

    View Slide

  74. LOOKING
    FORWARD

    View Slide

  75. - Read more
    - Teach more
    - Start blogging
    - Pair program more
    - CodePen everything
    - Ask for feedback more
    - Answer all the FED interview questions
    Looking forward, I am going to…

    View Slide

  76. in closing

    View Slide

  77. Most days feel like failure days.

    View Slide

  78. But the fact that I’ve taken any steps forward
    means I’ve made progress, and that is
    a success in and of itself.

    View Slide

  79. It’s not easy to become an expert. The
    important thing is to keep pushing forward,
    intelligently. Keep coding.

    View Slide

  80. Just keep coding.
    Lesson Learned #8

    View Slide

  81. Thank you!
    Jefferson Lam
    May 11th, 2015

    View Slide