Amazon gives each team independence. Therefore it is virtually impossible to insist on consistency between what different teams do. Each team makes sense on its own, but the whole can be very, very confusing.
Google has a process that results in much greater internal consistency. It may not be a great UX, but it is consistent. Inside and out.
For small systems, Amazon is going to give a better UX. But for a complex system, I prefer what Google will produce.
as a long time Google user, I find it pretty ironic to use consistency and Google in the same sentence. If consistency exists internally at Google, none of it made in to their products unfortunately.
> But for a complex system, I prefer what Google will produce
Having worked there in teams near to their tablets I really think Amazon would have a hard time producing software of the complexity of Android or Chrome.
I have a question. Do you think this Amazon culture is the cause or the result of service-oriented architecture at Amazon? Or maybe am I completely off the mark here.
I found this quote from SEC filings. Jeff Bezos says:
> Service-oriented architecture -- or SOA -- is the fundamental building abstraction for Amazon technologies.
You mean the way Google piggy-packed on Apples work which in turn piggy-backed on KDEs work? Amazon did an extension to optimise rendering on small devices, which is complexity wise not too far off to what Apple & Google contributed to the rendering engines, which at the end is the tricky bit an a browser, not the Chrome.
Really don't understand the downvotes. Whether they gave back to the community or not is another story, but they did piggy-back on previous code, even though adding a lot themselves and giving back a lot, but it still built on massive existing work.
Apparently Amazon also puts developers into the customer support rotation. If you want to improve customer experience, this is a great idea. I've worked small-medium business support before, and you're generally treated like chaff by the devs, who don't get to wear their own cut corners and bad decisions.
Amazon gives each team independence. Therefore it is virtually impossible to insist on consistency between what different teams do. Each team makes sense on its own, but the whole can be very, very confusing.
Google has a process that results in much greater internal consistency. It may not be a great UX, but it is consistent. Inside and out.
For small systems, Amazon is going to give a better UX. But for a complex system, I prefer what Google will produce.