It gets complicated quickly, but I think the jump from rithm's free courses to eloJS is a step that makes sense. Rithm gets you to the intermediate level, and EloJS cements it. I think they're releasing more stuff on python as well if you're interested.Ģ. They also give explanations for why you should do stuff (if you want to read). I also think these guys don't hold your hand and teach you how to think rather than just "do this". You have to give them your email, but they don't spam and are actually helpful. Rithm's free JS courses provide a perfect beginner to intermediate step for learning JS. I semi-recently found out about these guys they're legit. I've tried a shit ton of stuff for beginners and through a lot of trial and error (and time wasted -_-) I ended up with the roadmap that I believe works best. However, I also think you need solid fundamentals in order to make the jump to Eloquent JavaScript. I think Eloquent JavaScript is a PHENOMENAL book. I've shot this out to a few people already, but I'll just copy paste it here: And I didn't give up at with the weresquirrel stuff but again why do you have to bring statistical formulas into an intro to JS? I have a background in stats so I could follow it easily but can imagine how weird it must seem to people with no real math/stats experience. I just didn't expect it to be this hard for a "beginners" book like you say. One thing I have to say is once you manage to complete the exercises it does make you feel like you have learned something. Still so many people can't be wrong so I guess I will just continue through the chapters at the same snails pace. I mean the guy clearly knows his stuff but he is not doing that great at communicating his knowledge. Net background but I would have thought there should be some kind of interface definition. Only 2 different implementations and some commented out text that I guess must be the interface "design". Net is going (nowhere) so its not that I don't know how to program.īut the final exercise of chapter 6 is just so damn confusing: design an interface to do this and that.OK am I supposed to do that in my head because after about 2 days of struggling I finally looked at the solution for the exercise and there is no "interface" defined anywhere. I have 13 years experience in C# and have decided to learn JS because I can see where. I agree with you, I am at the end of chapter 6 and only made it so far because of bullheaded perseverance. Odds are good you'll be creaming all over the pages as you're reading it too. So going by the numbers, maybe you should give it a shot anyway. Everyone else sounds orgasmic whenever they mention it. In fact, I can only recall seeing one other person write anything less than gushing praise about it. Lots and lots of people obviously love it. Unfortunately, the only way I'll be able to do that is to read other people's books and actively avoid his in order to prevent damaging my brain further. The author clearly knows his shit when it comes to JS and I can only hope to ever become as good a programmer one day. The only people I recommend this book to is maybe campers, because sometimes you can't find dry kindling. I don't recommend this book for beginners, not for intermediate, not for anyone. Really? lol) Part of me believes that maybe the book's purpose is to turn off as many people from programming as possible in order to keep the supply of devs low. How the fuck does this happen? You have to be a special kind of bad teacher to be able to pull this off. I WAS READING ABOUT STUFF I ALREADY KNEW VERY WELL. Turns out I felt pretty lost by the end of ch. From about half-way through page 1 onwards, all I could think was, "if I didn't already know this stuff, I would be so lost and confused that I would give up the idea of programming forever". There is not one single thing he writes about that I didn't already know, and yet, the order in which he presents new concepts and their explanations are so confused, convoluted and muddled that I actually feel dumber after reading it. 3, I stopped reading in angry frustration. Maybe it's a good time to go back and try again, I thought. By the end of the 3rd chapter, I was so lost I gave up.įast forward several months to the point where I know considerably more JS than I did on my first attempt at the book. I saw EloJS being proselytized everywhere so much that I thought if I read it I might actually find God. A year ago I decided to learn JS seriously and in-depth in order to make it my career. I have a very solid grasp of all the fundamentals such as type, variables, loops, functions, etc. I've been hobby programming on occasion ever since I was a teen. If you write a book for beginners that is too complex for beginners, you done fucked up. Why is this a problem? Because it's a book that was written FOR beginners.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |