Every once in a while, you have to put in a heroic effort to diagnose a bug. When you finally figure it out, you want to run around the office singing “We are the champions”, even if it turns out to be a trivial issue. Because that doesn’t mean it took a trivial amount of effort.
What, if anything, ties IoT the numerous and varied aspects of IoT together? If you ask Tim Kellogg, it's a simple answer: AllJoyn, an open source project of the AllSeen Alliance meant to create universal and accessible interfaces for IoT development.
Nhan Ngo, a QA engineer at Spotify, made a series of illustrations about visualizing Continuous Delivery that are available under a Creative Commons license. She's done an amazing job at making a concept easy to visualize that many are unable to understand even after a great deal of educating.
Some months ago the first version of open source HTML5 NextCharts was released. You can read this article here. In the second release of the NextCharts project, it was time to add some simple widgets like alarm, indicator and display.
Back when Adam Cameron and I launched the ColdFusion UI - The Right Way project, I mentioned that initially we would accept submissions from the community to build out the content before releasing an actual readable version. Earlier this week I got off my rear and actually built a process to make this happen.
Basically EVERYONE is talking about it right now. But, really, why has it become so popular all of a sudden? Sounds like yet another web technology like any other else, right? Well, in a nutshell... (continue reading)
Most businesses depend on third parties to reliably deliver products or services to their customers. E-commerce sites rely on delivery services. Broadcasters rely on cable and satellite providers. And web platforms rely on cloud infrastructure to keep their systems accessible.
New developers joining a project will often find that the project won't build cleanly on their machine, and hours of time will be sunk into setting up the project so work can start. Counter this by using continuous integration to build your project from scratch.
So what is Netflix doing instead? It is focusing on the known developers who wish to use its APIs. As the ProgrammableWeb article explains, this "small group of known developers" is what is contributing mostly to the usage of the Netflix APIs. This makes perfect sense.