[jgamman]

perhaps "IT dept" still conflates infrastructure with application. if you are entirely cloud with a SLA for support, then "application" just means allowing depts to develop the tech they need to solve problems -> as the articles says 'any picture you like, but only using this canvas/paint/brush stack'. i've got a lot of sympathy for this view.

[dijit]

But. You still have support contracts, billing, SSO, commitment to resources based on usage and organisation management.

Do you really want to bog down your devs with this?

[Melkman]

Not every business is a software house. And IT departments wil not suddenly be terminated. Roles shift to different parts of the organisation. Billing is for the financial department. Filling SSO roles and identities is for HR. You still need staff knowledgeable of the used products and platforms. They are advising the business unit so why not put them there ? Most products are migrating to web based Saas. Businesses pick a platform and mandate that for SSO and office automation. Like Microsoft O365 or Google Workspace. No more need for own data centers or technical support by own staff. With shifting roles and decreasing workload there will be a time when it makes sense to just spread the remains and not have a separate department anymore.

[dijit]

Ok. So the laptop is managed by nobody, and HR has to configure SSO integrations?

Please.

Also, nobody has mentioned datacenters, datacenters are optional these days; the configuration of the software platform (whether it’s managed or not) still needs a somewhat competent technical person to make decisions and handle the implementation.

If you want to put that on your devs. That’s fine.

Next we’ll be talking about custodian duties being performed by JavaScript developers. It just reeks of ignorance; you wouldn’t want to do that even if you could.