Beyond Shipping: How to Keep Your Low-Code Solutions Healthy

Abstract

Low-code is wonderfully fast to build in. The question is what happens after launch. Solutions grow, modules multiply, connectors pile up, and at some point a small change starts to feel risky.

So what does "maintainable code" mean when the code is a canvas app and a handful of flows? The software engineering ideas behind it are old and boring and they still work: keep apps short, keep logic simple, reuse components, draw clear lines between the parts, automate the bits worth automating.

Quick demos throughout, aimed at solutions you will still enjoy improving a year from now.