slow_donkey

I tried solving this with a search engine that accounted for reviews with some manual curation, but I realized there's actually an extremely limited set of 'good' recipe sites and kept returning the same 10 sites with a long tail of average sites.

You could improve upon this by establishing site authority for a topic (cuisine), but it still seemed pointless to me.

To be fair this is a very very old list dating back to 2006/2008 and these were the pizza names that came up constantly at that time - it's also only rating the shops that he personally traveled to which were predominantly NY/Neapolitan because that's likely what he was benchmarking his own restaurant against.

I agree with you but nothing about the comment was discussing whether or not people will pay for repl.it

The context of this HN post is about originality itself.

Hm any competent ops team would have backups if they really cared to find your original data

IMO before react native came on the scene there were no well performing hybrid app frameworks except possibly xamarin. So it likely wasn't your fault

I haven't reviewed their numbers recently but the historical criticism is that you end up paying more money for Lambda yet their placement rate was lower compared to similar bootcamps.

I'm building a search engine for this exact issue - there's 10000 recipes for every dish but they have to be contextualized: Do I want mac and cheese in the next 30 minutes or am I serving this for Thanksgiving? Those are 2 different experiences and recipes.

Even the base issue of at least ranking recipe blogs by quality isn't solved by other aggregators such as Google / Yummly which are more of a recipe dump.

If you or anyone else is interested I'm planning to release a version in the coming weeks - email is in profile.

So I have the same issue. On Slack, I can't tell if someone is busy - almost no one sets their status as away unless they're actually offline. Whereas in the office it was easier to assess via headphones or if they've just gotten up from their desk etc.

How dare you question the snark

I don't disagree with you, but graphql just lends itself well to bad decisions and many times when I've poked at graphql endpoints they share these issues (missing auth after first later, exposing schema by accident, no depth/cost limit). I think a combination of new technology w/o standardized best practices and startups being resource constrained proliferates poor security with graphql.

Of course, the same could happen for standard REST as well, but I think the foot guns are more limited.

If you're in a major metro local meetup/slacks are a great tool. They'll provide the intro without you needing to 'know' the person. I've done that successfully with engineering positions and you could likely go through engineers if the (JS) community is larger.