This isn’t exactly the most prevalent opinion, but a major part of how these things work is the induced mentality. The main question would be “are you working yourself to death, trying to meet unrealistic expectations set by the dominant societal mindset?”
If, instead, you’re just tinkering and like doing what you’re doing, that’s a different story.
Good job exploiting yourself sucker. No, but seriously keep in mind that your time is limited, especially when you got little kids at home.
While your clients may appreciate any extra work you do for them and it might even get you “loyal” clients, little timmy would also like to spend some time with you.
Totally agree about the kids thing. Being a parent should always take precedence over working(besides working extra to fund the basic needs of the household). Good point :)
It depends… If you’ve got good posture (and I don’t mean sitting up straight, you have to shift around), a good chair, and you get up every hour or two to at least walk around? It’s still probably not healthy, but at least you don’t get too many aches and pains
On the other hand, it’s a lot harder with gaming. You’ve got your hands on the keyboard or clutching the controller constantly, you (or at least I) will tense up and put strength in my wrist at a weak angle, sometimes I’ll find myself leaning forward and tensing up
I feel it if I’m on a gaming kick, but day in and day out it’s usually not too bad. It helps that I need to walk to refocus anyways, so even gaming I usually take a lot of breaks
I don’t use NPM but if “Cache Assets” means what it means in the traditional sense, it wouldn’t affect most home deployments.
Historically, resources are limited and getting Apache to load images/javascript/CSS files from disk each time they’re requested, even if the OS kernel eventually caches them to RAM, was a resources intensive process. Reverse proxies stepped up and identifies assets (images, JS and CSS), and stores them in memory for subsequent requests. This reduces the load on the Apache web server and reduces the hops required to serve the request. Thereby making everything faster.
For homelabs, and single user systems, this is essentially irrelevant, as you’re not going to be putting so much load on the back end system to notice the difference. May be good to still turn it on, but if you’re noticing odd behaviors (ie updates to CSS or images not taking), it may be a good idea to turn it off to see if that’s the culprit.
Me too! I wound up switching over to a pitcher with a built in metal mesh filter though. If I ever need to make a double batch or something though, I’ve still got it.
The intern who did it didn’t know better and it’s cheaper to spend hundred of thousands on Microsoft rather than project past the next few years since whoever is in charge will be gone by then.
Welcome to the work world, where inefficiency is only problematic when it shows up on an Excel sheet.
slrpnk.net
Top