The book’s been a work in progress since 2008 and it looks as though Bibeault was added as an author to get the thing done by the August 2011 target release date. There’s no shame in this; Resig’s a busy guy, and while I’d love to see this book finished, given the choice between a finished jQuery book and continued work on jQuery and all the related projects, I’d always rather have the latter. As of this writing, 14 out of the 17 chapters are done and my guess is that the book looks to be on track for an on-time release.
Although currently incomplete, the drafts of the book have served me well over the past three years. The book starts where few do, with a chapter on testing, covering both the general principles of unit testing as well as an overview of some of the more popular test suites. From there, the book covers the functional programming aspects of JavaScript with chapters on functions and closures and then the object-oriented aspects with a chapter on function prototypes. There’s a block of chapters that cover misunderstood aspects of JavaScript: timers, regular expressions, the with statement, the eval statement and writing code that works across browsers. And finally, there are the chapters that deal with web pages: CSS selectors, the dreaded DOM, attributes and CSS and event handling. All these chapters are chock-full of good code examples.
JS had to “look like Java” only less so, be Java’s dumb kid brother or boy-hostage sidekick. Plus, I had to be done in ten days or something worse than JS would have happened.
I consider JavaScript: The Good Parts to be the first of the really good JavaScript books, and its chapters on objects and functions are still required reading. However, with the recent release of Eloquent JavaScript and upcoming release of Secrets of the JavaScript Ninja, it’s no longer the first book I’d recommend (it’s still one of the better ones, though).
DailyJS
DailyJS is the most regularly updated blog on JavaScript out there. As its name suggests, it’s a blog that features a new story about JavaScript or a JavaScript framework or library every day (or almost every day, anyway). There’s a lot going on here: a tutorial series called Let’s Make a Framework (where you do just that), another series called Code Review in which they examine the code of many popular JavaScript frameworks and libraries to see what makes them tick and see how the established projects are written, and various articles on all things JavaScript. If you’re developing in JavaScript, you should bookmark this site.
JavaScript, a.k.a. ECMAScript, but originally named Mocha, then LiveScript, is many things at once, making it a confusing, messy beast. It’s ubiquitous, useful, powerful and even after all this time, has some goodies in its bag of tricks that will surprise you. It’s also clunky and confusing; and to make matters worse, misinformation in the form of dead-wrong documentation and bad JavaScript code examples abound. I’m going to borrow a backhanded compliment from my friend and former co-worker Adam “Adam Bomb” Carter and call JavaScript a “hot mess”. And I do mean it in the nicest sense of the phrase.
One of the attempts to help alleviate the confusion is JavaScript Garden, a site created by Ivo Wetzel and Zhang Yi Jiang. Written for the benefit of both new JavaScript developers who want to get it right the first time as well as long-time JavaScripters who are wondering if there are better ways to do things.
…it covers common misconceptions and bugs related to objects, prototypes, functions, this, closures, the arguments object, scoping, equality and comparisons, typeof and instanceof, and much more. The site is very nicely written and designed, and I recommend that you check it out!
…
It’s awesome to have great JavaScript documentation, and to have a community that takes the time to write it. If you are interested in contributing, or you find errors, JS Garden is hosted on Github, so just file issues and send them pull requests to help make this resource even better.
JavaScript is the most important programming language today, and JavaScript Garden is one of the most important JavaScript sites today. Make sure it’s in your bookmarks!
W3Fools: A W3Schools Intervention
When searching for information about HTML, CSS and JavaScript, W3Schools (no link, let’s not give them any more search engine juice) often shows up in the results, thanks to its longevity and some good hard SEO work on their part. The problem is that the site is all kinds of wrong, from its inaccurate and out-of-date information, to its name that falsely implies an association with the W3C to the certifications of dubious value that they offer. Among the erroneous or outdated info on this site is their JavaScript reference material.
W3Fools, a site created by “members of the front-end dev community”, explains why W3Schools is best avoided. Give it a read, and after that, you’ll know why you should generally avoid W3Schools.
Random Hacks of Kindness (RHoK) is a worldwide weekend-long marathon where computer programmers, humanitarian aid experts and general do-gooders get together to build prototypes of software to provide aid to people in need. This weekend, there are 18 such marathons taking place across the globe, and Toronto is holding one of them, thanks to my friend Heather Leson, the prime mover being RHoK Toronto.
This is the third RHoK to be held in Toronto, and here are the project that the teams are working on:
I attended RHoK 2 in December as an interested party as well as a Microsoft representative, and I wrote up the event in an article titled Hacking for Good Causes.
I’d like to send my regards to everyone at RHoK Toronto as well as all the RHoKs around the world. Keep on hacking the good hack!
Teams at Random Hacks of Kindness Toronto “hackathon” create new mobile and online tools
WHAT:
Hackathon to solve humanitarian problems & pitch competition
WHEN:
Pitch competition & judging: Sun., June 5 from 3 to 5 p.m.
Hackathon: Ends Sun., June 5 at 3 p.m.
WHERE:
Ontario Institute for Studies in Education (OISE), 5th floor, 252 Bloor St. W., Toronto
WHO:
Experts in climate, disaster, crisis; software, design, Internet, media, more (see below).
TORONTO, June 5, 2011 /CNW/ – Disaster professionals working with volunteer software makers in Toronto yesterday began building a set of mobile and online emergency aid tools whose prototypes they aim to complete today. This evening, competing teams will vie for prizes in a pitch competition judged by a panel of experts.
The teams at Random Hacks of Kindness Toronto (RHoK Toronto) are among some 1,000 people in 18 cities across 6 continents participating in a global weekend-long hacking marathon, or “hackathon,” that unites technologists and humanitarian experts in an effort to solve pressing problems.
“It’s unbelievable that the teams are able to create these mobile apps and online tools in less than 48 hours,” said Heather Leson, lead organizer of RHoK Toronto. “By dinner time last night, one team here had already programmed a working prototype!”
Projects
Competitors at the Ontario Institute for Studies in Education in downtown Toronto are working on six projects:
A mobile app that can use Twitter, Facebook, e-mail and other notification services to deliver emergency messages even when cellular phone networks have stopped working, and can alert rescue workers when someone is alive under a collapsed building
A telemedicine tool that would help people in remote or disaster-stricken areas to visually diagnose life-threatening wounds and help them seek treatment
An alerts tool that harnesses the emergency response capabilities of the worldwide ham radio community to bridge the digital divide with Internet-based first-responders
An app that helps people find and identify food growing in their immediate vicinity
A tool that helps relief workers track and manage emergency medical kit inventory in the field
A tool that enables people to avoid adverse drug reactions and helps them create a personal digital medical history.
The Random Hacks of Kindness volunteer community — founded in 2009 by Google, Microsoft, NASA, Yahoo and the World Bank — has produced mobile and online software tools that were deployed after disasters in Chile, Haiti and Japan.
Pitch competition Sunday afternoon
“This afternoon’s pitch competition will let the teams in Toronto show off their work — and give the most innovative ones bragging rights,” said RHoK Toronto manager Melanie Gorka. “The best pitches will also win prizes that include a private lunch with leaders at Mozilla, which makes the Firefox Web browser; high speed computer networking equipment from Linksys by Cisco, security software from Symantec, and more.”
The Toronto teams will also be able to receive coaching to develop and enhance their pitch and presentation skills, and consult with special guests who are experts in crisis and emergency aid, before they showcase their projects in front of the pitch competition judges:
Jesse Brown, host of TVO.org Search Engine podcast; writer for Macleans.ca, Toronto Life.
Paul Osman, Mozilla Foundation. Open Web team manager.
Karen Snider, Canadian Red Cross national media manager and social media strategist.
Julia Stowell, Microsoft Canada open source community and marketing manager.
Special guests:
Sara Farmer, United Nations Global Pulse chief platform architect.
Kate Chapman, Humanitarian OpenStreetMap Team. Open global map for aid efforts.
Aaron Huslage, SafeCast. Crowdsourced open tracking of reactor-leak radiation in Japan.
“The best part of Random Hacks of Kindness is that no matter which teams win Toronto’s pitch competition, all the participants learn, mentor and share in their world. Plus, some projects will continue and maybe become fully built,” Heather Leson said.
ABOUT RANDOM HACKS OF KINDNESS TORONTO:
RHoK Toronto is an ad hoc committee of civic-minded citizens with professional expertise across a broad range of industry sectors. The first Random Hacks of Kindness hackathon in Toronto was held inDecember 2010.
Community partners new and old have donated space, food, funds, prizes, services and tools to help make the event a success. Donations may be made through the RHoK.org Toronto site or by contacting the organizers. Current sponsors include: Camaraderie, Centre for Social Innovation, CIRA, Cisco, GlobalNews.ca, Jonah Group, Lady Atelier, Marketcrashers, MaRS Discovery District, Aaron McGowan, Microsoft Canada, Net Change Week, Nitido Inc., Rightsleeve, Symantec, Syncapse, Tropo, University of Toronto and Yahoo Canada.
Random Hacks of Kindness was founded in 2009 by Google, Microsoft, NASA, Yahoo and the World Bank. The worldwide innovation community has seen thousands of volunteers work on 120 open source software projects, including tools used in the Haiti and Chile earthquakes in 2010, the recent Japan quake and tsunami, and landslide-prone parts of the Caribbean. “Open source” means the computer code is available for anyone to use and build upon.
Global Random Hacks of Kindness community: www.rhok.org
Unfortunately, the poster’s not in plain sight at the Stores, and whoever designed it focused more on being arty than being readable. No worries: I got my paws on the text, formatted and annotated it a little, and present it to you below – enjoy!
The Full Text of the Poster
In the last 10 years, we’ve learned a lot.
We’ve learned to treat every day with the same enthusiasm we had on the first day. We’ve learned the importance of giving our customers just as much attention as they give us. And we’ve learned the art of hiring the right people for the right positions. We’ve learned it’s better to adapt to the neighborhood rather than expecting the neighborhood to adapt to us. Which is why we spend so much time and energy building stores the way we do.
Our first store, in Tysons Corner, taught us our first lesson within the first 30 minutes. We had just opened the doors when we noticed the steel already needed polishing. With a special polishing solution. And a special polishing tool. That’s when we learned that blasting steel with virgin sand makes it less prone to scuff marks.
The Midtown Manhattan Store. Creative Commons photo by Brad Greenlee.
We’ve also learned more than a few things about stone. Like how to reveal granite’s true color with a blowtorch. And that sometimes granite has veins of color that have to be matched.
We’ve also learned that getting these details perfect can feel like trying to move a mountain. Sometimes two. But in the end, the effort is worth it. Because steel, glass, and stone can combine to create truly unique and inspiring spaces.
The Paris Opera Store.
We also understand that finding the right design for our stores is critical. We even built a full-scale facade of the Regent Street store in a Cupertino parking lot to be sure the design was right. Which taught us the value of seeing things full size. We once had a notion that ministores would offer the ultimate in convenience. Then we built one. Which showed us that bigger can actually be better. And we’ve learned that even when our stores are big, no detail is too small. This is something we learned all over again when we restored the Paris Opera store down to the last of its more than 500,000 tiles.
We’ve also learned that our customers like open spaces, glass staircases, and handcrafted oak tables. And that those spaces don’t need to smell like pine trees or tomatoes to make them inviting. We’re constantly working to make our stores more artful, more iconic, and more innovative. And we’re awfully proud of every single one. We’re proud of our stores not just because they’re successful, but because of everything they’ve taught us. All the ways Apple Stores have made Apple stronger as a company.
Over the past 10 years, we’ve learned that our stores are the embodiment of the Apple brand for our customers. Now, our customers just happen to be the entire reason we’re here, so let’s dedicate a few words to them. Around the time we opened the store in Tysons Corner, in 2001, everyone else was trying to talk to their customers less. Which made us think that maybe we should talk to them more. Face-to-face if possible. So we’ve found ways to strike up a conversation at every possible opportunity. We talk while they play with the products on the tables. And when they join us for a workshop. These conversations have taught us that customers love our products, but what they really want is to make a scrapbook out of family photos. They want to make a movie about their kid. Or a website about traveling across the country.
Which has taught us that Apple Stores can and should be centers for creativity. And we’ve figured out through programs like Apple Camp and Youth Workshops that creativity doesn’t care about age. The movies and slideshows we’ve seen kids make are proof that all you need are the right tools and an idea. And we must be doing something right, because the kids’ smiles are just as big as ours. We’ve also learned that musicians can record an album in our stores that goes to the top of the charts. And that award-winning film directors are interested no just in our computers but in our workshops.
We’ve learned a lot about having fun. And we’ve learned our customers like to use our products for business too. Experience has taught us that having one Pro Day per week dedicated to business customers isn’t enough. That we need to be open for business very day. And have space devoted to business training sessions, workshops, and events. We’ve learned that every staff member should be just as fluent in the needs of a business customer as the needs of any other customer.
Our millions of conversations with customers of every stripe have taught us it’s not about making people feel like a computer or phone loves them. That’s impossible. Instead, it’s about giving people the tools to do what they love. And we’ve learned how to create amazing programs like One to One and Personal Setup to give people those tools. We created programs like these to replace fear with confidence. Because our customers have shown us that the ownership experience is even more important than the sale. We learned all this by asking questions. And genuinely listening to the answers. And to be sure we’re hearing everything, we’ve learned to converse in 36 languages, and a few of the local dialects as well. We’ve even learned a few cultural things. The proper use of the word y’all, for example. And our Japanese customers one taught us that their superheroes don’t wear capes. Which also taught us to see feedback as a gift.
Creative Commons photo by Randy Lemoine.
We’ve learned that a visit to the Genius Bar can fix more than just computers. It can also restore a customer’s relationship with Apple. And that we don’t need a minifridge stocked with free water to get people to talk to a Genius. Knowing they can get exactly the right answer when something isn’t working is enough. We even figured out how to shorten the time an in-store repair takes from seven days to one day.
Our customers hold us to exceptionally high standards. So we’ve learned how to raise ours even higher. 325 store openings have taught us that a grandopeningcreatesblocksandblocksofexcitement. That people will stand in line for hours, even days, just to be among the first to walk through the front door. And to get a free T-shirt. Speaking of T-shirts, we’ve learned more than you can imagine about our own. We’ve found that when we wear black T-shirts, we blend in. And when we wear too many colors it’s confusing. But blue shirts are just right. We’ve also learned that it takes precisely 4,253 stitches to embroider the Apple logo on those blue shirts. And we even figured out which direction the stitches should go in.
When it comes to product launches, we’ve learned we have to work hard to ensure supply meets demand. If not on the first day, then soon thereafter. And we’ve learned how to put our own products to use in innovative ways in our stores. We’ve created entirely new systems like EasyPay to help our customers as efficiently as possible. We’ve replaced the red phone behind the Genius Bar with more expertise right in our stores.
All of these experiences have made us smarter. And at the very center of all we’ve accomplished, all we’ve learned over the past 10 years, are our people. People who understand how important art is to technology. People who match, and often exceed, the excitement of our customers on days we release new products. The more than 30,000 smart, dedicated employees who work so hard to create lasting relationships with the millions who walk through our doors. Whether the task at hand is fixing computers, teaching workshops, organizing inventory, designing iconic structures, inventing proprietary technology, negotiating deals, sweating the details of signage, or doing countless other things, we’ve learned to hire the best in every discipline.
We now see that it’s our job to train our people and then learn from them. And we recruit employees with such different backgrounds–teachers, musicians, artists, engineers–that there’s a lot they can teach us. We’ve learned how to value a magnetic personality just as much as proficiency. How to look for intelligence but give just as much weight to kindness. How to find people who want a career, not a job. And we’ve found that when we hire the right people, we can lead rather than manage. We can give each person their own piece of the garden to transform. We’ve learned our best people often provide the best training for the next generation. And that it’s important for every member of our staff to not only feel a connection to their store, but to the teams in Cupertino and to the stores around the world. Because the best ways of doing things usually translate, regardless of language or country.
We’ve also learned that due to the exceptional quality of our applicants, it can be harder to be hired at the Apple Store than in Cupertino. It can sometimes take two to three years to bring someone in. Not because they aren’t right for Apple. But because we want to be sure the opportunity we have to offer is right for them. Why have we learned to be so selective? So careful? Because our people are the soul of the Apple Stores. And together, our team is the strongest ever seen in retail. As beautiful and iconic as our stores may be, the people who create and staff those stores are what matters most.
So on this 3,652nd day, we say thank you to every single one of you. We say thank you to those who were there on the first day, and to those whose first day is today. The past 10 years of the Apple Store have changed Apple as a company. Our experiences, our successes, even our occasional missteps, have made us better. They’ve made Apple better. And it’s because of those experiences, and the ways they’ve changed us, that we can’t wait to see what we’ll learn next. It’s been 10 years. What an amazing first step.
A concise and balanced mix of principles and pragmatics. I loved the tutorial-style game-like program development. This book rekindled my earliest joys of programming. Plus, JavaScript!
An equally important recommendation comes from Shopify’s JavaScript guru, Nick Small, who points anyone who wants to get good at JavaScript to Eloquent JavaScript. Nick’s working on a very interesting JavaScript project (which I’ll write about in a future article) and he’s forgotten more about JavaScript than I’m likely to learn, so I give his JavaScript-related suggestions a lot of credence.
We’ve got a number of dead-tree copies of Eloquent JavaScript floating around Shopify, so I thumbed through one a couple of evenings ago and bought my own shortly afterwards. It’s that well written; my reading that night sold me on the book. I was initially rolling my eyes when I saw the title of the first chapter – Values, Variables and Control Flow – but Haverbeke’s got a gift for presenting things that you’ve seen before, shining a new light on them from an odd angle and giving you a new way of looking at stuff that is so familiar that you hadn’t given it much thought until now. And he does so in an informative, entertaining way, as evidenced by this passage on how to think of variables:
You should imagine variables as tentacles, rather than boxes. They do not contain values; they grasp them – two variables can refer to the same value. Only the values that the program still has a hold on can be accessed by it. When you need to remember something, you grow a tentacle to hold on to it, or you reattach one of your existing tentacles to a new value.
Haverbeke introduces the right stuff at the right time. After the basics, he presents functions, data structures and then error handling, providing a solid base of knowledge for the reader. With those out of the way, he goes on to cover functional programming, then object-oriented programming (most people would do it the other way around, but if you’re not getting into functional programming with JavaScript as soon as possible, you’re missing out on a lot of the power), then modules. After that, there’s a solid chapter on regular expressions and the book closes with four chapters on the most likely application of JavaScript: web development, from the DOM to browser events to what we once used to refer to as “Ajax”. At a svelte 200-ish pages, Eloquent JavaScript covers a lot of ground in less space than many other, lesser books you’ll find cluttering the shelves at your local store.
The only way to truly learn a programming language is to take it for a spin and as Seth Godin likes to put it, “poke the box”. Haverbeke made learning JavaScript from Eloquent JavaScript easier by providing an interactive JavaScript environment. There, you can run any of the examples from the book, make changes to them and see what the results are, and you can even experiment with your own original code.
Eloquent JavaScript is that rare sort of book that works for the person who’s just started programming, the experienced programmer who’s getting started with JavaScript and even the experienced JavaScript programmer who wants to get it right. If you code in JavaScript, this should be on your bookshelf (or in your e-reader).
The old version (free!): The version of Eloquent JavaScript that I’m talking about in this article is the 2011 edition, which is published in paper book and ebook formats. The previous version of the book is available online in the following forms:
A salmagundi (sometimes shortened to salmi) is a 17th-century English dish made of a mashup of ingredients. Every salmagundi I’ve ever seen has always included slices of hard-boiled egg, but beyond that, I’ve seen all manner of ingredients thrown in: roasted and smoked meat, fish and seafood, fruits and vegetables, nuts and flowers, and wildly different kinds of dressings and sauces. Nobody’s sure of the origin of the word, but it’s gotten around, from the French salmigondis, meaning “hodgepodge” and the Jamaican “Solomon Gundy”, a savoury spread made of herring.
In Cory Doctorow’s young adult novel Little Brother, the protagonist Marcus has a computer made up of a mishmash of parts that he calls “The Salmagundi”. I liked the name so much that I’ve decided to use it for posts that are a mishmash of stories, like this one.
Maple Butter / 5 Unconventional Ways to Entrepreneurship
Maple Butter is a new blog for entrepreneurs, and it’s worth checking out. Created by Dan Martell (creator of Flowtown), it describes itself as “a gut-spilling, F-bomb dropping, Woody-Allen-on-a-therapist’s-couch experience” where entrepreneurs and “wantrepreneurs” can get “useful advice that helps you turn traction into triumph”. I can get into that.
The latest article in Maple Butter is 5 Unconventional Ways to Entrepreneurship, a summary of Dan’s recent presentation at Big Omaha. He talks about about his presentation in the video above (taken from Beyond the Pedway), and those 5 unconventional ways are summarized below:
Don’t listen to your parents (at least when it comes to entrepreneurship). Unless your parents are successful entrepreneurs, their advice is more than likely to be biased against entrepreneurship and favour erring on the side of risk avoidance.
Embrace your (enlightened) laziness. Once again, this comes with a qualification: this means using your laziness to come up with an idea that saves people effort or makes their lives easier. It’s laziness as a virtue in the Larry Wall sense.
Choose your friends carefully. Strangely enough, this sounds like advice from your parents, and in this case, you should listen to them. As the saying goes, you’re the average of the 5 people you spend the most time with, and if they’re not pushing, inspiring and challenging you, you’re not going to go far. (This is an observation I’ve made when looking at some over-educated, under-employed, ambition-lacking acquaintances. They are good music recommenders, though.)
Hustle to help. You’ve probably heard this advice, whether you’ve heard the Beatles lyrics “The love you take is equal to the love you make” or read the book How to Make Luck (an underappreciated gem, in my opinion). I have personally experienced this: if you are known for helping others, others will come to your aid.
Failure is part of the process. You learn best from mistakes, so make excellent ones! Make mistakes borne of effort and ambition, not laziness and fear.
Smashing Magazine’s Ten Oddities and Secrets About JavaScript
Ten Oddities and Secrets About JavaScript is a list of curiosities contained within the world’s most simultaneously misunderstood and useful programming languages. Read it and find out how null is an object but not an instance of one, the usefulness of the === operator, the power of regular expressions in JavaScript, fooling your functions into thinking that they’re running in a different scope and how undefined can be defined.
Jacques Matthiej’s Productivity Tips for the Easily Distracted
TechCrunch: Users Say They’re More Likely to Buy if a Business Answers Their Questions on Twitter
The Twitter Q&A search engine service InboxQ conducted a survey of over 2000 young Twitter users and discovered that just shy of two-thirds of the respondents were more likely to buy from a business that answered their questions using Twitter. They’re also almost as likely to follow a business that answers their questions.
The moral of the story? If you’re serious about using social media to promote your company or be in better touch with your customers, make sure you answer your users’ questions!
The Matt Cutts Debunking Flowchart
If you run a public-facing online business – say, a Shopify store – sooner or later, you’re going to have to deal with people saying crazy things about you. Matt Cutts, head of Google’s web spam team as well as its unofficial spokesmodel, does a lot of debunking of the many crazy things and accusations aimed at Google. The graph above, courtesy of Search Engine Land, shows how Matt handles them.
After three years away from all but the most trivial of noodling with the Ruby programming language, I have become a Ruby Foo (as in Mr. T’s catchphrase, “I pity the foo’!”). I am severely out of practice with Ruby, and with two versions having appeared since I last made a living with Rails, even the act of creating a new project is completely different. Since Ruby is the preferred back-end programming language at Shopify and I am the Platform Evangelist, it’s time for me to “sharpen the saw”.
“I’ve been away from Ruby long enough that I’m probably back at newbie level again,” I told Obie between sips of latte made with overcooked beans. “I did it for a bit at the beginning using IronRuby, but between doing all the C# and PHP and the open source ‘Iron’ languages dying of neglect at Microsoft, I’m severely out of practice. I thinking of joining Shopify, and let’s face it: I don’t want to look like an ignoramus in the presence of rock stars like Tobi, Cody and Edward.”
“Give me your email,” said Obie, “and I can do something to help.” Of course he could – he’s the series editor of Addison-Wesley’s Professional Ruby series of books.
Shortly after South by Southwest, a couple of links to PDF editions appeared in my inbox. Thanks, Obie!
The first link was to Eloquent Ruby, Russ Olsen’s guide to speaking idiomatic Ruby and getting the most out of the Ruby programming language. It’s a breezy read, written in the same conversational tone that Olsen used in Design Patterns in Ruby, and the book is broken down into 31 bite-size chapters about a dozen pages in length. Each chapter’s title is some principle for programming eloquent Ruby – the first few are “Write Code That Looks Like Ruby”, “Choose the Right Control Structure” and “Take Advantage of Ruby’s Smart Collections” – and each explains that principle, provides code, shows you where you can find the principles used in actual, working projects. The book straddles the line between tutorial and reference; it’s written in tutorial style, but it’s organized so well that it might as well be a reference for those parts of Ruby that you might not use often (but should) as well as for those parts you keep forgetting (in my case, I always end up having to look up metaprogramming). I’ve been going through it at about a chapter an evening, and I’ve been getting smarter each time. Whether you’re coming back to Ruby after a hiatus like I am or if you just simply want to get better at Ruby, you should have this book in your library.
I have yet to properly sink my teeth into Ruby on Rails 3 Tutorial but a quick scan of the book has shown that it’s quite promising, and the Amazon reviews are bolstering my belief.
I’ll be writing from time to time about my return to Ruby and Rails in this “Ruby Foo” series of posts, and I hope that whether you’re new to the language, returning after a break like me or aiming for “guru” status, that you’ll check out this blog regularly for notes on my explorations and what I’ve learned.
