I took it as software engineers tend to build for scalability. And yep, IT often isn’t prepared for that or sees it as wasted resources.
Which isn’t a bad thing. IT isnt seeing the demands the manager/customer wants.
I’m glad you’ve done both because yeah, it’s a seesaw.
If IT provisions just enough hardware, we’ll hit bottlenecks and crashes when there’s a surprise influx of customers. If software teams don’t build for scale, same scenario, but worse.
From the engineer perspective, it’s always better to scale with physical hardware. Where IT is screaming, “We dont have the funds!”
Meh it’s usually for shitty companies that expect their devs to write real software, ssh into things, access databases, but put the same hurdles in front of them as joeblow from sales who can’t use an ipad to buy a sandwich without clicking a phishing link. So every new project is slowed down cause it takes weeks of emails and teams conversations to get a damn db sandbox and it’s annoying.
On the other hand IT doesn’t know you and has millions of issues to attend to
IT guy here. If we give one user special rights, that login will get passed around like a blunt at a festival to “save time”.
Users are dumb and lazy, and that includes devs.
Funny, that has actually been my entire experience with corporate IT. This field attracts the type of firemen that won’t climb down the pole because it’s a safety hazard. Y’all are… something special.
See I think this is where in general people in it misunderstand the impact.
Like, if it’s -40 and your furnace breaks, who is having the worse day, you or the furnace repair man?
The repair man might be grumbling because they have to do their job, but you’re grumbling because you’re freezing. You both might be grumbling, but by way of impact there is a massive asymmetry in impact.
That repair man is going around to many peoples freezing houses. They are also freezing their butts off all day. And not just one period in winter, every single day of winter.
And when they fix a house, they don’t get to enjoy the warmth afterwards. They have to go to the next freezing house.
I don’t get it. And I’ve been both.
Is it about how some software shouldn’t need the resources that they demand for?
I took it as software engineers tend to build for scalability. And yep, IT often isn’t prepared for that or sees it as wasted resources.
Which isn’t a bad thing. IT isnt seeing the demands the manager/customer wants.
I’m glad you’ve done both because yeah, it’s a seesaw.
If IT provisions just enough hardware, we’ll hit bottlenecks and crashes when there’s a surprise influx of customers. If software teams don’t build for scale, same scenario, but worse.
From the engineer perspective, it’s always better to scale with physical hardware. Where IT is screaming, “We dont have the funds!”
Meh it’s usually for shitty companies that expect their devs to write real software, ssh into things, access databases, but put the same hurdles in front of them as joeblow from sales who can’t use an ipad to buy a sandwich without clicking a phishing link. So every new project is slowed down cause it takes weeks of emails and teams conversations to get a damn db sandbox and it’s annoying.
On the other hand IT doesn’t know you and has millions of issues to attend to
IT guy here. If we give one user special rights, that login will get passed around like a blunt at a festival to “save time”.
Users are dumb and lazy, and that includes devs.
Funny, that has actually been my entire experience with corporate IT. This field attracts the type of firemen that won’t climb down the pole because it’s a safety hazard. Y’all are… something special.
It’s not special rights, it’s project materials approved by leadership, and noted on a published and approved feature roadmap
Edit assuming requisitioning a scaled db replica is “special” is kinda aligned with the meme lol
I’d say… elitism
More likely tribalism.
Por que no los dos?
Because you can’t have elitism in the group that knows so little about fixing something that one of their actual plans of action is to reboot and pray
This is exactly my face when IT is telling me the rules for my passwords.
Sorry, those rules come from our cybersecurity insurance, or some compliance rules.
We hate them as much as you do.
Then why are they different between systems? Do you have different insurers per application?
Those other applications come from an external vendor, we only provide the VM to run them.
We hate those even more than you do.
You can’t
Every single issue that occurs with those applications gets thrown in our laps to fix.
This includes all of yours as well as all your colleagues.
See I think this is where in general people in it misunderstand the impact.
Like, if it’s -40 and your furnace breaks, who is having the worse day, you or the furnace repair man?
The repair man might be grumbling because they have to do their job, but you’re grumbling because you’re freezing. You both might be grumbling, but by way of impact there is a massive asymmetry in impact.
But that is only looking from one perspective.
That repair man is going around to many peoples freezing houses. They are also freezing their butts off all day. And not just one period in winter, every single day of winter.
And when they fix a house, they don’t get to enjoy the warmth afterwards. They have to go to the next freezing house.
Understand that impact.
What applications do you have that IT controls the password requirements for?
IT controls your AD credential requirements in most cases and that’s pretty much it. It sounds like your employer needs to implement an SSO solution.
It is the AD credentials. It’s a fortune 500 company and it doesn’t even come close to NIST recommendations.
We have like 3 different ADs as a result of mergers and acquisitions, and the requirements are all different.