• 0 Posts
  • 108 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle

  • It’s important to identify the tasks you and your spouse do, and how you feel about them. Sharing the loaf works better if there are things your spouse does that you personally despise doing.

    For example, I do all the shopping, cooking, working, and clean the kitchen. It’s a heavy load, but those are all things I don’t mind doing so it’s tolerable. My wife handles laundry, cleaning most of the rest of the home, meal planning, and does a higher proportion of the direct child care. She doesn’t mind those things nearly as much as she hates the tasks I do.

    As one of us burns out from one task or other, we frequently check in and adjust. Sometimes I just can’t deal with the kitchen anymore and we order in takeout for a couple days. Sometimes she’s overwhelmed by chores and we tag team getting the obvious tasks done while the kid is napping.

    For technology, AnyList has been a killer app. Being able to collaborate on meal planning and building shopping lists is amazingly useful.

    I think the broader problem with mental labour is that men have typically been blind to many of the general maintenance tasks that women have silently done for generations, and this unspoken arrangement creates resentment. As long as you keep that in mind, it’s pretty easy to have conversations about it. Like other posters have said - make a list! Once you’ve written down all the things that have to happen to keep a household running, you can delegate them accordingly or at least make it highly visible as to who does what. It’s not necessarily wrong to have an imbalance, provided you’re both aware and honest about it.


  • I have not. I’ve seen crypto be highjacked by scammers and grifters who spew a lot of pseudo-technical nonsense and try to hype their business that doesn’t exist. I’ve seen coins come and go after they’ve been successfully pumped and dumped.

    But I’ve never seen crypto solve a real problem.

    The idea behind a blockchain is great and the list of pros is long. But… still haven’t seen it implemented to do anything useful.

    I would like crypto to solve a problem.

    Like your suggestion - could crypto help solve famine? How, exactly? Crypto isn’t something you sprinkle on a problem to fix it. It’s a very fixed set of technical specifications. So how can that be used to solve famine? Is famine caused by the lack of a publicly accessible ledger that requires proof of work? Or is famine caused by inadequate logistics and local politics? How does crypto help us get freighters of grain from Ukraine to Sudan? How does it offload that grain and see that it’s transferred onto rail and trucks to reach people in need? How will it ensure warlords and corrupt officials don’t redirect that aid to their own interests?




  • Nursing is a little different from most kinds of work environments, but not that different.

    I think there’s 2 halves to unpack here. One is her ability and the other is her attitude. If someone is getting along in their career and has trouble hustling around on their feet for 8 or 12 hours, I get it. They can move slower or take longer sitting breaks when there’s no patient in dire need. That’s why people work on teams.

    But then there’s the attitude part. Are other nurses dealing with her patients on the regular? Is she ignoring call bells? Is she never making any effort to help a fellow nurse when they’re swamped? Then we have a problem.

    Like you said, you’re new and it’s not the time to go in guns blazing. Your reputation doesn’t mean shit for a while now, but I don’t think that means you should just suck it up and do your job in spite of it.

    I would mention it casually to your manager. Not as a complaint (see: your reputation doesn’t mean shit), but as a casual concern. “I didn’t want to say anything to X, but I’ve been noticing since I started that she seems to really struggle to deal with her patient load.” Whether you try to frame that along with “how can I help?” or something else is up to you.

    The main thing you want to take away is:

    • your manager has been informed by you that you’ve seen a problem with this nurse
    • you documented the conversation if it was in person
    • you’re keeping notes on your coworker when something unacceptable happens.

    These sorts of dramas play out slowly. The best thing you can do is collect information you can refer back to later in case things take a twist.

    I can’t tell you how many times in my life an employee has become “a problem” in management’s eyes, but we’re starting at 0 because nobody ever complained or documented any of the issues that were going on for YEARS.











  • I think this is just a picky optimization.

    The first one runs the constructor to instantiate a new string, then gets its class (which is presumably a static property anyway). The second doesn’t have to run any constructor and just grabs the static class name from the type.

    Maybe there’s more implementation nuance here but it seems like an opinionated rule that has zero effect on performance unless that code is being called thousands of times every second. And even then the compiler probably optimizes them to the same code anyway.




  • This happened to me once and I completely overthought it.

    In my case, I removed the PCB from the drive and took a close look and saw a single scorched IC that I figured was the problem. I think it was a voltage regulator or something like that.

    So I bought a scrap drive and tried to transplant the PCB onto my dead drive, but of course that wouldn’t be able to read my old data.

    So took it into a local electronics repair shop and asked if he’d be able to make it work.

    He took one look at the damaged PCB, pushed the scrap one back at me and said “yeah I’ll just replace this part.”

    40 bucks later I had a working drive again and was able to rescue the data.


  • The short answer is no.

    You can do an easy experiment to see this using image files. Grab a random JPG file and open it in a graphics program and save it as a BMP format image.

    JPG is already compressed, and BMP is absolutely not compressed. Then try compressing each image. You’ll find that the JPG doesn’t get much smaller, or might even be a bit bigger when compressed. Now do the same with the BMP - that one makes for a smaller RAR!

    The main issue here is that compression is about removing empty space in a file (it’s a weak analogy but bear with me). If the file itself already had some kind of compression (basically every AVI or MP4 or MKV you download probably is already compressed), then there’s already a lot less empty space inside the file. RAR doesn’t have much empty space left to work with, so it can’t really reduce the file size any more.

    It’s worth doing some testing on a single movie to see how this all works. You’ll probably find that it’s best to just leave the files exactly the way they are. No RAR. No ISO. No tricks. The gains simply aren’t there.

    If you’re looking to save on some disk space with your movies, you’d get a lot farther by just deleting one movie you don’t really want that badly. The amount of space you get back from that will exceed your compression gains. It also means you don’t have to go and uncompressed the movies every time you want to watch one.