The board book we have is an abridged version which (1) omits the weird belligerent chase scene in the bottom half and also (2) skips a few details inThe board book we have is an abridged version which (1) omits the weird belligerent chase scene in the bottom half and also (2) skips a few details in the first half while retaining all of the images, leading to at least one visual non sequitur. (Roller skates!?)...more
If you’re unfamiliar with Jasmine, Ragonha will give you a solid foundation of the testing framework by the end of the second chapter. Less than 40 pages in and you’ll understand Jasmine’s approach to testing, as well as how to stand up a basic test suite. His coverage of the core functions and the collection of built-in matchers is concise and accurate. He builds on this foundation by demonstrating Jasmine’s abilities in testing everything from asynchronous code (Sinon.js!) to MVC components (Backbone.js!) to AMD modules (Require.js!).
Disclosure: I received an electronic copy of this book from the publisher in exchange for writing this review.
The first book that E. ever really requested and then voluntarily sat through without needing to be like... restrained. (He really couldn't be more diThe first book that E. ever really requested and then voluntarily sat through without needing to be like... restrained. (He really couldn't be more different than H.)
He probably likes this one because it has all of his favorite things:
- puppy dogs (insert panting sound here) - beach balls - soccer balls - ducks - eating - ice cream - the park - the beach - daddy...more
Borderline four stars... and I think when it's completed and fully edited, it just might be. (Disclosure: I read an early access edition; O'Reilly Borderline four stars... and I think when it's completed and fully edited, it just might be. (Disclosure: I read an early access edition; O'Reilly  has been doing that a lot lately...)
: To be fair: almost all of the technical book publishers that I know of are doing this lately -- i.e., releasing "Early Access Editions" and "MEAPs" and the like.
: I go back and forth on this bit of critique. If you're "all theory" then you're potentially losing out on providing some value because you're discussion is too far away from the real problems; but if you're too close to "the real thing" then you're just talking about that specific situation or tool-chain and it winds up being about addressing that problem with that tool, and not really "that class of problem". Elliott is somewhere in the middle here, listing only slightly toward "too specific" and only in a couple of places.
: The PDF I have of this book has a little more, and some slightly different content than the version I read on my Kindle. Again: "Early Access Editions" and all that......more
And that's where MacCaw's Little Book on CoffeeScript comes in.
It's short (62 pages!) and gets right to the point. And MacCaw is (by and large) eloquent about the subject, if a bit... provocative at times.
Loved: I wanted to learn a couple of things about CoffeeScript and MacCaw gave us exactly that, and with no ceremony. "This is CoffeeScript. Yes, this is all there is to it. And we're done."
However: there were a few statements in the book that made me bristle a bit. Example:
And the crux of the book is about CoffeeScript. And by the end of it, you'll know enough about that little language to form your own opinion of it. And that opinion is probably something like:
I would rate this one as a pretty solid introduction to AngularJS, covering the framework's philosophy, the core APIs, and getting into a few (but notI would rate this one as a pretty solid introduction to AngularJS, covering the framework's philosophy, the core APIs, and getting into a few (but not all) of the nuts-and-bolts. By the time you get to the end of it, you should be able to build a non-trivial app in Angular -- though the jury's out on exactly how non-trivial that will be. Green and Seshadri have a clear and straightforward approach to presenting the material (no tricks!) and it (mostly) helps that they're both so deeply involved in the framework's development.
I had quite a few "ah-ha" moments while reading this one, enough to get me better engaged with "the Angular Way" and to see some mistakes and pitfalls I was making in my own apps. Unfortunately, despite how clear Green and Seshadri are throughout the text, there are still a few concepts that don't quite ring totally clear. In particular: (1) there is a whole chapter on directives and yet at the end of it, I was not sure that I understood them that much more than when I started ; (2) whither filters?; (3) I have a sneaking suspicion that they slyly snuck in a few of the kinda/sorta undocumented features of the core Angular libraries without really mentioning it. 
Overall, the book is well-structured, with clearly titled chapters, making it easy to jump around and cherry-pick what you need out of it. If you're new to Angular, I highly recommend this book and urge you to (at a minimum) read the first four chapters.
: That being said: you can tell just how important Green and Seshadri think directives are, and also just how complicated they think they are. Directives are introduced pretty early on, and then they get their own chapter, and then there's another more detailed (and arguably more useful) illustrative example in the "Cheatsheet and Recipes" chapter. (Which, by the way, would have been better titled as "Case Studies" -- but I digress.) Anyway: I'm thinking that directives are just one of those things that's critical to "the Angular Way" but is also fairly complex (incidentally or otherwise?) and you just need to find your own "ah-ha" moment.
: I say kinda/sorta because the Angular documentation (you may have noticed) is broken down into an "API Reference" and a "Developer Guide" and it isn't always clear which features are documented where. Or why something is documented in one but not the other (or else why it's in both...) So maybe I'm being a little unfair when I say "snuck in" and "undocumented" but... well: that's how it felt....more
This is a book that I remember from my own childhood and now my son is asking me to read it to him. And man... It's one of those books that you just sThis is a book that I remember from my own childhood and now my son is asking me to read it to him. And man... It's one of those books that you just sort of begrudgingly grind your way through.
Also: kind of a Bildungsroman? But with a duckling? And/or it's totally a book about puberty. The only thing it's missing is the pubescent duckling having a confusing wet dream.
ALSO: dude! Why is that boy just randomly picking up eggs and taking them home? And furthermore: the way it ends? With the grown-up duckling's own egg left in the grass like that -- aren't we setting this story up to be a bit cyclical?...more
Not nearly as cheeseball as I expected. Not nearly as sexist as I expected. John Carter is actually a (mostly) decent guy. And this novel holds up welNot nearly as cheeseball as I expected. Not nearly as sexist as I expected. John Carter is actually a (mostly) decent guy. And this novel holds up well;I can see why it's a classic of the genre....more