You could improve upon this by establishing site authority for a topic (cuisine), but it still seemed pointless to me.
394 karma · joined January 26, 2018
You could improve upon this by establishing site authority for a topic (cuisine), but it still seemed pointless to me.
Looks like they actually might have added locking recently with https://github.com/pulumi/pulumi/pull/2697 but I haven't looked deeply
The context of this HN post is about originality itself.
It's also arguably not an equivalent comparison. Many people attending these bootcamps have already graduated college and tend to forgo work to attend - there is a huge opportunity cost even if they don't directly lose money. I have no reason to believe the model wouldn't work, but there's ample evidence that the implementation of the model via Lambda is flawed.
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.
Of course, the same could happen for standard REST as well, but I think the foot guns are more limited.
For example, "1/2 cup of diced tomatoes or a can of tomatoes (preferably san marzano)". This sort of freeform text doesn't suit regex very well but also lacks substantial context clues. You'd most likely use named entity recognition which could recognize that "1/2" is a quantity, "cup" is the unit, etc. but I haven't gotten very good results yet.
Maybe I'll write up a post when I land on a solution.
I do wish normal cooking recipes had a similar convention - it's rare that I've ever used exact amounts since the ratio and technique are always more important.
Possibly a more interesting approach could be gated support similar to an exclusive discord for patreon subs to ask questions.
As an example, look at low-code for inspiration to determine what features people need which aren't being filled by existing solutions. Hopefully that reduces the need to compete via feature checklist.
Even if Haskell was objectively the 'best' language, it'd likely be a poor choice for most teams simply due to familiarity and developer speed.
I'd be extremely hesitant to hire the services of this company entirely because they use Haskell and it'd be a nightmare to maintain after their contract.