51–60 of 132 posts
The best foods are fermented. :9
https://en.wikipedia.org/wiki/Garum ? Strange how such a wildly popular sauce vanished from the face of the Earth.
Also, I'd posit that Worcestershire sauce is the spiritual descendant of garum.
I know some people think it's heavy on the vinegar, but there's nothing wrong with original Tabasco – peppers, vinegar, salt. No modern food additives.
Interesting use of github How do you know Microsoft won’t steal your secret sauce?
A recipe without 10 pages of useless, boilerplate SEO content?
I have recently purchased an instant pot the SEO content on recipes searched for drive me mad
Why github? You couldn’t just use pastebin? It’s a recipe! How much collaboration are you expecting to happen? Are you expecting people to file issues about your chili sauce?
Wouldn't that be great? If you think about it, it's surprising how GitHub's potential as a platform has been solely used for code up until now, taking into account that pretty much anything that can be represented as text may benefit from its "social coding" features.
2013 jduclos.com/notes/github-for-lawyers
Previous HN Discussion on the topic from 2017 https://news.ycombinator.com/item?id=13446275
A recipe without 10 pages of useless, boilerplate SEO content?
I have recently purchased an instant pot the SEO content on recipes searched for drive me mad
Habanero chili is extremely hot but has a sweet, fruity flavor. I haven't tasted piri piri chili, but I'm sure this sauce is delicious. I'm kinda upset the chilis are deseeded, though.
Earlier quoted context omitted.
I sure hope someone would fork it and iterate on the recipe, that's why version control exists. So you can have, you know, versions. Recipes are like software, except food pops out. Change the recipe, change the food. Change the recipe a little, change the food a little. Why wouldn't you want to post it to Github?
I'm not opposed to the idea, it just seems like a stretch of what github is made for. What did they select as the programming language for the repo? Junior devs struggle with git concepts, how will this catch on for mainstream recipe users? Recipes are nothing like software. Software can return expected results for everyone who uses it. But everyone can tell you a story of a recipe not turning out right. The hardware…
Not a bad point, I didn't think about it like that. However, I think this would be more useful to the people who are competent enough to implement nuanced recipes. Small changes in the recipe can lead to large changes in the food, much larger than the error between competent cooks. What if you have different tastes than the original recipe, and I like your taste? I'd wanna know about your changes, especially if I had the skills to implement them and I had a passion for cooking.
Plus, Generations have already been iterating and verbally passing down recipes for thousands of years. Most of that history is gone, and all we have is a thin slice which is what we know today. You only stand to gain by using version control for recipes.
But sure, Github probably won't explode as the go-to recipe database, because the intersection of git users and competent cooks is small compared the amount of cooks.
> It's also just a cheap post. What, now we can upload otherwise unnoteworthy content to github, and suddenly we're on the front page of HN?
This is not too important to me. Hey, we're all here talking about the post, so maybe it is noteworthy.
A recipe without 10 pages of useless, boilerplate SEO content?
I have recently purchased an instant pot the SEO content on recipes searched for drive me mad