Generally they’re users with just enough information to be dangerous.
They know some things, but don’t have a knowledge deep enough to know that there are serious downsides to (insert whatever they care about this week here).
I’m pretty sure I’d be more neckbeard nerd than techbro.
Yup. Most of the time, policies are in place because someone tried what you’re trying and it let them do that thing… And because Windows let that thing happen, something bad happened for everyone.
So now nobody can do that thing.
The prosumer tech bro that’s never touched enterprise equipment or dealt with operational requirements are the worst.
I couldn’t tell you how many times I’ve heard that something works fine at their home but doesn’t work while they’re at work. Sometimes that’s intentional, sometimes that’s because the network in the office is about 80,000x more complex than the Linksys you plugged in at home, set a password on once that you immediately forgot, and has been doing little more than source Nat and L2 bridging every since, with no regard to what the traffic is, just sending it out regardless, and creating a goddamned mess in the process, but because it’s only you and your spouse and maybe a kid or two, that doesn’t really matter.
Suddenly when you’re dealing with hundreds of endpoints on a LAN, you don’t want every broadcast packet being sent out over the dozens of access points you have dotted around, so no, your multicast discovery won’t work Brenda. So you can’t use Chromecast in the office, okay? I don’t care how important you think it is, it would take hours to get this to work properly and I have more pressing concerns at the moment.
But this kind of sounds exactly like the rationale these tech bros use to claim they know more than everyone and “these plebs just don’t understand”
Tech Bros drive me up the wall.
Generally they’re users with just enough information to be dangerous.
They know some things, but don’t have a knowledge deep enough to know that there are serious downsides to (insert whatever they care about this week here).
I’m pretty sure I’d be more neckbeard nerd than techbro.
“Hey Windows won’t let me…”
No, it’s actually me who doesn’t let anyone on the network do that. For a reason.
Yup. Most of the time, policies are in place because someone tried what you’re trying and it let them do that thing… And because Windows let that thing happen, something bad happened for everyone.
So now nobody can do that thing.
The prosumer tech bro that’s never touched enterprise equipment or dealt with operational requirements are the worst.
I couldn’t tell you how many times I’ve heard that something works fine at their home but doesn’t work while they’re at work. Sometimes that’s intentional, sometimes that’s because the network in the office is about 80,000x more complex than the Linksys you plugged in at home, set a password on once that you immediately forgot, and has been doing little more than source Nat and L2 bridging every since, with no regard to what the traffic is, just sending it out regardless, and creating a goddamned mess in the process, but because it’s only you and your spouse and maybe a kid or two, that doesn’t really matter.
Suddenly when you’re dealing with hundreds of endpoints on a LAN, you don’t want every broadcast packet being sent out over the dozens of access points you have dotted around, so no, your multicast discovery won’t work Brenda. So you can’t use Chromecast in the office, okay? I don’t care how important you think it is, it would take hours to get this to work properly and I have more pressing concerns at the moment.