Risk Management
I met with Dwight (co-founder of DoubleClick) when I was out in NYC. He congratulated our product launch. He read my blog, commented:“You have a great team, it sounds like it.” – Just like how Dwight would say things. He was very interested in our ROR UI, told me that one of the projects he did was using ROR too. We also talked about Hadoop backend – which I have yet to blog about. I asked him to check out Erlang and asked for his opinion. — Watch out, Jack ![]()
I asked him: the product has now launched, what should I lookout for next? “Risk Management” — Dwight said. I nodded. We all know exactly what “Risk Management” means coming from the ASP operation background. We went on and talked about how you should NEVER go down. This reminded me the operation “Dos and Donots” tips that I sent out to FreeWheel engineering group. We also talked about how to make technical trade-off decisions to maintain a right balance between stability/availability and cost, as it is always true that the cost would shoot to roof when you try to cover the last 0.01% risk cases.
I really enjoyed my short visit. Dwight is a wise man, no doubt. I have loved to go to him for advices all these years. I am looking forward to talking to him again.
Btw: I met a lot of familiar faces at Dwight's place too. It is good to run into friends everywhere.


Never mind. From the risk management perspective, if we could not fix a problem, the worst case is that we have to fix Erlang...
Thank God it is open source.
Reply to this