• 3 Posts
  • 578 Comments
Joined 1 year ago
cake
Cake day: December 28th, 2023

help-circle

  • I also think tech workers should unionize. On a darker note, I think outsourcing/offshoring post-covid is going to kill any unions viability.

    Quite possibly, but that’s just another part of the onshore/offshore cycle. And having worked for a company that utilized offshore for coverage reasons, I’m not that worried about my position. Offshore techs are decent, but I have to clean up after them more than my onshore coworkers.

    You need bargaining power (withhold your labor) and I’m not sure that will exist for this trade because of how easy it will be to find workers.

    Offshore may work as scabs, but much like scabs, the work quality is noticeably worse. Ultimately, I think tech workers are a bigger hindrance to a tech union than the threat of offshoring is. Mainly because of the house cat like “rugged individualism” they’re sure they have and a lack of overall understanding of the system we work in.


  • But rebuilding your container is pretty trivial from the command line all said and done. I have something like this alias’d in my .bashrc to smooth it along:

    Docker compose pull; docker compose down; docker compose up -d

    I regularly check on my systems and go through my docker dirs and run my alias to update everything fairly simply. Add in periodic schedule image cleanups and it has been humming along for a couple years for the most part (aside from one odd software issues and hardware failures).

    How often are there issues with dependencies? Is that a problem with a lot of software these days?

    I started using docker 3-4 years ago specifically because I kept having issues with dependencies of one app breaking others, but I also tend to run a lot of services per VM. Honestly, the overhead of container management is infinitely preferable to the overhead that comes with managing OS level stuff. But I’m also not a Linux expert, so take that for what you will.









  • Lol, is Netflix any of my customers who thought moving to public cloud services was a good idea?

    I would ask why customers are so dumb about how much public cloud offerings cost, but I know it’s a combination of 1) seemingly low prices up front, 2) bean counters that aren’t able to accurately cost forecast long term, and 3) a fundamental understanding of just how much compute they actually need. It’s absolutely stupid how many customers we have that are having to pull back on services because some genius thought moving to azure was a good financial move only to find out 6-8mo later that they’ve spent this year’s budget already.






  • Configuration by config file is preferred but not mandatory for me, but a docker image is mandatory for me to even try the app anymore. And the ability to backup and restore state is key, preferably in such a way that I can write my backup to a mounted smb share rather than writing locally and copying to the network.

    I’m running everything on commodity or 2nd hand gear, so failures aren’t unheard of. I had one of my micro PCs cook itself this year, and the majority of my services on that box fit that mold (mostly), so I got them back up pretty quick. Though, I did run into issues with container backups not working (because they write the backup like a database, so it has to be a local write for a db lock) and had to start from scratch .