David: Well, obviously in the first instance these developers will need to spend at least some of their time facilitating new citizen developers. There still needs to be some guidance, as you bring people on, to understand what the standards are and how to approach certain problems.
But beyond that, as a company we’re going to be able to refocus our high-dollar IT resources — those traditional developers — on the more complex projects we have, the harder problems.
The analogy is that of the highly skilled craftsman. You don't necessarily want them sitting there carving out block stones for a building. That's not a good use of their time or the value that they can add.
So if you can teach someone else how to do those simpler tasks, then the craftsman can work on the architecture of the building, or maybe one of the fine complicated aspects. It’s the same thing for me from a development standpoint, right?
Sudheer: Absolutely. And we’re already seeing that shift take place. Traditional developers on my team are focusing more on innovation and working on more complex tasks.
We’ve been able to work on a system to automate some day-to-day IT tasks. In the past, we were too involved in keeping the lights on to focus on a long-term project like this. That’s a huge change.
Sudheer and David are two of the experts we’ve been interviewing on the IT skills gap, low-code development, and citizen developers. For more on these topics, check out:
Jonathan Reichental, CIO of the city of Palo Alto, on why we face a skills gap in the Fourth Industrial Revolution; Anna Rodriguez of Slalom on how developer skills can keep pace with tech trends; Michael Krigsman of CXOTalk on why the growing skills gap is provoking an “innovation vs efficiency” struggle in IT, and Sarah Franklin of Salesforce on how to empower everyone to be a developer.