Why not just stick to what we’ve always been doing?

1. wget something.tar.gz
2. tar something.tar.gz
3. man tar
4. tar xzf something.tar.gz
5. cd something
6. ls -al
7. ./config.sh
8. chmod +x config.sh
9. ./config.sh
10. make config
11. Try to figure out where to get some obscure dependency, with the right version number. Discover that the last depency was hosted on the dev’s website that the dev self-hosted when it went belly up 5 years ago. Finally find the lib on some weird site with a TLD you could have sworn wasn’t even in latin characters.
12. make config
13. make
14. Go for coffee
15. make install
16. SU root
17. make install

there was a tendency for MUCH worse surprises to be included.

Yeah, like strange unreleased Weird Al tracks with sex and drugs references… Every spoof was labeled weird Al back in 2000

deleted by creator

Listen to Baz Lurhman’s “everyone’s free to wear sunscreen”. And I mean listen to it. Every single line is true.

But of course, how else could you describe yourself as having experience with TeX? /s

I think our TeX savvy lemming here confuses a knowledge level in the expert/consultant sphere with “having experience”.

Having worked with LaTeX on and off for 15 years, and on occasions developing TeX macros (ie copy pasting stuff from stackoverflow and shotgun debugging it until it sorta works) and creating various graphics with PGF/TikZ, I would describe myself as having extended experience with the TeX environment. But I still can’t tell you exactly what causes \hbox underfull without looking it up… Probably because it’s never caused a failure to output my documents.

Ok, go on then, tell the class what underfull hbox is. And no googling!

That’s with the mindset that I wouldn’t want to stay long at a job like that

Oh I concur, but elsewhere OP mentioned that the job pays a rather unskilled (OP mentioned having an A+) 20 year old 55k USD, and OP is getting certs as well. In that case I’d seriously be working on my STFU-skills, instead of meddling in something that my boss really wants me to stop meddling in. Maybe do a bit of CMA - but not to the extent of emailing my boss to get a paper trail.

When you’ve been in an organization for only three months, and it’s your first job in the industry, maybe just absorb what’s happening instead of trying to change stuff. Make up your own opinions, sure, but keep them to yourself. Maybe evaluate on how you perceived situations, and how they played out, and modify your views based on that.

It’s your first IT job and you’ve been there for a few months? While your safety concerns definitely can be relevant my advice is this

You should

1. Don’t rock the boat as a new hire. Figure out what is going on first. Maybe there’s a reason to some of the madness you see.
2. Do NOT contact the owners. Doing so will likely be seen as disloyalty by your boss and possibly the owners as well. Only go through your immediate superior.
3. Don’t bring it up again with your boss. It’s not your responsibility.
4. Leverage the user. Let the user be the one to push for a system switch.

You could

1. Figure out if you can get the system on a separate VLAN and get it locked down in firewall rules.
2. Research the system. Why don’t your boss want it replaced? Does it run some ancient software? We’ve got some machinery that is running windows 7 at work. When I got hired, in the days if windows 8, the controller was running windows XP. The setting up of drivers and archaic proprietary software, involved in upgrading, is immense. When we switched to 7 this €60k equipment was down for days, and it was a week before it operated properly.

Original Finnish management has split off to a new independent company with the same name last year

Best business move EVER! Now people have to wonder with whom they’re doing business. Sorta keeps people on their toes. Way better than coming up with a new brand, making it easier for their five customers. /s

I was wondering what a washing machine needed a TPM for. Better title: “machine fails to boot after power failure”