bradyo
Joined 14 years ago
Joined 14 years ago
* over-abstract (where you could replace the abstraction name with a slightly more verbose but clearer definition)
* over-generalize (it's a meeting about handling returns in multiple physical locations but they keep talking about "channels" instead of physical locations)
* propagate abstractions without actually understanding the underlying concrete implementation (they know omni-channel means having multiple ways to return, but not exactly which ones)
But yeah as the consumer of abstractions you have to dig into the definition and understand the context in which it's applied in order to understand what's going on
Mayo clinic, Harvard health, and pubmeb do a great job with health info. IMDb for movies, Goodreads for books, *gearlab.com for reviews, booking.com for accomodations.
I think the biggest threat to Google isn't a better general search engine, it's user behavior switching to more domain-specific websites as the top of the funnel. E.g. people going directly to Amazon to search for products instead of first searching Google.
To some extent, Google has figured this out, which is why they now have a dedicated flight search, hotel search, product search (Google shopping still exists and it's pretty good!), etc.
I had the same reaction! The information density is perfect. If anybody else loved this book and has similar recommendations, please share.
Hasura also some limited support for generated multi-table transactional APIs, which Postgrest doesn't. Meanwhile, Firebase supports arbitrary read-modify-write transactions.
This team has its work cut out for them and I can see a fierce competition with Hasura and Firebase.