The debate about low-code is in full swing with developers from all backgrounds weighing in. What’s your take? Does low-code mean more or less spaghetti code? Here’s the low-code low-down:
Low-code / no-code is the future of software engineering.
True. But: it’s a part of software engineering’s ongoing simplification through a variety of productivity-enhancing inventions.
No-code and low-code are the same.
False: no-code is for non-coders. Low-code is for software engineers.
I am a developer, no-code isn’t for me.
True: professional 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.
Low-code / no-code tools will make developers redundant.
False. They are productivity-enhancing tools, but not substitutes for humans writing code.
It doesn’t matter which no-code / low-code tool to learn first.
False. Use three questions to create a shortlist of platforms (check out my earlier article on this topic to find out what these three questions are).
With low-code, I will eventually hit a brick wall for complex use cases.
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.
Individual skill determines software engineering teams’ productivity.
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.
To learn more about each one of the seven points above, check out my other posts on Hackernoon!