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?](/glossary/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?)

{% include weblinks.html url="https://twitter.com/GergelyOrosz/status/1582133778478080000" %}

<div class="card">
<div class="card-body">
<small class="text-muted p-0 m-0">\@GergelyOrosz via Twitter on Oct 17, 2022<a href="https://twitter.com/GergelyOrosz/status/1582133778478080000"> <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" class="bi bi-link-45deg" viewBox="0 0 16 16">
<path d="M4.715 6.542 3.343 7.914a3 3 0 1 0 4.243 4.243l1.828-1.829A3 3 0 0 0 8.586 5.5L8 6.086a1.002 1.002 0 0 0-.154.199 2 2 0 0 1 .861 3.337L6.88 11.45a2 2 0 1 1-2.83-2.83l.793-.792a4.018 4.018 0 0 1-.128-1.287z"/>
<path d="M6.586 4.672A3 3 0 0 0 7.414 9.5l.775-.776a2 2 0 0 1-.896-3.346L9.12 3.55a2 2 0 1 1 2.83 2.83l-.793.792c.112.42.155.855.128 1.287l1.372-1.372a3 3 0 1 0-4.243-4.243L6.586 4.672z"/>
</svg></a></small>
<p class="card-text">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.</p>
</div>
</div>