Oh no, you!

  • 65 Posts
  • 2.79K Comments
Joined 1 year ago
cake
Cake day: November 3rd, 2024

help-circle

  • neidu3@sh.itjust.workstoWould You Rather@lemmy.dbzer0.comWyr
    link
    fedilink
    English
    arrow-up
    40
    ·
    edit-2
    2 days ago

    I think you gotta be reeeeally unlucky to be eaten by something within 30 seconds of arriving.

    And the chances for dangerous shore positioning are really slim because the ocean is fucking huge. I’d say chances are that you won’t even be able to see land during all of those 30 second rounds. Source: I work with/on ships


  • neidu3@sh.itjust.workstoWould You Rather@lemmy.dbzer0.comWyr
    link
    fedilink
    English
    arrow-up
    49
    arrow-down
    1
    ·
    edit-2
    1 day ago

    I tend to agree. I usually claim that I can’t swim, as what I do doesn’t really constitute swimming, but I can stay afloat and move in a deliberate direction.

    A complicating factor: Swells and bad weather make it a lot harder. But on the flipside, no matter how badly it goes, if I’m teleported back in 30s I’d just fill my lungs beforehand. I can hold my breath for much longer than that, and even if I couldn’t, it would take more than 30s to die from oxygen deprivation - just make sure I have EMTs on standby for when I return.



  • Me and the IT admin in my previous job had this understanding, as I dealt with field hardware, and he dealt with the “normal” IT stuff.

    Once a merger caused the corporate requirement of only allowing whitelisted apps to run, my laptop was simply disappeared from the requirement list. It made it easier for the both of us. I could be on the other side of the world in sudden need of running some proprietary BS software that had to be whitelisted, and nobody wanted me to have to wake someone up to whitelist stuff.

    When you deal with network hardware that cost more than most PCs, and the server clusters cost more than a house, some leeway should be allowed.







  • A dirty hack that exists now is infinitely better than a properly developed tool that has gone through all stages of approval and quality control at some theoretical point in the future.

    My shitty report.pl script was heavily frowned upon when I put it on the production servers. Not only was it an undocumented script, but there was going to be a “proper” tool for that soon. Well, the proper tool never arrived and now three years later everyone is using my script because we are all too lazy to compile a list of warnings manually.



  • An STL file describes an object/shape. This needs to be translated into actual print instructions such as move to X/Y position, squirt plastic, move again, etc. This is what a slicer does: It “translates” from a shape to actual print instructions. I’m not sure, but I’ve always assumed that it’s called slicing because it takes the 3D object and creates many vertical slices with print instructions.

    I don’t know about your printer specifically, but I guess it takes Gcode (which is what you get as output from a slicer) like most other printers? I suggest you grab PrusaSlicer as it’s very flexible and supports a lot of different printer defaults. Load your STL in there, slice it, transfer the result to your printer, and you should in theory be good to go.

    Tip: Start with something small.



  • neidu3@sh.itjust.workstoComic Strips@lemmy.worldMozilla situation
    link
    fedilink
    English
    arrow-up
    30
    ·
    edit-2
    4 days ago

    Can someone cue (or is it queue? que?) me in on what all the fuzz is this time around? I feel like I hear a pitchfork mob at least once a year without actually noticing anything different.

    Just for the record: I’m not claiming that there’s much ado about nothing, merely that I am severely out of the loop as usual.