About /recipes/

May I have your attention please. This is now exclusively a food blog. No further questions. Thank you.

In the wake of the mushroom stroganoff incident I started keeping more plaintext backups of recipes, mostly in Google Keep. Given Google's history of killing things, this was probably not a great idea. When I needed to reference a recipe, I would open the note on my phone in the kitchen, and read it there.

Instead of Google Keep, I've played around with different recipe apps, but didn't really like any of them. I was always like 'eh, one day I'll just make one that does what I want'. I have decided that it's finally time to make the thing that does what I want. As I've done more home cooking in the last few years, I think I have enough experience that I can tell what would be useful, and what would be superfluous.

I swear, it's not just me being lazy. In reality, I think the killer app isn't an app at all, it's a laminated recipe book. No dealing with getting food on your precious technology - the phone stays in another room, away from the flour and cornstarch. Earbuds can reach from a ways away, and have touch controls on them. The reason I need a digital recipe presence at all is really for backups. That laminated recipe book is prone to getting lost, damaged, stolen, etc. I also don't currently own a laminator or printer, but I do own a computer. With a backup source that I control, I can easily do something like generate a pdf of all my stored recipes. It's also nice for sharing with others, as I can send them a link that I know works (and isn't an ad-ridden mess) instead of emailing it or sharing on Google Drive or using some other annoying format. I can also add any notes I have to the recipe without fear of ~pick: running out of space/not being able to read my handwriting~.

So, there you have it. To summarize, by storing recipes on my blog, I get:

• easy backups
• easy sharing
• easy to add content
• easy to add notes later

I'll start adding things here as I make them.