> a fairly long-lived and large code-base Such could be spaghetti on any platform. To understand web programming, I wouldn't start with something big and old. I've been doing web programming for more than a decade, and I still don't get the majority of web frameworks. Start instead with the basics, and work your way up: 1. HTML. Don't view the source of websites and web apps to understand HTML. Read a good book or tutorial. HTML Dog is a good one. 2. CSS. Likewise. 3. JavaScript. Definitely don't try to learn JavaScript by viewing source either. Instead, maybe HTML Dog. There's also…
You will probably get hundreds of comments with unsolocited advice, but let me just say to checkout and setup JSLint: https://github.com/douglascrockford/JSLint Setup and how you use it is more important than just using it. I run it in three places: 1) In my IDE (bound in vim on save, same in TextMate) 2) As a Git checking hook 3) In deployment / build scripts Turn all the warnings way up and it always catches redeclaration bugs. Set it up once and don't allow any code to get checked in or deployed with even a single warning present. I also pass all Javascript through the Google…
>median age of an American is 41. That we're discussing people in that age range as counterexamples kind of proves the point. Don't take my previous post as a complete dataset. It was only coincidence that I happen to list programmers in their 40s off the top of my head. Here are some more in their 60s: - Google also hired Vint Cerf (TCPIP) at age 62. - Amazon AWS recently hired James Gosling (Java) age ~62. - PayPal hired Douglas Crockford (Javascript book author) at age ~57. My point is that SV companies (and other industries besides tech) will actually discriminate against the young…
Well, first things first, you must be aware that JavaScript is a bad language, broken in many ways and mostly executed in a random fashion (i.e. almost no platform follows 100% ECMA, and even some ECMA directives are retarded, like ECMA4 didn't force chrome to return object properties in creation order by default, whereas ECMA5 fixes that to the default behavior we've always seen and expected). In that sense, writing good JavaScript is like writing good PHP or good C++, it's a lot about avoiding the broken features (for both those languages, there are a lot of features one shouldn't use,…
You can learn a ton about the language itself by reading. A good place to start is this collection of free online resources. http://jsbooks.revolunet.com/ My favorites from this site are as follows: http://eloquentjavascript.net/contents.html http://bonsaiden.github.com/JavaScript-Garden/ http://www.addyosmani.com/resources/essentialjsdesignpattern... http://jstherightway.com/ Mozilla has excellent JavaScript material: https://developer.mozilla.org/en-US/docs/JavaScript/Guide https://developer.mozilla.org/en-US/docs/JavaScript/Referenc... As far as print goes, you'll want these books in…
Very true. I love CoffeeScript very, very much. It's my favorite language - I like it even better than ruby, if you believe me! I like using indentation instead of stupid 'end's that only God knows are ending a loop or a def or something else, I like the use of ... instead of * (for splats), and a few other things. But, as much as I like CS and hate (really hate) JS, I have to agree with you wholeheartedly. You must know JavaScript well. Variable/function hoisting won't bite you in CS, but other JS idiocies will. Read Douglas Crockford's "JavaScript: The Good Parts" at least twice (and take…
Does this mean Svelte 3 is the Tesla of the web? No virtual DOM it's like it doesn't even use gas. XD tl;dl around 20:45: They're comparing javascript and the tools you use for it to transportation modes. Saying things like Angular was the H2, React is the H3, vanilla javascript is riding a bike. They really are just saying don't over engineer things and use the right tools for the job. Douglas Crockford's Javascript the Good Parts, is imo the best when it comes to getting a feel for what the right/wrong tools are. That book was a perspective changer for me. People like to get very…
http://fecklessmind.com/2009/02/09/top-5-javascript-books/ http://www.reddit.com/comments/6y1km/ask_reddit_good_javascr... http://www.reddit.com/r/programming/comments/9gy1e/askproggi... http://www.reddit.com/r/programming/comments/8ptt5/ask_reddi... usual suspects: Flanagan, "Good Parts" and Crockford's Videos, Resig, Harmes/Diaz...
My girlfriend got me a Kindle 3 as an early Christmas gift, and while there are a lot of things I wish it would do better (or at all), I actually really like it. From worst to best: 1. The Kindle is pretty terrible for textbooks or other things used purely as references (some people supposedly read texbooks, I don't). 2. The Kindle isn't too bad for technical books that you actually want to read, but aren't going to use as references. For example I bought the Kindle version of Douglas Crockford's Javascript: the Good Parts and read it front to back without much issue. Code formatting was…
I hate these books. Basically it's just synonyms for well known concepts, like blue in language b is called gog and orange in language a is called koom. It extends to more complex concepts as well like this is how you do an if statement in python vs. c++. For JavaScript the good parts it's this type of book. Literally nothing new is learned save how to rename the some concept as the good part of JavaScript. Details that you can learn any time. What I want from a book is to learn new concepts. For example functions and data are the same thing. Or recursion and a loop + stack are isomorphic…