Low-Code Programming Models
I&#x27;ve long been interested in low-code, because it&#x27;s one of those things where the benefits <i>seem</i> obvious, but become less obvious the more you think about it.<p>In some cases the benefits are plain to see. For instance, if you needed to represent a squiggly line in SVG, the natural movement of a user&#x27;s hand guiding a digital pencil is going to be far superior than writing out each x&#x2F;y position in a vector path.<p>But other use cases aren&#x27;t so clear, and in fact, many tasks could be made far more efficient with a textual interface.<p>I think the reason people assume that code is time-consuming or complex, is because historically it&#x27;s been used to solve complex problems that non-technical users don&#x27;t understand. So in other words, they don&#x27;t understand the problem domain. My theory is that if they understood the problem domain, then they could understand any formal syntax dedicated to the domain.<p>As an example, the following pseudo-code:<p><pre><code>  begin dishwashing:
    gather(plates)
    sink.load(plates)
    each plate(rinse)
    each plate(dishwasher.load)
    dishwasher.on()
  end dishwashing
</code></pre>
Everyone understands the problem domain (how to wash dishes), so even though someone may be unfamiliar with historical programming conventions and syntax, they should be able to grasp what the code does.<p>It&#x27;s something I&#x27;m exploring with this language I&#x27;ve been building called Matry: <a href="https:&#x2F;&#x2F;matry.design" rel="nofollow noreferrer">https:&#x2F;&#x2F;matry.design</a>.