slopfront
Reddit, read-only. No JavaScript. No cookies. No tracking.
preferences

Learn JavaScript Properly - Week 7 [final week!]

6 points · submitted Jul 2013 by u/d0gsbody

1/ Read OOP in JS: What You NEED to Know

2/ Read either:

  • Chapters 9, 18, 21, and 22 of JS: The Definitive Guide, OR

  • Chapters 6 (only the "Object Creation" + "Inheritance" sections), 16, 22, and 24 of Professional JS for Web Developers.

3/ Improve your quiz application even further with:

  • Twitter Bootstrap,

  • Handlebars.js, and

  • Add scorekeeping + ranking functionality amongst users who have taken the quiz (if you wanna get really fancy)

4/ If you haven't already, please post your quiz!

Awesome work, everyone! Share your quizzes!!

I am also talking with a few other people, including Hack Reactor, the school that moderates this subreddit, about doing more extensive learning projects going forward (I may put up a post seeking help with this in the next 2-3 weeks).

7 comments · 88% upvoted · other discussions

comments

robotmayo 2 points · Jul 2013

Man, JavaScript : The Definitive Guide is so dry. Always find myself falling asleep halfway through a paragraph.

[deleted] 2 points · Sep 2013

[deleted]

mrbogus 2 points · Sep 2013

I 'd like to know this as well. This is a great idea that you guys have. Just out of curiosity, for the ones that stuck around, do you have any success stories?

[deleted] 2 points · Jul 2013

Wonder how many stuck with this all the way through.

totalmajor 1 points · Jul 2013

How do we get previous weeks?

ericawebdev 2 points · Jul 2013

In the right sidebar under Study Groups: you can see the link for Currently in Session: Learn JS Properly [Summer Session]

robotmayo 1 points · Jul 2013

Wouldn't ranking require a server side service meaning that people would have to learn server side language?

TheAceOfHearts 1 points · Jul 2013

You can do ranking as an instance thing. Sort of like arcade games, which have the high scores reset when the machine is reset. When you refresh the page it'd reset. (Although you could store it in cookies or localstorage or w/e)