It took me 5 days (and I had a full-day meeting on one of them) to deliver >80% of the goodness. Alone.
...so you should have almost no confidence in your implementation, or accept that you’re dealing with an orders-of-mangnitude easier version of the problem than Google is.
I understood the point to be the latter. Like, the usual rule of thumb is that 20% of the effort produces 80% of the value, and Drahflow is claiming that in this instance 0.0068% of the effort produced 80% of the value. (Assuming that Google Wave was developed by a hundred-person team).
Wave was certainly not developed by a hundred-person team. That article says that the “enabling technologies” behind Wave, including GWT and Google’s XMPP fork, comprise a hundred-person team, which I could maybe believe between three or four of Google’s key infrastructure projects at the time.
I think in Wave’s case, as an innovative technology that had no clear predecessor, most of the two years is probably design, not development. Wave missed its mark, so none of that design is really re-usable.
...so you should have almost no confidence in your implementation, or accept that you’re dealing with an orders-of-mangnitude easier version of the problem than Google is.
I understood the point to be the latter. Like, the usual rule of thumb is that 20% of the effort produces 80% of the value, and Drahflow is claiming that in this instance 0.0068% of the effort produced 80% of the value. (Assuming that Google Wave was developed by a hundred-person team).
Wave was certainly not developed by a hundred-person team. That article says that the “enabling technologies” behind Wave, including GWT and Google’s XMPP fork, comprise a hundred-person team, which I could maybe believe between three or four of Google’s key infrastructure projects at the time.
I think in Wave’s case, as an innovative technology that had no clear predecessor, most of the two years is probably design, not development. Wave missed its mark, so none of that design is really re-usable.