> NestJS is one of those things where people coming from other languages like Java don't know how to develop without the patterns that Java gave them.
This is EXACTLY how I felt using NestJS. Except, IMO, it took the worst part of Java (Spring DI, esp. the over-verbose, make-changes-in-4-random-files-to-get-an-object style they did it circa early 2010s, instead of the much cleaner styles they have today) and shoved it into a language that is built on a completely different paradigms and constraints.
Not had a single pleasant experience working with NestJS, especially once it hits a certain scale, and you are just bogged down running between modules, services, controllers and DI-hell
"Imagine spending one hour in the kitchen to only feed yourself one time. That would be peak insanity to me today."
YMMV. For me, spending time cooking is a great way to take a break from my computer and spend time away from a screen. And like showering, the process of cooking is now mechanical enough that it allows me to focus on broader tangents in whatever I'm working on and set myself up for the next session of coding/building stuff, and now with a full tummy.
I life in a country where fresh produce is readily (and cheaply) available, so I find things like weeklong mealprep (especially, pre-chopping veggies for the week), and eating microwaved food from the freezer ridiculous, both from a taste as well as a health perspective.
Honestly, I think the trick is to have a set of a 12-15 recipes that you can fall back to, and once you have a hang of it, it's easy to create interesting variations with your food! Of course, YMMV
"Much of it (not all) is science and engineering. You can robotically produce incredible meals. And I argue you should" - This I agree with 100% with you on!
I think the general issue on cooking is similar to shopping, exercise, or "work" for some folks. Some have an interpretation of exercise = fun or pleasure. Some, like me, have a body that treats all exercise as the most dreadful idea ever, and even walking up a hill after years of walking up hills is an excuse for waves of fatigue. Endless little voices scream in misery with every step. You end up in a state of "how do I do this because I need to?" It's either lie down at the bottom of the hill because my body has immediately decided it wants to go to sleep with false exhaustion, or walk up the hill.
Eating can be close. Eat because my body makes complaints, otherwise would not even bother. Not even restaurants. More time, and food is often not very satisfying. The actual food made, whether its fresh, microwaved, ect.. does not matter, because my body has decided it no longer wants to enjoy food. I used to think the variation experimentation part was nice, until my body decided it was a mini game to eliminate that. I almost question the "Food you can make so you don't die."
One thing I've noticed: cooking for myself and my parents feels like less of a chore than cooking only for myself. That's a big part of why, for just myself, I'd rather cook up a big batch and freeze portions for later, aside from recipes not always scaling down well.
Cooking for other people can be something of an event. Cooking for yourself after a busy day for yourself can be a chore you're sort of resigned to so that you can get some necessary calories in your body even if, in general, you like cooking. That's where it's nice to be able to mindlessly pop something in the oven or microwave that dish you've previously made or even just bought.
I agree with all that. I'll eat leftovers. For somethings they're great like a big pot of chili. For some things they're awful. For others, it's somewhere in between and/or some leftovers can be incorporated into a new dish.
Cooking a company meal can be an all-day affair but, especially when I was commuting into an office every day, I had a fairly standard set of recipes that I could whip up in very little time and with very little effort. It really wasn't worth preparing a larger quantity that I would have to reheat for a less good result.
I call this the Reheating Coefficient: how good does something taste when reheated compared to how good it did originally?
Stews can sometimes achieve even >1 RC. I find lasagna is really good as well. And then you have stuff like fries which start out pretty great and lose all appeal the second they hit room temperature, never to recover.
Stews and soups are pretty good in general--although I tend to like reheating stews with big chunks of meat less than something like a chili. I agree on lasagna. I always make one using three bread pans, freeze 2, and eat the third over 2 or 3 days.
I'm annoyed at my local BBQ place. They changed their menu around a couple of months ago and now fries are automatically included as a side which doesn't fit well with bringing the takeout home and eating it in a couple hours.
> And then you have stuff like fries which start out pretty great and lose all appeal the second they hit room temperature
While I agree with the general point, I had to mention that an air fryer can revitalize some things that I used to see as unsalvageable. Fries are surprisingly great after a few minutes at 375.
My personal favorite: chopped leftover fries into roughly equal sized chunks, reheat in the pan until they're back in shape, then use them to make a lazy spanish omelette. Mind you, keep tossing and stirring them to avoid burning and add a small amount of oil if the fries are particularly dry.
Great resource. For stuff in a similar vein, check out the YouSuckAtCooking Youtube channel[1]. Absolutely hilarious, while still being helpful to get better at cooking! :-)
Aglio e Olio - Literally takes 4 ingredients, and (Italians will hate me for this) can be spruced up easily with other stuff available in your pantry, be it chopped up chinese sausages, peppers, olives, shrimp, or leafy greens.
Moroccan Shakshuka - Eggs, Tomatoes, Peppers, Spices - Slowcook and lap up with a nice piece of bread. What's not to like? Again, very easy to spruce up to ensure you don't feel like you're eating the same meal everyday
It's always amusing to see DNS "hackery"[1] like this, and always makes me go back to DNS Toys (https://www.dns.toys/), which generated a huge discussion on HN a year ago [2]
---
[1] well, it's not really hackery if you're being pedantic, since it's doing what the spec allows it to do
Honestly, I think I'd rather travel as much as possible, and gain first-hand experiences of places, things, and people who live and experience life differently than me, than write long winded articles in the New Yorker where I have to namedrop Pessoa and Socrates every two lines because I've outsourced my critical thinking to their writings. Honestly comes across like that angsty teen who just read Ayn Rand once and decides their entire personality is based on the book (Heck, many of us have been that kid!)
There's a hundred reasons why folks dislike travel, many of them EXTREMELY valid to one's lived experiences/circumstances, but this article is the most strawman-ny argument against travel anyone could conjure up.
I know this "blog" is probably hokum, but in my experience, the power of having a good network is incredible. I've been in tech for a decade, and only had a peoper whiteboard interview for my very first role, and have been able to leverage my network to get roles at some dream companies without having to go through the "invert a linkedlist"/"design a parking lot" type of interviews, with great pay raises, role hikes, and increased responsibilities.
Us engineers love complaining about the interview process, but then do NOTHING to display skill outside of a resume (and trust me, the amount of lying that happens in resumes is incredible).
For sports like F1 where there's a lot of $$$ that goes into running the sport itself, it's still understandable, but I always find it funny when you have cricket players (which is huge in India where I'm from) walk out with a dozen logos plastered on them [1], though the sport is much "cheaper" to conduct. But then again, finance bros be making money while the sun shines I guess, and I assume these companies getting their logos in front of a billion eyes is enough RoI for them.
This is EXACTLY how I felt using NestJS. Except, IMO, it took the worst part of Java (Spring DI, esp. the over-verbose, make-changes-in-4-random-files-to-get-an-object style they did it circa early 2010s, instead of the much cleaner styles they have today) and shoved it into a language that is built on a completely different paradigms and constraints.
Not had a single pleasant experience working with NestJS, especially once it hits a certain scale, and you are just bogged down running between modules, services, controllers and DI-hell