the open-sourcing of Rest.li, a piece of infrastructure developed and used here at LinkedIn. Rest.li is a REST+JSON framework for building robust, scalable service architectures using dynamic discovery and simple asynchronous APIs. We feel that Rest.li fills a niche for building RESTful service architectures at scale, offering a developer workflow for defining data and REST APIs that promotes uniform interfaces, consistent data modeling, type-safety, and compatibility-checked API evolution.
Walmart started using big data even before the term big data became known in the industry and in 2012 they moved from an experiential 10-node Hadoop cluster to a 250-node Hadoop cluster. At the same time they developed new tools to migrate their existing data on Oracle, Netezza and Greenplum hardware to their own systems. The objective was to consolidate 10 different websites into one website and store all incoming data in the new Hadoop cluster. Since then they have made big steps in integrating big data into the DNA of Walmart.
Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services. The overarching goal of Swagger is to enable client and documentation systems to update at the same pace as the server. The documentation of methods, parameters, and models are tightly integrated into the server code, allowing APIs to always stay in sync. With Swagger, deploying managing, and using powerful APIs has never been easier.
(Full Story: https://developers.helloreverb.com/swagger/ )
Sonar is the most polished tool in the code quality space, and literally includes PMD, FindBugs and Checkstyle all in a single package, plus some excellent support for tools in the Java ecosystem. You can find plugins readily available for all sorts of useful tools: Checkstyle, Clover, Cobertura, Emma, FindBugs, JaCoCo, PMD. Sonar is used as more of an orchestration engine, letting you call on all of the previous tools and aggregating their results. It is very convenient to use, especially if you’re already using Maven, and certainly helps you “get your technical debt” under control. In a large, enterprise environment, Sonar and some combination of the previous tools is essential. (http://zeroturnaround.com/labs/code-quality-tools-review-for-2013-sonar-findbugs-pmd-and-checkstyle/#!/)
(Full Story: http://www.sonarsource.org/ )
Remember the revolutionary insight, common to great managers: People don’t change that much. Don’t waste time trying to put in what was left out. Try to draw out what was left in. That is hard enough. If you apply their insight to the core activities of the catalyst role, this is what you see: When selecting someone, they select for talent . . . not simply experience, intelligence, or determination. When setting expectations, they define the right outcomes . . . not the right steps. When motivating someone, they focus on strengths . . . not on his weaknesses When developing someone, they help him find the right fit . . . not simply the next rung on the ladder.
Rule of Thumb #4 “There are No Steps Leading to Customer Satisfaction” – Required steps only prevent dissatisfaction. They cannot drive customer satisfaction. Level 1 – At the lowest level, customers expect accuracy. Level 2 – Customers expect availability. Level 3 – Customers expect partnership. Level 4 – The most advanced level of customer satisfaction is advice.
So the only solution is for Heroku to return to routing requests intelligently. They claim that this is hard for them to scale, anExplaind that it complicates things for more “modern” concurrent apps like those built with Node.js and Tornado. But Rails is and always has been Heroku’s bread and butter, and Rails isn’t multi-threaded. In fact a routing layer designed for non-blocking, evented, realtime app servers like Node and its ilk — a routing layer that assumes every dyno in a pool is as capable of serving a request as any other — is about as bad as it gets for Rails, where almost the opposite is true: the available dynos are perfectly snappy and the others, until they become available, are useless. The unfortunate conclusion being that Heroku is not appropriate for any Rails app that’s more than a toy.
(Full Story: http://rapgenius.com/James-somers-herokus-ugly-secret-lyrics )
"We’re very comfortable with this idea of BYOD," Congdon told CITEworld. "We view consumer technologies in our daily operations as a core technology for us." That means that when employees find a consumer app that works for them and helps them with their jobs, Congdon and his team want to hear about them.
But before I do I want to make a point. TDD is a discipline for programmers like double-entry bookkeeping is for accountants or sterile procedure is for surgeons. Are there times when accountants don’t use double-entry bookkeeping? Are there times when surgeons don’t use sterile procedure?
So until a startup is rich and successful, it makes sense to just live with your Amazon addiction and suffer the occasional outage with the “blame Amazon” explanation. Startup CEOs should be sure to tell everyone about this dependency in advance so that such a failure doesn’t come as a surprise. But Netflix is beyond that stage. It is time for Netflix to start recovering from Amazon addiction and take full responsibility for the quality of its service.