Eloquent JavaScript 4th edition (2024)
181–190 of 249 posts
Re: Eloquent JavaScript 4th edition (2024)
#182Earlier quoted context omitted.
One hundred percent agree on both this book and the “You don’t know JavaScript”. Both are free (search Kyle Simpson GitHub). I ended up buying the YDKJ first edition paperbacks but see the second edition of all of them are done or a work in progress. EJs is the one I tell my students to start with as IMO is more of a programming book that just happens to us JS. I can tell the ones that read it (it’s optional) and the…
> Note the YDKJ books can come off as very ‘only my opinion is the right one’ kind of like JS the good parts I got the same feeling and it's very off-putting. KS seems like a dick. It's ironic that so much of his dickishness seems to be reacting against what he takes as Doug Crockford's dickishness. Ah the irony.
Re: Eloquent JavaScript 4th edition (2024)
#183Earlier quoted context omitted.
Are you reading programming books the same way you would read a fiction book? If so, stop doing that. Programming or any technical learning is a hands on experience. Take notes and apply techniques, using pen-and-paper or the keyboard, as they are presented. If you really have to just "read" a technical book, IME a less-is-more approach works best. 5-10 minutes at a time, not even a chapter at once. Maybe a few parag…
I read about fifty books a year for a decade now. Only about four of them per year, are programming books. They are indeed to be read very differently. Here's how I read them, ymmv. - never in bed. never as audiobook. But sitting. At a table or desk. - no distractions. At most "focus music". - read a chapter through. Then read it again and do all excercises (on a computer without wifi) - make copious notes, highlight…
And make sure you are typing the code, and not just copy pasta. Writing it out helps most people process it.
Re: Eloquent JavaScript 4th edition (2024)
#184Nothing changes in last few years. We still go in with what we incorrectly assumed at the start.
Re: Eloquent JavaScript 4th edition (2024)
#185This is from the chapter on HTML and JS (emphasis mine). It is funny to see how govt agencies and criminal organisations are mentioned in the same breath. How did we end up here?
Re: Eloquent JavaScript 4th edition (2024)
#186This is, in my opinion, the book to use to learn JavaScript at more than a surface level. The only other materials I recommend as much (but for a different level of learner) are the “You don’t know JavaScript” in-depth book series. In 2015, I was consulting for a distance learning program, administered by a major California University, that wanted to replace their current textbook (one of those “Head First” O’Reilly…
Re: Eloquent JavaScript 4th edition (2024)
#187I really like the Deno approach so far. I prefer TS mostly these days as well as the esm stroke modules. I think node just made usage harder in their approach. I understand why, I still disagree on the solution.
Re: Eloquent JavaScript 4th edition (2024)
#188For those that don't know the author, Marijn Haverbeke is the creator of CodeMirror (code editor) and later ProseMirror (text editor). https://codemirror.net/ https://prosemirror.net/
Re: Eloquent JavaScript 4th edition (2024)
#189Earlier quoted context omitted.
I read about fifty books a year for a decade now. Only about four of them per year, are programming books. They are indeed to be read very differently. Here's how I read them, ymmv. - never in bed. never as audiobook. But sitting. At a table or desk. - no distractions. At most "focus music". - read a chapter through. Then read it again and do all excercises (on a computer without wifi) - make copious notes, highlight…
> do all excercises (on a computer without wifi) And make sure you are typing the code, and not just copy pasta. Writing it out helps most people process it.
And turn off copilot. The code from the book is very likely in its training set. It will produce it almost verbatim. And you learn nothing.
Re: Eloquent JavaScript 4th edition (2024)
#190Earlier quoted context omitted.
I read about fifty books a year for a decade now. Only about four of them per year, are programming books. They are indeed to be read very differently. Here's how I read them, ymmv. - never in bed. never as audiobook. But sitting. At a table or desk. - no distractions. At most "focus music". - read a chapter through. Then read it again and do all excercises (on a computer without wifi) - make copious notes, highlight…
I don’t mind distractions when learning via books (I wouldn’t be able to finish my degree otherwise), but the other advices still apply. Reading a chapter without doing the exercices is like listening to a lecture without taking notes. You may understand a few things (or everything), but you’ll find that doing practice, drawing diagrams, or summarizing it lead to a deeper understanding. More often than not, you have…
But I guess a neurotypical zoomer can code fine with a TV in the background, a podcast in one ear, insta and DMs ploinging into their notifications and slack nagging in the status bar. I cannot.