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

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 full-size slide

  2. 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 full-size slide

  3. THE GOAL:
    52 PROJECTS IN 2015

    View full-size slide

  4. Weathery
    January 11th
    1

    View full-size slide

  5. 52
    January 19th
    2

    View full-size slide

  6. 52
    January 19th
    2

    View full-size slide

  7. 3
    Messengerbot
    January 25th

    View full-size slide

  8. 4
    Eightball
    January 31st

    View full-size slide

  9. 5
    Keyfighter
    February 9th

    View full-size slide

  10. 6
    Peeps
    February 25th

    View full-size slide

  11. 7
    Rollaball
    February 28th

    View full-size slide

  12. 8
    Flapper News
    March 12th

    View full-size slide

  13. 9
    Project Euler
    April 1st

    View full-size slide

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

    View full-size slide

  15. REASON #1 :
    TIME

    View full-size slide

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

    View full-size slide

  17. REASON #2 :
    PROJECT IDEAS

    View full-size slide

  18. REASON #3 :
    NOT MAKING PROGRESS

    View full-size slide

  19. time
    skill
    Expectation
    time
    skill
    Reality

    View full-size slide

  20. Some reflections…

    View full-size slide

  21. REASON #1 :
    TIME

    View full-size slide

  22. 24 Hours Sleep

    View full-size slide

  23. 24 Hours Sleep
    Work

    View full-size slide

  24. 24 Hours Sleep
    Work
    Commuting

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  28. REASON #2 :
    PROJECT IDEAS

    View full-size slide

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

    View full-size slide

  30. “Project”?

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  33. 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 full-size slide

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

    View full-size slide

  35. REASON #3 :
    NOT MAKING PROGRESS

    View full-size slide

  36. time
    skill
    Expectation
    time
    skill
    Reality

    View full-size slide

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

    View full-size slide

  38. time
    happiness
    How Skill Acquisition Feels

    View full-size slide

  39. Kathy Sierra: Making Badass Developers

    View full-size slide

  40. Kathy Sierra: Making Badass Developers

    View full-size slide

  41. I was trying to hit too many targets.

    View full-size slide

  42. 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 full-size slide

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

    View full-size slide

  44. Kathy Sierra: Making Badass Developers

    View full-size slide

  45. I was getting really good at being mediocre.

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  48. 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 full-size slide

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

    View full-size slide

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

    View full-size slide

  51. WHAT HAVE I
    ACHIEVED?

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  55. I started redesigning my website.

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  58. I’ve started
    working out more.

    View full-size slide

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

    View full-size slide

  60. 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 full-size slide

  61. LOOKING
    FORWARD

    View full-size slide

  62. - 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 full-size slide

  63. Most days feel like failure days.

    View full-size slide

  64. 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 full-size slide

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

    View full-size slide

  66. Just keep coding.
    Lesson Learned #8

    View full-size slide

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

    View full-size slide