This article originally appeared on https://hilton.org.uk/blog/no-code-maintenance, written by Peter Hilton who is a Product Manager at BRYTER.
Software maintenance with no-code tools
Not writing code doesn’t make all of the work of automation go away. You can have fun building things, but someone will eventually want you to fix something, or ask you to support some new scenario. No-code solutions resemble traditional software, in this respect: maintenance hurts.
Software only becomes maintainable with some effort. The difference with no-code tools comes from their different affordances for keeping your implementation consistent, understandable, and explained.
Maintainability requires consistency, good naming, and documentation. With luck, your tools will help reduce the discipline and effort these require.
A programmer has a lot of freedom in how they write each line of code. Coding style matters, and different teams use different styles. No-code tools tend to offer less flexibility in the style of whatever you build, though. For better or worse, you can’t usually change the shape and colour of your boxes and arrows.
No-code tools make fine-grained consistency easier than programming languages.
At larger scales, however, low-code tools offer fewer ways to structure large projects. You typically can’t freely add groups and layers to what you build, in the same way that you can with programming languages, so you can’t structure your solutions consistently. While conventional coding often results in spaghetti code and lasagne architecture (many layers), it also enables higher-level abstractions that tame (or at least bury) the complexity.
Programming languages make coarse-grained consistency easier than no-code tools.
Default names, like untitled, belong to experiments that you’ll abandon by the end of the week. Maintainable software, however, requires good naming. Otherwise, you’ll end up looking at some calculation, and wondering what the numbers mean and whether they appear in the right order.
a ÷ b
b ÷ a
Programming languages resist good naming.
They restrict which names you can use, and rely on tools for renaming. No-code tools do better, typically allowing spaces and significant capitalisation. You can avoid something ambiguous like polishVat, and call it Polish VAT, say. No-code tools tend to have better renaming support, so you can improve names and fix typos without risking breaking anything.
No-code tools have limited support for named abstractions, such as a Discount policy, that you can reference by name. Meanwhile, programming languages love named abstractions - functions, objects, classes, etc.
Programming languages typically let you name more things than no-code tools.
Despite programmers’ widespread contempt for code comments, for documenting code, all mainstream programming languages support them. Many programming environments even extend this basic support with tooling to automatically extract documentation comments into external documents.
Programming languages have consistent but mediocre integrated documentation support.
Perhaps programmers’ own attitudes hold back no-code documentation capabilities. Spreadsheets, for example, typically let you attach comments to individual cells, but not to whole sheets. And few spreadsheet users compensate with a documentation sheet to explain the other sheets.
No-code tools have the opportunity to address documentation far more effectively than programming languages can, using richer content than the unstyled text that programmers reluctantly write. But consistency, naming and documentation only matter to people who’ve learned not to ignore maintenance. Usually the hard way.