Colin on the need to break free of batch based MapReduce: “All of these recent shifts from companies like Google, Yahoo, and others no longer see a competitive advantage in batch based MapReduce. The future has arrived, let’s look at some evidence…”
“I follow a style of development that greatly reduces the risk of big projects like Storm. I call this style “suffering-oriented programming.” Suffering-oriented programming can be summarized like so: don’t build technology unless you feel the pain of not having it. It applies to the big, architectural decisions as well as the smaller everyday programming decisions. Suffering-oriented programming greatly reduces risk by ensuring that you’re always working on something important, and it ensures that you are well-versed in a problem space before attempting a large investment.
I have a mantra for suffering-oriented programming: “First make it possible. Then make it beautiful. Then make it fast.””