The interesting thing about Baccarat is that despite the odds, despite common sense, despite the understanding that the game is completely random, people will still sit there and record every single hand and score trying to use it to look for patterns to predict future results. Programming is similar.
For a while I've been thinking about what makes me like or dislike a project. Having spent a very big part of my career working for consultancy companies, I was exposed to many different environments, industries, team sizes, processes and technologies.
From March 5th 2013 Twitter are removing there current API and it will be fully replaced with the new API V1.1. This means that any application that is currently using the old API will stop working on March 5th. The main feature of the API is that requests need to be authenticated before they will work correctly.
This is the second excerpt from Scrum101, the free intensive online introduction to Scrum, which I introduced several weeks ago. In this second except, I’d like to share the most popular Scrum 101 lesson at the moment.
I found a very good review of ZeroMQ from Pieter Hintjens, a veteran in distributed software. He not only had a strength and weakness review of ZeroMQ, but he also had an interesting and critical take on a popular message queue, RabbitMQ.
An article by a Cornell professor sparks a debate about MongoDB's fault-tolerance, and we get to see how the CEO of Evernote gets things done. Plus Drupal 8 gets a new default editor and the greatest CSS3 demo of all time arrives!
I’ve been working with geographically distributed and dispersed teams for the past couple of years. Some of them on quite large programs, some of them reasonably small. What they all have in common is that they all want to transition to agile.