Thanks for the article. It's so important to avoid the "one size fits all" mentality. There's a huge range of software tools, with those for users at one end and those for toolmakers at the other. No Code sits towards the user end, while C, JS and Python are more suited to toolmakers (who might be using them to build No Code tools). In between there are products like SQL and AppleScript.
Only a novice or a fool believes that a single tool can do all jobs equally well. It requires experience to recognize the best tool to use for any given job, and a good engineer is always on the look out for better, more efficient ways of doing things rather than just reaching for the same screwdriver or hammer each time.
For me, warning bells start to ring when low-level coding tools are used to build high-level products such as UIs or to express business logic. Both invite the creation of products that are essentially unmaintainable; they rely too much on what was in the mind of the builder, which is seldom visible in the resulting code. These areas are where No Code scores right now, and as it matures its scope will no doubt expand.
Thanks for reply! I'm still coding with JS and Python, however, I use No-Code tools when I want to create some sort of landing page or as I said to make the easy part by this, so it will never fully replace coding, just and additional information that can be useful for you!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the article. It's so important to avoid the "one size fits all" mentality. There's a huge range of software tools, with those for users at one end and those for toolmakers at the other. No Code sits towards the user end, while C, JS and Python are more suited to toolmakers (who might be using them to build No Code tools). In between there are products like SQL and AppleScript.
Only a novice or a fool believes that a single tool can do all jobs equally well. It requires experience to recognize the best tool to use for any given job, and a good engineer is always on the look out for better, more efficient ways of doing things rather than just reaching for the same screwdriver or hammer each time.
For me, warning bells start to ring when low-level coding tools are used to build high-level products such as UIs or to express business logic. Both invite the creation of products that are essentially unmaintainable; they rely too much on what was in the mind of the builder, which is seldom visible in the resulting code. These areas are where No Code scores right now, and as it matures its scope will no doubt expand.
Thanks for reply! I'm still coding with JS and Python, however, I use No-Code tools when I want to create some sort of landing page or as I said to make the easy part by this, so it will never fully replace coding, just and additional information that can be useful for you!