Please don't build software just because Google published a paper. First off, it's not like it's a great design just because Google created it, they've churned

Please don't build software just because Google published a paper. First off, it's not like it's a great design just because Google created it, they've churned out some real stinkers. And it's not like the code is guaranteed to be good; because you're not a Google engineer, you can't possibly be a God-like super-coder who designs nothing but perfect systems. (Or so you'd think from the way people fetishize FAANG papers) The most frequent design mistake I see is an engineer with a "hammers before nails" complex. They want a perfect design that will work for everything (that they have so far thought of) in some beautiful and hidden way. So they build the thing, and they think it's great. And then they go to hook it up to products... and it doesn't work well. The user story, the context diagram, and the mock-up all need to come first, not the code.