You can read the article here. Below you'll find the github links and relevant instructions for each implementation of Granny's Address book.
Skip to your favorite language
It may surprise some of you that despite my open source roots and business, I’m not on the whole a big fan of telecommuting. I’ve worked for companies where it worked and companies where it didn’t. I nodded my head when I read about Mayer’s switching Yahoo away from telecommuting. She is totally right.
Bad developer habits die hard. If you don't load test as you go, you're asking for a nasty surprise at the end of your project.
Scalability and performance are not the same thing. Developers used to say, "Hey, it works on my machine." Now they say, "Hey, it was fast on my machine." But it's different in production or under load. Unbelievably, most organizations still fail to do adequate performance or load testing -- nor have they integrated performance and scalability into their systems.
Contrary to the rants you read on Stack Overflow and Hacker News, Oracle is still your only option in many cases -- even when you need scalability and high availability
For the record, I'm a NoSQLer and a big data guy. After nearly 20 years of dealing with what I've come to refer to as "the beast" (aka Oracle), I've turned coat and decided I prefer solving the problem rather than mitigating it.
Authored by: Phil Rhodes, Senior Consultant at Open Software Integrators
Natural Language Processing (NLP) has a long history, dating back to the earliest days of computer science. Computer scientists have been working on means to allow machines to “understand” written language for decades now. And while the field suffered some setbacks in the 1960's and again during the “AI Winters” of the 1970’s and late 1980s, significant progress has been made, and freely available, open-source toolkits make it possible for almost any organization to begin taking advantage of this powerful technology.