What does the origin of DevOps teach us?

Recently, I read an interesting story on how the name DevOps came about.


True enough, as an “afanaciado” of DevOps movement, I didn’t know this story. It even had a reference to the city I work in – Toronto. It is home to one of the two people that caused this name to appear! I am feeling proud, now:-) As I read the story, I was intrigued with Patrick Debrois and Andrew Shafer’s tenacity to pursue what they believe is important for two years in the face of seemingly indifference from the fellow community members. In addition, Patrick’s courage to organize the first #DevOps conference in 2009 on a brand new topic further proved that if you believe in something, follow it up with action, then you will be rewarded. That reward may not be success as in this case, but the experience itself will be reward enough.

That is one of the fundamental pillars of agile. Don’t wait for everything to be ready. Don’t expect all the documentations will be complete. Don’t even think you can spec out all the possible edge cases before building the software. Do execute on what you already know. Get feedback quickly and then build on top of that. You will be rewarded with information/knowledge that otherwise will just be a design/estimate/assumption/risk. As an added bonus, you might just get a working product that’s right for the customer. Isn’t that nice 🙂