Low Code

Pegasystems CTO: No silver bullets, low-code software dos & don’ts

We’ve known low-code software shortcuts in one form or another for many years before the current revolution. Pegasystems CTO Don Schuerman reflects back on this technology’s current guise and helps to provide a few low-code dos and don’ts.

Two buttons on a yellow background, one is green for ‘dos’ and the other is red for ‘donts’

The software industry loves a new label. So-called DevOps practices unifying developer and operations teams existed in various forms long before the DevOps revolution of the last decade or so. Artificial Intelligence (AI)-based inference systems existed well before the current AI epiphany phenomenon.

Perhaps even more fundamentally, software engineers have been drawing curly cloud bubbles around groups of network instances long before the advent of cloud, hence the name, obviously.

A pertinent popularisation period

Similarly, in many ways, low-code software shortcuts and templates have been used by software developers for at least half a century as engineers worked out ways of encapsulating certain repeatable functions and building macro-style automations into their programming procedures.

Not to downplay the new era of low-code completely, there are clearly now dedicated platforms that offer speedier acceleration and automation functions that many of us may have ever dreamed of. But this is not plug-and-play technology so we need to think about how we apply it when, where and how.

Helping to navigate a selection of the core dos and don’ts of the low-code no-code (LC/NC) space, Don Schuerman offers his viewpoint is his role as CTO of Pegasystems,  a company known for its customer engagement data platform with specific low-code functionalities.

To continue reading this article register now