5 ms·
I believe this is assuming companies have segmented networks and jump hosts. In my experience, most... don't. Enterprise IT at non-tech companies is an absolu
by ethbr0 6y ago
I believe this is assuming companies have segmented networks and jump hosts.
In my experience, most... don't.
Enterprise IT at non-tech companies is an absolute #&@_ show. The only rationale I've been able to come with is: if some portion of your company isn't developing / keeping up with tech trends, your IT shop isn't going to be pressured to either.
- sbarre 6y agoMost non-tech companies don't have an IT department, they outsource. Which means they rely on those companies to do the right thing, while not really prioritizing the work (i.e. not giving it much budget), or being able to critically evaluate the quality of the work being done. So none of this is surprising.
- Godel_unicode 6y agoIt's also the case that the perception of non-technical companies having garbage IT means they get overlooked by more savy admins in their job-hunt. Very few people want to drag a manufacturer kicking and screaming into modern IT, when it's way easier to get a job with a company that gets it. This year is going to be huge for Google cloud and m365.
- Kalium 6y agoIt's also been my experience that non-technical companies sometimes strongly undervalue IT or programming expertise. Few who have a choice ways to take a job at a rate well under market using outdated technologies with an employer who will not value them. I had one of those jobs for a while. It was awful. The worst part was the ridiculous demands (example: all bugs should be fixable in 30 minutes or less) on top of the embarrassingly low pay.
- buran77 6y ago> non-technical companies sometimes strongly undervalue IT or programming expertise Half of this is actually the right way to do it. On one hand undervaluing IT in almost any company these days is a major problem waiting to blow up. IT isn't just an end, it's the means to do everything else. Using computers but ignoring any good IT practice under the excuse that it's not an IT company is like working from an office with asbestos, lead paint, and black mold because you're not a construction company. But on the other hand non-technical companies, meaning ones without a strong IT culture and focus, should undervalue programming expertise. One of the worst things a non-tech company should do is deploy all kinds of custom IT solutions developed internally by their "programmers with expertise". Invariably (and I mean this in the most literal sense possible) they will end up with a patchwork of systems that nobody understands or maintains properly but which underpins all the core services the company needs or delivers.
- Kalium 6y agoI think your first scenario is a good illustration of undervaluing IT, with attendant eventual disaster. Perhaps your second is IT being overvalued? You've described a situation where technologies are being deployed inappropriately by an organization ill-equipped to handle the ongoing effort required. This is the sort of silver bullet thinking I would expect from leadership that does not understand IT beyond that it is powerful.
- buran77 6y ago> You've described a situation where technologies are being deployed inappropriately by an organization ill-equipped to handle the ongoing effort required. I took the archetypal "non-technical companies" you gave as an example earlier. If I understood your meaning correctly in the vast majority of those cases undervaluing "programming expertise" is probably the best thing to do. And by "undervaluing" I mean they such companies should not consider this as a skill they should rely on to build their IT around. It's not that the skill is not useful in itself, just that it doesn't serve that type of company well, and valuing it suggests the companies are considering heading in waters that they're unlikely to successfully navigate. Most of those companies will do things inappropriately because they are ill-equipped to handle this. For all intents and purposes "programming expertise" in such a company is like driving drunk. Sure you can get home safe anyway but that's not a reason to be proud of. Or you can crash but the real issue isn't that you couldn't cut it while driving drunk. You shouldn't be doing it to begin with.
- ethbr0 6y agoI think there are two different kinds of IT value. The first: I am a competent employee, who can do what needs to be done (in whatever technology). The second: I am a forward-thinking planner, who surveys and keeps abreast of options and can identify, test, and deploy appropriate ones. In my experience, it's the second that's lacking. Aka the "we can only deploy if Microsoft holds our hands through it" shops. Usually 1/2 because of lacking talent and 1/2 because of lacking / incorrect policies. I've seen, but haven't seen too many, instances of "insert crazy state-of-the-art technology." Usually it's just institutional paralysis that prevents anything from getting done.
- HappyDreamer 6y ago> non-technical companies sometimes strongly undervalue IT or programming expertise They might also be unable to know if a job applicant is good at IT or not? And listen mostly to how he/she describes him/herself, and how confident he/she sounds? Meaning, the company in effect hires IT people a bit randomly, and then mostly finds people who aren't that good at their job. And if the company started paying more, then, more competent people, but also lots of more so-so competent people, would apply for the job? And I wonder if the company then still ends up with a random mediocre IT people who are unable to really secure the network? Just that the salaries are higher? I wonder if the underlying problem is that 99% of the population is unable to know if someone is good at software or not
- bobbob1921 6y agoGreat point. + most of mgmt doesn’t see the real value in security until after the first (major) incident has occurred. (Has been my experience atleaste for < 50 employee orgs.)
- dredmorbius 6y agoThis goes back well over a decade, but a talented Linux admin at a tech shop had to spin up a fresh Windows VM instance to use some MSIE-dependedent intranet app. By the time they'd completed the task ten minutes later, the instance had been pwned, on the office LAN. It's a sh*tshow everywhere.
- jlg23 6y ago+1. Even when being told (for money!) to do the right thing most pay the consultant fee but don't act. True story: A friend was pentesting a large company network in Germany, wrote his report and got paid. Years later, when being hired as head of IT security, he pulled out his old report and simply tried the default/easily crackable passwords he had discovered in the core infrastructure: They all still worked. If his section about "use jump hosts" was ever useful for the company, it was because someone had that page open by accident, needed a place to put down his mug of coffee - et voila: His report even made a difference!
- deleted 6y ago[deleted]