As someone who has worked in the tech industry near Seattle, I don’t know how well known it is to the wider populace or people in Europe, but open source is absolutely anathema here. It’s seen as insecure, unstable, and unreliable.
I work in IT so I’ve tangentially worked across a number of sectors supporting their stacks and it’s pervasive within the American culture. There is a major de-prioritization of in-house IT knowledge and sysadmins in favor of enterprise support contracts. When shit hits the fan, it’s less important to have a knowledgeable team and more important to have a foot to stamp down on until the issue is resolved. Often that foot has another foot that stamps down, onward and onward until someone manages to engage the MSP or cloud provider that set the service up initially with their scant documentation.
It’s a nightmare both for tech workers and from a cyber security perspective. A lot of this contains my own personal bias and perspective on the matters, but let me say, I have stared into the void and I can’t stop screaming.
as someone getting into the it field. My current employer could make more of their IT department in house but they don’t want the responsibility of that that want someone ELSE to take the blame when something fails.
I definitely learned that working with a law firm once. I could have set them up something more secure with an open source stack but what they really wanted was a company to blame if things weren’t as secure as I promised.
I imagine that’s why a lot of governments and big companies pick a big corporate vendor when it’d be cheaper and better to hire people. There’s less liability if you can blame a vendor than a specialist in the event something goes haywire.
As someone who has worked in the tech industry near Seattle, I don’t know how well known it is to the wider populace or people in Europe, but open source is absolutely anathema here. It’s seen as insecure, unstable, and unreliable.
I work in IT so I’ve tangentially worked across a number of sectors supporting their stacks and it’s pervasive within the American culture. There is a major de-prioritization of in-house IT knowledge and sysadmins in favor of enterprise support contracts. When shit hits the fan, it’s less important to have a knowledgeable team and more important to have a foot to stamp down on until the issue is resolved. Often that foot has another foot that stamps down, onward and onward until someone manages to engage the MSP or cloud provider that set the service up initially with their scant documentation.
It’s a nightmare both for tech workers and from a cyber security perspective. A lot of this contains my own personal bias and perspective on the matters, but let me say, I have stared into the void and I can’t stop screaming.
as someone getting into the it field. My current employer could make more of their IT department in house but they don’t want the responsibility of that that want someone ELSE to take the blame when something fails.
I definitely learned that working with a law firm once. I could have set them up something more secure with an open source stack but what they really wanted was a company to blame if things weren’t as secure as I promised.
I imagine that’s why a lot of governments and big companies pick a big corporate vendor when it’d be cheaper and better to hire people. There’s less liability if you can blame a vendor than a specialist in the event something goes haywire.