Live data from Hacker News

When Employees Use Software That IT Hasn’t Approved

hbr.org

241–250 of 326 posts

Re: When Employees Use Software That IT Hasn’t Approved

#241
post #106

Earlier quoted context omitted.

LOL reminds me of a very old bash.org http://www.bash.org/?5273

That reminds me about the story of a University that an old DEC VAX that got walled up during a remodel. Machine kept running and no one notice. A decade later another remodel came along and they tore down the wall to find the machine just happily running.

I remember an old Netware version of that story.

Re: When Employees Use Software That IT Hasn’t Approved

#242

Earlier quoted context omitted.

Try running Visual Studio without admin rights and you will weep. Regarding other rights, I tried to onboard a new Dev without admin rights, however, after the 25th IT ticket (that take days to get done), I gave up.

Visual Studio does not require admin rights to run at all. It stopped needing that almost ten years ago. The only exceptions are some parts of the C++ debugger and the driver development kit.

or anything to do with Service Fabric.

I'm not sure if your "almost ten years ago" is meant to be hyperbolic, or genuine... I can't even remember why, but I know the project I was on 6 years ago definitely needed visual studio to have admin access, and it was all standard C# app stuff (maybe WPF?)

Re: When Employees Use Software That IT Hasn’t Approved

#243

Security training focuses way to much on email phishing and not enough on this kind of stuff. Actually getting your work done, managing your own computer. Of course people can't be trusted if they havem't been trained. How to handle USB drives. What and from where you can download and run programs. What actually IS a program and what isn't. Many of us learned this the hard way by playing lots of cracked games in the…

This assumes that a company has a culture that allows training to happen and affect change, instead of being pushed off, ignored, or laughed at.

And training on different file/executable types isn't effective. Many high profile phishing attacks have been carried out using malicious attacks embedded in innocuous files like word documents or PDFs. The only way to actually prevent malicious code from a download is to prevent the download in the first place.

Re: When Employees Use Software That IT Hasn’t Approved

#244

Earlier quoted context omitted.

And what if two companies standardized methods are incompatible?

You write a new standard to unify the existing two standards

Or you create some sort of middleware to talk between the two.

Re: When Employees Use Software That IT Hasn’t Approved

#245
post #47
post #22

This is exactly extremely common. In my company there is this constant battle about the devs having admin rights on their machines. We need admin rights to do our job. We have had dozens of meetings explaining the situation but IT can’t come up with a solution so the devs go around security because they have no alternative if they want to finish their work . Same with Dropbox. They block it but we have suppliers who…

I think most of the reasons for admin rights are no longer valid. Its easy to change user environment variables and lots of applications can be installed as a user. Why would you need admin rights? Dropbox/googledrive is a huge security hole that is definitely blocked at most companies I work at.

Why do you need admin rights?

IIS development - Visual Studio needs Admin to actively debug IIS.

Memory tools like dotMemory.

Dealing with Windows Services.

Shit... dealing with Windows.

Re: When Employees Use Software That IT Hasn’t Approved

#246

As a born and bread corporate (mostly banks) corporate IT guy, I used to frown upon this behavior. Then I got one of my bigger career breaks because the finance team went behind IT, bought a software and installed it in a machine which kept under their desk. They further hired people from an IT service company to configure the machine. The configuration was so bad that it exposed the company's network to whole wide w…

Really interesting story, especially if you put it in the context of being corporate world and a finance team, both of which aren't the type to rock the boat.

It says a lot about the struggles of enabling change in structures with strong silos that (what are probably among the most risk averse type of) people would go to such lengths.

Re: When Employees Use Software That IT Hasn’t Approved

#247

Earlier quoted context omitted.

You'd probably really appreciate this comedy sketch video: https://www.youtube.com/watch?v=BKorP55Aqvg

Clients don't know what they want and don't know how to describe what they do want. That doesn't mean they're wrong. Actual experts get to the root of what they need, and find ways to solve the requirements, even when they seem impossible. Mandatory response viewing: https://www.youtube.com/watch?v=B7MIJP90biM

That's even more amazing.

Re: When Employees Use Software That IT Hasn’t Approved

#248
I just witnessed a very similar situation, on a smaller scale, but there are many of these in my company, and they add up.

Boss: "We need access to the database of our primary application that you wrote for us so that we can pull the data into this new tool to track progress."

IT: "No. Not only can we not give you access to YOUR data in YOUR application that we wrote on YOUR dime, we will not allow you to have this new application written by someone who isn't in our group. If you wanted something like this, why didn't you just ask us? We would have written this for you."

Boss: "We had a meeting about this over a year and a half ago, and you told me that you didn't even have the time to discuss it further."

IT: "... Well, we're still not going to let you do this."

IT is effectively holding the rest of the company hostage, and the corporate technical debt is becoming epic. So skunkworks solutions will continue to be developed.

Re: When Employees Use Software That IT Hasn’t Approved

#249
In our company people just started using free slack en mass, boycotting the horrible IT approved Skype for business. When it was discovered that thousands of employees were using slack, the CTO had to step in and tell IT to fuck off, and started paying for the full version.

Re: When Employees Use Software That IT Hasn’t Approved

#250

Earlier quoted context omitted.

You'd probably really appreciate this comedy sketch video: https://www.youtube.com/watch?v=BKorP55Aqvg

Clients don't know what they want and don't know how to describe what they do want. That doesn't mean they're wrong. Actual experts get to the root of what they need, and find ways to solve the requirements, even when they seem impossible. Mandatory response viewing: https://www.youtube.com/watch?v=B7MIJP90biM

That’s definitely a clever way to meet all the stated requirements, but in no way does it attempt to get to the root of the real user requirements.

Which, of course, involves talking to actual users.

Post reply on HN