“Nearly everyone working in tech has an opinion about low and no code tools.”
– Katrina Dene, Director of Communications, StackOverflow
The debate about low-code will keep the dev community busy for a while. What’s your take? Does low-code mean more or less spaghetti code? If you’re still not sure here’s our TL; DR about low-code software engineering:
True. But it’s a part of software engineering’s ongoing simplification through a variety of productivity-enhancing inventions.
False: no-code is for non-coders. Low-code is for software engineers.
True: real developers are likely to get frustrated with the loss of control in a pure no-code tool. Well-designed low-code tools that make software engineering more efficient are the right tools for experienced developers.
False. They are productivity-enhancing tools, but not substitutes for humans writing code.
False. Use three questions to create a shortlist of platforms.
False, provided you pick the right platform for the right use case. Selecting the right tool before starting to develop will save you a lot of time down the road.
True and false. Of course, individual skill makes a big difference in outcomes. But when you treat software engineering like an engineering process, increased productivity can also result from better dev tools. Low-code, for example, can accelerate app delivery by up to 10x, according to Forrester.
Those were our seven lessons on low-code software engineering. If you’d like to read more, here’s a list of all lessons with links to our website: