<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Low-Code on Wilhelm Maritz</title><link>https://wjmaritz.dev/tags/low-code/</link><description>Recent content in Low-Code on Wilhelm Maritz</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 04 Oct 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://wjmaritz.dev/tags/low-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Low-code is not no-logic: expression thinking in Power Automate</title><link>https://wjmaritz.dev/posts/low-code-expression-thinking/</link><pubDate>Sat, 04 Oct 2025 00:00:00 +0000</pubDate><guid>https://wjmaritz.dev/posts/low-code-expression-thinking/</guid><description>&lt;p>Developers tend to dismiss low-code tools, and I understand why: what you see first is boxes connected by arrows, which looks like flowchart software rather than programming. But that visible layer is only half the platform. Underneath every one of those boxes is an expression language, and that is where the actual logic lives.&lt;/p>
&lt;p>The distinction that made this click for me is the old one between &lt;strong>statements&lt;/strong> and &lt;strong>expressions&lt;/strong>. Statements do things. Expressions evaluate to values. In Power Automate the actions are statements, and their fields accept expressions.&lt;/p></description></item></channel></rss>