Agree that it's an abstraction that OP doesn't know the definition of, but there's also a tendency for people to
* 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
Part of the problem is that the in-app purchase cut isn't just for payments infra, it also includes the rest of the infrastructure and value prop for the app store(s), which is otherwise only $100/year, which is nothing for huge companies. The problem is they also force users to use the official app store. tbf this is all less true on Android. I feel like a competitive market would have decoupled these costs.
Yeah the comments in this thread are baffling (or they didn't read the 100 character tweet lol). The tweet is just describing domain specific database-like websites. Have people not heard of allrecipes.com? Yummly? Or one of the other thousands of recipe db sites? No blogspam, just structured recipe search. You can even search by ingredient!
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.
Yeah this feels a little bit like a declarative configuration file for Hasura/Firebase (which is already a good idea). Looking forward to seeing how far you can take the frontend stuff!
A lot of commenters are focusing on the RPA part, but what seems to be more novel (to me at least) is the passive discovery of what could be automated with RPA. That seems like a generically hard problem, good luck!
Yeah, this title is currently overadvertising the product. Without even getting into the non-OLTP DB parts of Firebase, Hasura is much further along towards being a Firebase replacement. It already handles auth and a basic admin UI for both the schema and data. I respect the vision and welcome more competition, but this seems to just stitch a "push" system to Postgrest for now (with no auth to boot).
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.
Until yesterday, I would've voted Prisma. There was actually a Show HN post recently that debuted Zapatos: https://news.ycombinator.com/item?id=23273543. The top comment also mentions mammoth: https://github.com/Ff00ff/mammoth. Probably going to switch over to one of them as they're closer to raw to raw SQl and well typed.
As far as I can tell, prisma has turned into just an open source typescript query builder (probably the best in it's class though). Prisma used to be graph.cool which was very similar to Hasura.
If you didn't have unlimited PTO, how much would you be happy with? Tell, not ask, your manager your expectation. This is ideally done immediately upon starting. Afterwards, act like you have that amount of a vacation, and then take it.
I want a social network consisting entirely of people who have walked the walk before writing about it please. The r/ask* subs are a decent start. Experts in their field who tweet about their field (and not unrelated bullshit that's hard to filter out) are also great. Would pay.
"Filling business needs" is also not an objectively useful thing. There are many businesses I would prefer not advertise (e.g. cigarette and gun companies) and many more industries that are nearly zero-sum (and thus advertising just moves a fixed pool of money around). I'm not sure where this idea that growth for the sake of growth is inherently good came from. In fact, we've demonstrated many ways it's harmful.
> As a former Googler, I can see why people post these: internally Google is hyper-evangelized as the best place to work ever (why would you work anywhere else). When leaving, its a necessary step to form a good argument for yourself as to why you've decided to go against the culture.
As another former Googler, this was one of the most concerning things about my experience at Google. The pressure I put on myself and received from others when I was debating whether to leave was enormous, especially because it was my first job. Nevermind the rampant imposter syndrome while you still work there. In hindsight, it was super toxic and led me to stay there even longer than was good for me and burning out harder. I've talked to a few current Googlers and Xooglers who also felt that way.
And on the flip side, if you're the interviewee and you don't pass an interview, try not to beat yourself up. It just means the interviewer / interviewing company is looking for something different.
* 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