Re:Why WhatsApp Only Needs 50 Engineers for Its 900M Users
by Alupis on Wednesday September 16, 2015 @11:10AM
(#10227179)
Pretty much every single one of your test cases has already been solved in the XMPP specification, which WhatsApp is likely using (essentially all modern chat services/servers/clients speak XMPP).
[ Parent
| on HN ]
Re:Why WhatsApp Only Needs 50 Engineers for Its 900M Users
by lordnacho on Wednesday September 16, 2015 @11:23AM
(#10227269)
Sure. And someone's got to take the XMPP package and put it on the different platforms, test them all for correctness, etc. I'm not saying there aren't existing parts that can be used. But even if you have a plausible component, someone's got to look at the docs, maybe build a toy version, think about whether you're hitting the limits, integrate with the rest of the codebase, and so on.
It's easy to see what pieces you need. But there's still work in glueing them together and testing the result.
I think 50 is a sensible number of in-house engineers for this sort of thing. You want cover as well in case someone leaves or gets ill. You want people to be able to upgrade the system when things change. You want people to look ahead at future requirements. And you want to be able to do these things all at once, with slack built in for peak load.
Re:Why WhatsApp Only Needs 50 Engineers for Its 900M Users
by Alupis on Wednesday September 16, 2015 @11:47AM
(#10227473)
Well, you sort of are making my point -- 50 engineers is plenty (maybe even too many) to cobble together a solution to a problem that already has been solved and solved again.
WhatsApp did nothing technically challenging, but they did strap a business model (err, sort of) to something many others failed to capitalize on.