Musings on seeing the below tweet: How might the experience searching (for solutions or fixes) when building with low-code tools differ from the more code-centric (wc?) tools (like Python or Bash)? Scripting languages have large (though not always welcoming) communities with existing solutions and support. How do those building low-code tools consider how they might prepare documentation, exception handling, and naming? Can low-code tools be examined as a still higher-level programming language? (Akin to how some have suggested we view prompt engineering with code generation tools?)
The explosion of low-code tools to build internal-facing tools is incredible.
Retool being the best-known one, and Appsmith, Bubble, Budibase, Internal .io, Softr, Superblocks, Tooljet and so many more show that there’s a big shift in how companies want to build internal tools.
The explosion of low-code tools to build internal-facing tools is incredible.
Retool being the best-known one, and Appsmith, Bubble, Budibase, Internal .io, Softr, Superblocks, Tooljet and so many more show that there’s a big shift in how companies want to build internal tools.