HN user

whtrbt

120 karma
Posts3
Comments65
View on HN

I used to want this kind of recipe card, but I've cooked so much that's no longer the case (I actually forgot all about the idea until reading this comment). I can usually look at the list of ingredients, and imagine what needs to be done. If it's an unusual or unfamiliar cuisine I will read the method, but after that point the list of ingredients suffice. If I read a recipe somewhere and want to cook it later, I will just write the ingredients on a post-it (usually in cooking order) and maybe 1-2 brief comments.

I imagine in domains you are skilled at you'd also prefer high level instructions than a step-by-step tutorial.

I agree that doesn't help the beginner, or someone who doesn't cook regularly, or someone cooking something new and I think most recipe writers are just following the established structure without thinking about what they and others really need.

Play Aardwolf MUD 7 months ago

It’s certainly possible, but you don’t need to go to any trouble - I’d hate to have misremembered the name and waste your time.

Play Aardwolf MUD 7 months ago

There was a MUD I read a printout of the textile manual for when I was a kid (didn’t have a computer). It explained how to create mobs and zones, and one of the example characters they used repeatedly was a knight or paladin called Geoffrey. I think it also introduced me to kobolds.

I’d love to find it again and reread it.

I thought it was called Legends but that hasn’t turned up the same thing.

Maybe stupid answer, but I’ve read a few older papers that used ensembles to identify when a prediction is out of distribution. Not sure what SotA approach is though.

You're going to be battling with your attention a lot in the beginning. I think just making a habit of it regardless and putting in the time is necessary.

You could always go on a retreat — you'll have very limited options for distractions. It might sound like an extreme thing to do, and maybe it is, but I did it without much prior practice and got a lot out of it.

I read the docs too. Great docs can spell the difference between using your code and giving up or finding another solution. If you're new to a particular language or programming, code with great docs can also teach you how the language itself works.

Tabulator (http://tabulator.info/docs/5.3) is the last example that comes to mind, had to use it earlier this year.

We use a kotatsu [0] for this - a table with a heating element underneath and a thick quilted 'tablecloth'. I'm in Melbourne, so the lowest it gets is a few degrees above 0C, but we _never_ use air con/heating. Summer we close the blinds in the day, open blinds and windows up at night.

It's not fair to expect that approach to work for everyone everywhere, but there are plenty that could do this instead of wasting so much energy on creating a homogenous environment year round.

[0] https://en.wikipedia.org/wiki/Kotatsu

I think the type of estimation meant here is the agile type, where the team looks at a feature/requirement and estimates the time or relative effort based on the nature of the requirement + whatever other factors they choose. It's usually more intuitive and not based on historical data.