IH needs a pro-code group and here's why
I see IH has a very large group for no-code-based tech and a somewhat smaller one for low-code. I'm excited for this emerging concept and kinda freaked out about how powerful it could be, especially when combined with WASM/WebAssembly edge/near-edge containers & datastores.
What IH group is serving pro-code's userbase?
Or, is the concept so new it simply doesn't exist yet?
*edits to title: I suck at copy.
Anyone experienced will know why no-code/low code won't work in the longer term. It works really well as a rapid application development (RAD). It doesn't work as it's hard to scale and low barrier-to-entry, etc. It's more of a product/service to enable niche application and not a platform.
I think as a small IH, a lot of IH here are just using existing technology to build a product-fit for a niche market. Which is a good use case for no/low code. But again, as the business scales, moving away is such an easy migration (since everything is quite well understood/defined), that I think no/low code platform will always hit a wall regards to growth.
This comment has been voted down. Click to show.
You are right. Internal tools typically have different requirements though. One can also use any of the traditional RAD tools.
"Here's why"
Literally says nothing about why...
because the concept of JavaScript/WASM containers making up a pro-code pluggable system is fascinating. Sorry I didn’t make it more clear.
The definitions of no-code, low-code, and pro-code I’m basing my understanding on are spelled out in detail here: https://towardsdatascience.com/no-code-low-code-and-pro-code-a71b25935d2b
What does pro-code mean?
I understood it to mean a professional dev writes custom code for just the important bits that are plugged into a larger system.
That is low-code if you mean plugged into no-code tools.
Not according to this: https://towardsdatascience.com/no-code-low-code-and-pro-code-a71b25935d2b
I think according to this definition, the original Windows Control Panel’s .cpl applet system is an example of pro-code.
Interesting never heard the term "pro-code" in the no-code space after building a tool for it for 5+ years.
anti-no/low code I guess?
I think it would mean more defaulting to code whereas no-code defaults to no-code tools.
Most of the indie hackers on the wbe space are "pro-coders" in case you want to meet more indie devs ;)