Winter Rant

"I’m utterly disgusted. I strongly feel that this is an insult to life itself." – Miyazaki

,

Threads Dev Interview #20: What is a draw-back of no code solutions?

What is a draw-back of no code solutions? [Threads] [Wayback Archive]

We shouldn’t confuse no-code tools with programming. I think that is where the perceived drawbacks will emerge from. I think No-code will be great for localized, cookie cutter automation or system building. But there will be limits to the amount of customization you can have with the resulting systems and automation. WordPress will give you a great site, but it will never be able to easily integrate with a Database unless you start writing code yourself.

No-code tools will also have the tendency for people to build systems that are so complex that they might have been better off if built using traditional software engineering and programming (which offer more control). This is something else that No-code tools would need to have: deliberate limitations that does not let systems get too complex (otherwise we might see flaky/hard-to-maintain systems).

Published by

Responses to “Threads Dev Interview #20: What is a draw-back of no code solutions?”

  1. […] This was a follow up question to my response on, What is a draw-back of no code solutions? […]

    Like

  2. […] What is a draw-back of no code solutions? [Threads] [Wayback Archive] [vpalepu.com] […]

    Like

Leave a reply to Threads Dev Interview #20: Are we going to start seeing “no-code developers” emerge? – Winter Rant Cancel reply