“If you’re sick, stay home and rest.”
A simple statement, and one that makes an immense amount of sense. Fact of life: anyone can get sick. Some people invariably tend to get sick more then others; this can be the result of genes, lifestyle, diet, and likely other reasons I’m not thinking of at the moment.
Alice stayed home sick yesterday; she was throwing up, had a fever, and quite a nasty cough. She ended up staying home to rest today as well, as she’s not feeling much better and wasn’t even sure she’d be able to make the transit trip without throwing up on the skyrail, let alone last through the day.
And she’s feeling horrible guilty about it.
Wait, what? Something isn’t right here; she’s obviously sick, and it is logical that she stay home to rest, isn’t it?
Officially, people will tell you yes. But have you ever felt that hegemony that you’re never really sick enough to warrant missing work? That only weak, undedicated people miss work due to illness? That if you’re sick, you should stay home, but that now really isn’t a good time to be sick, as there is so much work to be done?
I have. It exists at all levels of jobs, but I’ve found it to the worst in minimum wage jobs – the jobs where, although you technically can call in sick, the managers are always very unhappy when you do (or maybe I just had a bad manager – I recognize my own experiences might not be universal).
Please don’t misunderstand me; her company, this time, has been exemplary in that she hasn’t previously felt that pressure; they honestly seem to care about the health and well-being of their employees. But she has before, while working for other companies. And today, even if her company seems to recognize the logic of staying home to rest when she is sick, she still has that sense of guilt at missing work.
Work can generally wait, people. Very rarely is it actually a matter of life or death.
Gaaah, I do so find it frustrating!
One of the topics I wish to discuss is the difference I perceive between following recipes and cooking. Do not misunderstand me, there is nothing wrong with using recipes; they are quite useful, and allow someone to attempt dishes they may never have been exposed to before. However, learning how to cook is about a lot more than simply following recipes.
Learning how to cook involves learning why you do certain steps in a recipe. Being told to fry the chopped onion for 3 to 4 minutes on medium heat is only really useful if you know what the end result is supposed to look like, and not all stovetop burners heat to the same temperature when set to medium.
My other major complaint with a recipe approach to cooking is the waste of ingredients that tends to occur. You’ll buy what you need, use part of it for the recipe, and suddenly you’re left with all these ingredients you don’t know what to do with. This is a cycle we want to avoid!
In my blog, I don’t just want to share recipes; I want to help people learn how to cook. Cooking can be a lot of fun, and a very satisfying experience.
And hey, as my dad put it to me back in high school, knowing how to whip up a tasty meal is never a bad thing when there’s a girl you’re trying to impress. And the opposite holds true too (and half opposite – girl impressing girl, or guy impressing guy).