 You learned at scale with HBase. Obviously for folks out there, you guys are a great example of, to me, the future application that enterprises are struggling with. I mean, Facebook, you just had a clean sheet of paper, built a great platform, your product model has been about introducing products and iterating fast, no real clunky R&D team, slow things down. It's really applied research in real time. So you launch some stuff, smaller teams, really good code of ethical over there within among the engineers, which is cool. What have you learned and what could you share for the folks out there who are moving to cloud, building their apps, trying to be more app-ified in the sense of being like a Facebook, in the sense of being an IT ops, dev ops environment. What are the biggest challenges? Well, one thing I'd say that I love about Facebook is the way that our ops and dev ops work is we have what we call app ops people that are on our engineering teams. So rather than kind of in a lot of organizations there's a distinct wall. There's engineering and there's operations and there's a lot of finger pointing and the other main problem is the fact that Hadoop and H-Base and these other technologies, they're so early that there's no such thing as ops. I mean, it's engineering. It's engineering ops, right? So it's one thing that I've really, really liked is we have ops guys that have an engineering bent and then all of our engineers are very kind of aware of ops and so it's created a really good environment and allowed us to iterate quickly there. That's the culture, basically. You got a culture. That's the culture. If you have that siloed ops skills, you're screwed, basically is what you're saying. But I'm saying that. He didn't say that. I said that. It's an uphill battle and it depends on the ops guys and there's nothing like sitting with people. I mean, in the end of the day, people are people and sitting with people, you become tolerant and you understand what their position is.