Planning to write a blog about this topic, but before I do, I would like to hear your thoughts on "no code".
Do you like “no code”?
What do you like/dislike about it?
Personally I dislike the term, and I'm planning to write an article about why.
I would like to hear your perspective first though, so hopefully my article will be more well rounded.
Top comments (12)
I think it is a great tool for non-technical managers or designers to build a prototype, validate it with real customers, and make sure they know what they want to deliver. It many hands of developers so they can keep working on serious apps and systems and make important long-term architectural decisions. Without "no code" solutions they would have to spend much more time prototyping and reworking something, overengineering it at a certain point, and then throwing the whole thing away when the manager realizes that the validation part was not successful enough.
The problematic part comes when those non-tech people decide the "no-code" prototype can go live as a final product and start asking developers to "just" add a little button doing XYZ so they can deploy a big marketing campaign. It would be great if those "no code" tools would help understand the limitations of the solution to their users clearly enough and not sell them "we can do everything for you, fire your dev team".
Yeah I agree that the tools are not being honest to people about what they can truly do. Thanks for your comments!
You have to ignore the literalness of the term, and that's hard for developers to do.
The no code thing is a good thing. It opens the doors for those who lack the coding super power we all possess. And for all of us with this power, it keeps us focused on the goal versus the rabbit hole.
I think you are right. Thank you for your thoughts.
No code is annoying, because it’s a buzzword and a lot of buzzwords get overused or get “hyped.” I don’t think no code is true to its name, but hey if you can empower a lot of non-developers to build applications, by all means that sounds like a valuable resource.
For sure. Thanks for your input!
25-30 years ago "no code" was called "4gl". Those of us who remember such things remember the messes that had to be cleaned up. Also, we remember the dependencies that were created on the vendors who were selling these solutions: no code = no easy way to fix it yourself once the vendor is out of business.
"No-code" tools are great for prototyping ideas and learning to think more efficiently in terms of functionalities/logic. The hype behind it though has created the illusion that you can completely replace developers by combining 5-6-7 no-code tools to build something you have no idea how it works or if it's safe to use. Having said that, I'm a designer myself and use Webflow as a design/prototyping tool. But I see lots of people wanting to build products on top of it...
I think writing code is the fastest way when dealing with logic and programing.
But for html/css, I think nocode tools like Desech Studio are exactly what's needed to be more efficient. Why create a gradient by hand without any visual feedback, when you can use a slider and proper tools to build. And this also applies to animations, effects, transforms, and also to margins and sizes.
I'm not a fan of "no code" tools because I think their implementation is too dogmatic: they see code as something dirty and to be avoided. Sometimes, a few lines of code are much more powerful than what its no-code counter part can accomplish elegantly. Regular expressions are a great example of this.
That said, I'm a big fan of "low code" tools that provide opportunities to drop down into code when you need the extra power.
I love using WordPress page builders like Elementor for this reason: I can drag-and-drop a page together extremely fast, then I have escape hatches for custom HTML/CSS/JS/PHP if needed. Sure, if I wrote it all by hand it would handle responsive breakpoints a little better and it might be a bit faster. But it would take me three times as long for something that is only marginally better.
The real challenge is understanding the boundaries of what no-code/low-code tools can reasonably accomplish, and making sure you stay within its capabilities. I've seen a project manager commit to using a low-code tool without understanding its capabilities, and the whole project ended up way behind schedule and WAY over budget.
I believe no-code is a great tool for scientists and people learning to think logically. I have come across it several times in science and in education. However, I think it needs more research and development.
Consider Scratch? I have taught fourth graders Scratch and some kids couldn't get enough. I don't know if Scratch is the best way to learn coding, but children under high-school age need to learn how computers work and how to manipulate them easily. Once, I was chastised by other teachers that I thought my kids could be programmers!?! But what better way to learn Cartesian coordinates? Vectors? Translation? Transformations? Boolean logic? Need I go on?
I have also seen it used successfully in science by biologists and chemists that weren't formally taught C.S. Netlogo is one of several tools that I have seen used to simulate everything from bee behavior to egress simulation by fire engineers. One guy I knew in grad school was from Suadi Arabia. He needed to simulate fire escape routes since the Saudis don't want to mix the male and female populations even in emergencies. (???) Crazy but true.
Besides, who hasn't watched Star Trek TNG and watched Jordi program the 'holosuite' just by describing it? Who doesn't want that? ;))
I was looking over another post on No-code and thought about ONE more item that you might be interested to learn about, Galaxy. Ultimately one can work with something like this...