16 comments

[ 3.0 ms ] story [ 48.4 ms ] thread

    For example, low-code/no-code software development platforms
    allow employees to drag and drop application components,
    connect them together and create mobile or web apps without
    programming skills. It’s another function of the old IT
    department that is no longer necessary.
ROFLCOPTERING TO INFINITY

Anybody else remember when Visual Basic for Applications was going to make hand-written line-of-business code vanish overnight, replaced by point-and-click MFC widgets?

Also LOL at "we've decentralized technology decisions, people can do whatever they want as long as they use the company-wide-prescribed languages, protocols, and software architecture".

what they are really saying: we hzve realized we need to vet& pay IT like theyre cia agents becauze they vulnerable to all kinds of side channel attacks.
Ignorance is bliss.

It is only ignorance that allows someone to so foolishly state what has been communicated in this article.

You will _always_ need people to keep up with support contracts, be that your "no code" systems or your desktop computer.

People will always expect email to "just work" and they assume that it's going to just work, but, even if you outsource your email services to Microsoft or Google: It's not that easy.

What about your assets? If you're working on a product, where are you storing everything? Dropbox? Where's your backups.. because dropbox is not a backup..

Argh, obviously everything is domain driven but this is just drivel. Probably just rage bait for clicks.

How does this even get published let alone at WSJ. It’s that cliched person in the office who is clueless of what IT does.
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.
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?

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.
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.

(comment deleted)
Just imagine the future! Each department has their own IT. They can buy phones themselves. And fix contracts for anything they need. Buy computers. And their own software! They decide which office suite they want. And their own servers with storage networks when they need any. And their own networks complete with firewalls, load balancers and LDAP. Each department can have their own login solution. And their own way of sharing files, chatting and have video meetings.

As long as no person ever tries to communicate, share documents or other information with a person from another department. That might cause some problems. /s

Msg a URI link, grant requested permission when opened.
We moved to o365, I was worried for my good friends the exchange admins, because the entire premise of saving money by moving to the cloud is that you can get rid of people.

Good (?) news is that they're busier than they've ever been, even needing more support from other admins.

Turns out, TANSTAAFL

I do wonder how many times we need to learn this.

We use O365 for years. It is still a software you install on local Windows machines (almost nobody uses the browser version). Aside from billing very little has changed.

Cloud made IT a bit easier, but it is still the old work. Since we are lacking IT personal, devs have to support IT (2 IT people for 300 employees, we have difficulties hiring IT staff because most of the good ones have build a their own business by now).

But since devs run in a completely different environment in their own subnet, devs can only do so much to support corporate IT. We are delegated to fix old certificates and stuff like this.

> What the bank and the energy company and a handful of other organizations have realized is that segregating IT makes it nearly impossible to have the agility, speed and flexibility that customers demand

We are about 100x faster than you will be without an IT department.