• 3 Posts
  • 162 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • Full disclosure: Haven’t read the article yet.

    Working in corporate IT, this most likely is targeted toward enterprise customers who either take a long time to roll out OS upgrades or can’t due to technical limitations within their environment. In those cases, paying the cost of extended support is more palatable to troubleshooting or rushing mass OS upgrades. This is a fairly common practice with enterprise software vendors.

    Edit: Okay, just skimmed it. Looks like this is actually a new program for non-enterprise consumers, which is interesting. First I’ve heard of that.






  • I’m going to say that while everything I’ve read on the matter supports the “it’s one of the more pleasant ways to go” argument, I’d be more interested in reading expert opinions on the matter before coming to a concrete conclusion.

    The lawyers on both sides of the case should be consulting with doctors and medical researchers to understand what the experience would consist of, how long it would take, the efficacy, side effects if it fails, etc. This is the information that I think should be the deciding factor for proceeding or not.

    I will also say that while oxygen deprivation is quick, it’s not instant. It does take up to a few minutes in some cases before brain death to occur, and something to the order of 30 seconds to a minute for unconsciousness to set in.

    My personal opinion based on the information so far, assuming that everything I’ve read is factual, would suggest that of all the execution routes available so far, this one is likely the least awful. I won’t say most humane, as I don’t really believe there is a humane way to approach it. If we do have to use the death penalty though, I think this is the approach I would have the fewest objections to.



  • Apologies in advance for the novel!

    I’m a little late to the party here, but here is my story. Nothing too glamorous, and admittedly I’m still very much an amateur.

    In high school, I wanted to be in band. Always loved music, loved listening to it and wanted to make it. Unfortunately I came from a pretty poor household and we couldn’t afford an instrument.

    Five years ago (wow, it’s already been five years?!) I decided “hey I’m making decent money now, maybe it’s time to learn to play something.” So I went to my local music store knowing NOTHING about how to actually play an instrument. But I decided to walk around and see if something called out to me.

    I walk by the keyboards section, which is having a pretty slow day, and one of the guys there is just rocking out on this Korg Minilogue. It sounded phenomenal, and I just knew the synthesizer was for me. Admittedly up until that point, if you happened to ask me what a synthesizer was, I would have just said something like “it’s a fancy electric piano.” Yeah…real informed decision there. But I left with a lighter wallet and a brand new synthesizer.

    Well, having a synthesizer is nice, but it’s not conducive to making a full song, especially if you know little about making music, but at this point I am just devouring all of the synth YouTube content I can find, and stumble onto the wonderful world of grooveboxes.

    “Wow, I can make full songs on a little box that I can just take with me? Sign me up!” Now, in case you don’t know, my background is in tech. As such this scratched two itches for me, which are my love of music and my equally strong love of gadgets and gizmos. I may or may not occasionally be referred to as the little mermaid by my friends.

    So I went down that rabbit hole. Mind you, at this point I still BARELY know anything about actually making music, and do I really have to learn about chords and scales? Where’s the fun in that. So I took the “more dollars than sense” approach and tried to supplement my lack of skill with more gear. Spoiler alert: it didn’t work.

    Eventually I decided “I’ve got way too much gear and nothing to really show for it, and that needs to change.” I went through all my gear and decided “this fills a practical use case, and this does not,” and sold anything in the latter category. It was a huge relief.

    Around that time I also ended up signing up for a couple online courses on music production, like Andrew Huang’s on that site that used to be called Monthly. It wasn’t bad…helped me get a better idea of how to think about music production overall, and I finally forced myself to put out my first track. It wasn’t particularly good, and I’ve only officially released one song since then, but I’m still slightly proud of it.

    Since then I’ve only ever officially released one other track and have worked on others off and on. I have no visions of making a career out of it, but I enjoy having fun and just noodling something out. Maybe I’ll release more, maybe not, but at the end of the day I’m at a point where I enjoy what I’m doing with it all.

    In regard to what made it all click for me - I naturally fell into the technical aspects of it (like how MIDI works, how to use a mixer, etc), due to the fact that I troubleshoot tech for a living and that felt like an extension. As for the more musical parts, I think what really did it for me was learning that musical inspiration is exactly that - inspiration. It doesn’t have to follow a specific formula. You can start from complete randomness, and if you like it, great. If you don’t, you can always build up from there or start again.









  • Yeah, I’m kind of torn on this one. On one hand, having a drive replaced for an issue, then having that replacement fail with the same issue (or at least same effect) reeks of problems. That probably warrants merit.

    On the other hand, it does show they likely have poor data backup practices if losing a single hard drive is costing them 3TB data loss. Either they were recording a day’s worth of video and lost it, in which case that sucks but it happens, or they had a ton of other data that likely should have already been backed up elsewhere in which case I have little sympathy.




  • Hmm…this should work but I do have a concern on it based on my experience with AWS. Maybe this is different with minio though.

    In AWS, S3 bucket names are globally unique. Not just to your AWS account, but across ALL S3 buckets period. So let’s say you have a username of “test” and use that policy. If that user attempts to create a bucket and that bucket name is taken, well that user is out of luck.

    Obviously if minio doesn’t require globally unique bucket names you’re probably fine, but otherwise this could realistically become a problem.