▪█─────█▪

  • 0 Posts
  • 28 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle
  • This is why I got all of our devs to start building with the target of a Docker container in mind.

    And for the ones who still won’t or can’t wrap their brains around Docker, I run their shit through a Github Actions workflow that spits out their ugly baby as a Docker container. In the end, I don’t give a shit what it is, your Rube-Goldberg piece of shit is getting stuffed into a Docker container.

    “It works on my machine!” Yeah, well, your machine is now everyone’s machine thanks to the magic of containers. Now fix your broken shit so PagerDuty doesn’t call me at 3am again. Fuck.





  • I hate Node and NPM so much that I have a physical reaction to just seeing the words now.

    I already disliked Node & NPM quite a bit, but the hatred and disgust got to the point it is now after having to write a CI/CD pipeline in Groovy/Jenkins for a Node site that that our devs were building. I had to automate the build/deployment of Satan’s favorite framework in Satan’s favorite language. I came pretty close to quitting.

    It’s out the door now, but I’m in the middle of reimplementing the pipeline in Github Actions so I don’t drink myself to death when they come knocking to do it again.










  • tool@r.rosettast0ned.comtoProgrammer Humor@lemmy.mlTrue
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Aside from the callback chains and API shit, my issues with Node rest almost entirely on the lack of a standard library, because that led to the state of NPM today, which is just an absolute garbage-fire shitshow as far as I’m concerned.

    I have my own separate issues with NPM, namely its dependency resolution (my God, just take dnf's dependency resolution algorithm and use it), trivial packages that other packages list as a dependency (is this an int? Is this running on Windows? Better take this one line and make it a package!), and the relative inability to remove a package from a registry (did a secret slip in there while testing? Tough shit!). The worst of that being the trivial packages, I think, because then you can end up with projects that can have a dependency tree 10s of thousands packages long.

    And all that bullshit wouldn’t be even 1/16th of the problem it is today if there were a standard library.

    You should take what I’m saying with a grain of salt, though, I’m just a DevOps Sysadmin, and aside from running some software that uses Node, most of my experience with it is unfucking it when our devs come to me to fix the tangled monster they’ve created.



  • At that point you may as well go full Vagrant or start using Docker images.

    And no matter how quirky or obtuse venv/conda/pip can be, they will never be as bad as Node. Ever. Node will hold that King Shit crown forever, or at least to God I hope it does.

    Something worse than Node coming around and getting popular might just make me quit IT altogether.



  • tool@r.rosettast0ned.comtoProgrammer Humor@lemmy.mlask
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    1 year ago

    A few jobs ago, we had a fleet (2K+) of mobile inkjet and Zebra printers that we were responsible for for some ungodly reason.

    The Big Blue Sledgehammer from Lowe’s was the official method of decommissioning them per the IT disposal policy. That I wrote.

    That’s the only thing I miss about that job.