this post was submitted on 07 Mar 2024
596 points (96.9% liked)

linuxmemes

20688 readers
1221 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 0 points 6 months ago (2 children)

Those few employees are probably going to all be developers, and despite there being a bunch of mathematics and engineering involved, being a developer is very much a creative process. Similarly, I wouldn't begrudge a digital artist for wanting to use a Mac to do their work.

If a developer is asking for a thing, they're not asking for it because they've suddenly developed a nervous tic. There's typically a reason behind it. Maybe its because they want to learn that thing to stay relevant, or explore it's feasibility, or maybe it's to support another project.

I used to get the old "we don't support thing because nobody uses thing" a lot. The problem with that thinking is that unless support for whatever thing immaculates out of nowhere it'll just never happen. And that's a tough sell for a developer who needs to stay relevant.

I remember in like 2019 I asked for my company to host git repos on the corporate network, and I got a hard no. Same line, there wasn't a need, nobody uses git. I was astounded. I thought my request was pretty benign and would just sail right through because by that point it was almost an industry standard to use git. I vented about it to some devs in another department and learned that they had a system with local admin attached to the corporate network that somehow IT didn't know about. They were using that to host their repos.

I guess what I'm trying to say is that if keeping employees happy is too expensive, then you gotta at least be aware of the potential costs of unhappy employees.

[โ€“] [email protected] 5 points 6 months ago (1 children)

My last employer had several thousand employees. Some of the IT guys knew Linux, but it wasn't anywhere in the organization. I managed to convince them to let me install Linux on my desktop. They said sure, with the provision that I was not allowed to have a single issue. If I had an issue, they'd format it back. It was a fantastic last 8-9 years at work, as far as computer use went.

[โ€“] [email protected] 2 points 6 months ago* (last edited 6 months ago)

My usual reply to said employees is "if you know how to install and configure a Linux distro, you probably also know how to solve your own problems". Everything else is pretty much deployed over AD, so if you can get to the point where you need admin creds to hook to the DCs, then do whatever you like.

Eventually, all of them failed to even get close to being a part of the AD DC and that is where the story ended.

[โ€“] [email protected] 4 points 6 months ago (1 children)

learned that they had a system with local admin attached to the corporate network that somehow IT didn't know about. They were using that to host their repos.

That's called shadow IT and is a huge security risk.

[โ€“] [email protected] 1 points 6 months ago* (last edited 6 months ago)

We do know about stuff like this... we just decide to turn a blind eye about it since we know who is using it and why they're using it.

But if things get out of hand and we notice weird things happening, then yes, we will act on it and will "know about it".