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

help-circle


  • So is the issue that your extra drive mounts to /storage, but that happens after Docker has already started and taken over the directory, so the mount fails? Normally I’d expect it to happen in the other order. Is this a weird race condition?

    This might be a good thing to run through with ChatGPT- there are probably ways to delay the Docker container start, but maybe there’s a more significant misconfiguration you can deal with.






  • Read the email again. The key word in their marketing slop is “alternatively”. You have a Plex Pass and are the server admin. Your users need to do nothing.

    Unfortunately, that does mean I have to respond to messages from all my users asking what that email means and convince them they can just ignore it.

    A second “nice” part of this change is that iOS users no longer have to buy the Plex app on the App Store to stream longer than a minute. The app is only like 5 bucks one time, but it was a barrier when trying to convince stubborn people to just fucking TRY my Plex server.


  • I feel sick saying it, but I think this is a project you could complete with AI. It sucks ass at understanding complex problems, but it’s good at cranking out small scripts to integrate tools together.

    You basically just want a wrapper around ffmpeg with a light web interface to handle upload, script execution, and download.

    LLMs are pretty good at spitting out a simple web interface that runs in a barebones server like Express or nginx.

    If you don’t need to worry about security or accessibility or any “not on the critical path” concerns, this could probably work after a few iterations.

    As for anything already out there - I’ve never come across anything. The closest app I can think of is TDARR which is intended to automatically transcode your media library to h265. That wraps up some of the ffmpeg stuff you want, but doesn’t address the upload/download half of the workflow.




  • 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.




  • A full stack developer is either a back end developer that has no business writing front end code but does it anyway, or they’re a front end developer that has no business writing back end code but does it anyway.

    Or they’re perfectly capable of doing both because they’re at a startup that’s years away from running at scale or having to worry about performance and security.


  • It’s a little worrisome, actually. Professionally written software still needs a human to verify things are correct, consistent, and safe, but the tasks we used to foist off on more junior developers are being increasingly done by AI.

    Part of that is fine - offloading minor documentation updates and “trivial” tasks to AI is easy to do and review while remaining productive. But it comes at the expense of the next generation of junior developers being deprived of tasks that are valuable for them to gain experience to work towards a more senior level.

    If companies lean too hard into that, we’re going to have serious problems when this generation of developers starts retiring and the next generation is understaffed, underpopulated, and probably underpaid.