<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bas Meeuwissen on Medium]]></title>
        <description><![CDATA[Stories by Bas Meeuwissen on Medium]]></description>
        <link>https://medium.com/@bas_masking?source=rss-62264684ff36------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8kA668oD3FWoxLtgnWFQ-g.png</url>
            <title>Stories by Bas Meeuwissen on Medium</title>
            <link>https://medium.com/@bas_masking?source=rss-62264684ff36------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:34:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bas_masking/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[An Introduction to Medium-Code]]></title>
            <link>https://medium.com/maskingtech/an-introduction-to-medium-code-12a9e68947cd?source=rss-62264684ff36------2</link>
            <guid isPermaLink="false">https://medium.com/p/12a9e68947cd</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[application-development]]></category>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Bas Meeuwissen]]></dc:creator>
            <pubDate>Mon, 30 Jan 2023 18:40:06 GMT</pubDate>
            <atom:updated>2023-01-30T18:40:06.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ULbdxwrI5KvBJ7eV" /><figcaption>Photo by <a href="https://unsplash.com/@mrthetrain?utm_source=medium&amp;utm_medium=referral">Joshua Hoehne</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In my <a href="https://medium.com/maskingtech/the-low-code-experience-from-a-developer-perspective-5a5613e983b9">previous article</a> I wrote about my experience with low code and the challenges I face when using it. I concluded that I am looking for something that I call <em>medium-code</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NnA3GivjREtS1VdP" /></figure><p>In this article I’m going to explain what it is and what it looks like. But I’m not doing this by myself. The co-author of this article is <a href="https://medium.com/u/ec9f0e30558b">Peter van Vliet</a>, a full-stack developer with more than 20 years of experience building high-code applications. In these years he dealt with the complexity that comes with high-code, which in his experience frequently leads to unnecessary overhead.</p><p>Since we both have challenges in our area of expertise we decided to try to solve these issues by combining our knowledge. The idea of medium-code sprang to mind and we started working on this.</p><h4>What is medium-code</h4><p>With medium-code we want to close the gap between high-code and low-code. Both worlds are far apart in the way developers build applications. High-code is technical oriented and text based whereas low-code is business oriented and GUI based. When taking a closer look there are similarities. Both provide standardizations to speed up development and are supported by tooling for optimizing the developer experience.</p><p>This means that the gap is mainly created by the orientation (technical vs business) and development approach (textual vs GUI). Due to the difference in culture between the types of developers, it is hard to understand each other. They miss a common language to communicate with each other.</p><p>Our vision is that this language should make code more like natural language and hide any underlying technical details. For this, <a href="https://en.wikipedia.org/wiki/Domain-specific_language">domain specific languages</a> (DSLs) can be created that meet these requirements, making them very suitable for closing the gap. This has led to the following definition.</p><blockquote>Medium-code is a framework of domain specific languages</blockquote><p>When looking at the purpose of a domain specific language (DSL), we can see it only has <strong>one</strong> specific purpose. This is in contrast to <a href="https://en.wikipedia.org/wiki/General-purpose_language">general purpose languages</a> (GPLs) used in high-code environments. Due to the nature of GPLs, they can be used to do nearly anything, where a DSL can only do what it is designed for. To make GPLs work in an application context a lot of abstraction is required.</p><p>The following example compares a GPL with a DSL for defining a data model. We’ve used Java as GPL, but similar definitions are created in other languages. As DSL we’ve used SQL because it’s one of the most used ones by non-programmers. Although SQL is still quite technical, an alternative DSL can be created that uses more natural terminology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*vQBMCxsHzGOkYb1WXrPiZw.png" /></figure><p>Although both define the same, the SQL code is more concise and straightforward. The Java code contains technical annotations, which add no business value and do we consider overhead. A low-code environment avoids technical overhead by providing visual development tooling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*OI4KcrDPuUEfxkhjMlij4A.png" /></figure><p>In this example the information and terminology are similar in both situations. This is an important part for closing the gap and needs to be taken into account when it comes to the design of a DSL.</p><p>Of course, building applications is more than defining data models. Therefore we also need DSLs for defining things like processes, security, user interfaces and more. By using a similar syntax, developers can learn them more easily. All DSLs must collaborate together in order to become very powerful. This makes it the framework that we call medium-code.</p><h4>The value of medium-code</h4><p>The value medium-code brings is — besides a better alignment of business and IT — mainly a higher developer productivity. As a seasoned low-code developer I speak from experience when I say that visual development is not always the optimal way to develop an application. Some tasks become very cumbersome, because I need to click through three levels of menus to find the configuration option I need.</p><p>If I could do the same in a code editor, I would be able to write the requirement in seconds. Code editors these days have intelligent tools, like syntax assist, auto completion and AI support to help me develop faster and reduce programming errors. Using code also makes it possible to share and reuse solutions across implementations. These are the biggest gains that aren’t available with visual development.</p><p>This makes a DSL a perfect intermediate solution because it can be edited using a code editor but can also be aided by visual development tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*YD-nX1Wu1s1kG8PDkyJSsA.png" /></figure><p>The enhanced productivity comes from the choice to do code editing and switch to visual development when it suits the situation. For example when an application developer is not comfortable with developing in code, or when aligning requirements with the business.</p><h4>Conclusion</h4><p>Both high-code and low-code bring a lot of value on their own, but both worlds are too far apart. Medium-code builds a bridge between these worlds by applying DSLs as intermediate languages. These languages are more natural, making them more understandable by the business and the developers, and enabling a more productive way of developing applications. In our ideal world applications are built with a combination of low, medium and high-code with a best-fit approach.</p><p>Thanks for reading our article to the end. We hope it brings some insights about our view on application development. We would love to hear what you think of medium-code.</p><p>In our next articles we want to publish more about medium-code, for example a deep dive into one of the DSLs we have. Or a detailed example of a use case using low-code, medium-code and high-code. Please leave us a comment to let us know what you think about this article or what you want to read about next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12a9e68947cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maskingtech/an-introduction-to-medium-code-12a9e68947cd">An Introduction to Medium-Code</a> was originally published in <a href="https://medium.com/maskingtech">MaskingTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The low code experience from a developer perspective]]></title>
            <link>https://medium.com/maskingtech/the-low-code-experience-from-a-developer-perspective-5a5613e983b9?source=rss-62264684ff36------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a5613e983b9</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[no-code]]></category>
            <dc:creator><![CDATA[Bas Meeuwissen]]></dc:creator>
            <pubDate>Fri, 23 Dec 2022 23:25:49 GMT</pubDate>
            <atom:updated>2023-01-30T18:41:25.603Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZroMGr4WA-fs7YZ1eaff7Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/fr/@seffen99?utm_source=medium&amp;utm_medium=referral">Sven Brandsma</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>On the internet there are numerous articles about the good, the bad and the ugly of low code. Why you should use them or why you shouldn’t. In this article I’m writing about my personal experience when developing software with low code. I have been using a low code platform for the last 12 years. That’s even before the dawn of low code itself. My experience is primarily based on the Pega platform for which I am a certified Lead System Architect, Pega’s most senior certificate, since 2014.</p><p>Low code platforms are sold for their focus on rapid application development and the ease of use by non-developers. It allows less technical people to participate in the development process. The platforms are also cloud first, which means that the infrastructure is taken care of by the platform supplier.</p><p>Let’s start off with the good news. In my opinion low code really works. The promise that it helps organizations to build applications faster with less professional developers is true. But there are a few side notes.</p><h3>The software process</h3><p>The first note I want to make is that a low code application is still software that needs to go through regular application development processes, like QA and security checks, to get deployed to production. Most of the marketing of low code is about faster development, but none of them talk about getting your application to production and maintaining it using IT approved processes. The <a href="https://en.wikipedia.org/wiki/DevOps">Dev(Sec)Ops</a> process entails much more than just development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*wBhmkHWO9VyQoe3hADYiew.png" /></figure><p>The image shows that the (visual) coding part is just one step in the whole process. Speeding up that step is nice, but that doesn’t automatically speed up the other steps. If you want to maintain the gained speed from coding, then the test step should be able to follow along. But low code platforms have limited capabilities for (unit) testing. Much of the testing needs to be done outside of the low code experience, or even using the runtime UI. It’s common knowledge that UI tests take the most time to write and execute. I would call this a big disadvantage. To put this in perspective. A citizen developer can drag and drop a process in hours, but it takes a professional tester days to test and automate that same process.</p><p>In my experience there is not much difference between the rest of the steps in the process. Once these are automated, the difference is in the tools used, rather than the time taken to execute them.</p><h3>Software customization</h3><p>The second side note is with respect to customization. Low code enables fast development because of all the pre-configured building blocks. They can easily be combined into working software, but the base is pretty rigid. The number of options to customize these blocks is limited for a good reason. It reduces the number of errors, makes the overall user experience more aligned and increases development speed.</p><p>But what happens when the business wants something that is not supported by the platform? The low code experience stops and you’ll need to resort to high code alternatives. Either write your own custom block in the high code, or build another app outside of the platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*KzNYGQmFadQ4A5W2hP3DSw.png" /></figure><p>More often than I wanted I had to resort to high code for things that are not delivered out-of-the-box. And the requirements were not really off the scale. A pdf merger, authentication options on setting up external services, custom UI elements, etc.. Note that I go back a long time and some of the items are added to the platform today, but a platform will always stay one step behind. The supplier simply doesn’t have the time to implement all of the new features that are released every day.</p><p>When doing high code it has some drawbacks that are not easily solved. The first is technical and related to platform updates. When using pre-configured components in your application, an update won’t have much impact. The correct behavior of these components is guaranteed on the next version of the platform. But high code is not guaranteed to work on the next version. Each component written by yourself needs additional verification after each update. For Pega, this means at least 4 times every year.</p><p>The second one is related to the developers that use the platform. Within the Pega community there aren’t many (lead) developers who can also write high code. That means that you’ll need a totally different person to code your solution. But that won’t be easy, as the programmer also needs to know the platform before they can code on it. The programmers I have spoken to are not keen on low code in general. They want their own tools and speak their own language. Simply put, programmers are not interested in low code platforms. And even if you find someone who can do it, you probably don’t want them to. Finding the next one is nearly impossible. This imposes a serious risk for the organization and means you should want to stay within the boundaries of the platform.</p><p>To demonstrate what the gap looks like, I have collected one example of high code that is required for a simple use case. When entering a phone number, it should be formatted in an international format (i.e. +31612345678).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/488/1*mAWg4ctxbksYEj-rnsXJmw.gif" /></figure><p>A custom piece of code is required for this.</p><pre>String tempValue = theValue;<br><br>if (tempValue.length() &gt; 0)<br>{<br>   tempValue = tempValue.replaceAll(&quot;[^\\d\\+]&quot;,&quot;&quot;);<br> <br>   if((tempValue.length() &gt; 10) &amp;&amp; (tempValue.charAt(0) == &#39;+&#39;))<br>   {<br>       //Assume number is already in right format<br>   } <br>   else if((tempValue.length() == 10) &amp;&amp; (tempValue.charAt(0) == &#39;0&#39;&amp;&amp; tempValue.charAt(1) != &#39;0&#39;))<br>   {<br>       //Assume Dutch number without countrycode<br>       tempValue = &quot;+31&quot; + tempValue.substring(1);<br>   }<br>   else if // etc<br>  <br>   theValue = tempValue;<br>}</pre><p>There is hardly any citizen developer who is going to understand the example above and can extend the functionality or fix bugs. They might search for a solution on the internet and copy paste code from untrusted sources. Imposing a whole different level of risk to your application.</p><h3>The development team</h3><p>The last side note is about less professional developers. Yes, citizen developers can build processes themselves, but they hardly have the technical knowledge to implement services, configure security and prevent an application from getting bloated. They do bring valuable insights and knowledge about the business domain, and talking to them directly in a language they understand is a very good thing.</p><p>But from what I have seen is that you’ll still need a lot of experienced, professional developers. Looking back at the first side note, a heavy investment is also required for test capacity. And with respect to the second site note, you’ll likely need a programmer to support custom code. That makes that the roles required for low code are the same as those required for high code, with the addition of (lead) platform developers like myself. And those are all necessary to enable a citizen developer to help with coding an application.</p><p>I spend most of my time coaching and mentoring citizen developers to use the concept and the tool correctly. I can help about two to three citizen developers in my team. That leaves me with little time to build components for them to use and that means I need another developer to do that for me.</p><h3>Conclusion</h3><p>As I have mentioned at the beginning, low code does work within the boundaries of the platform. As long as you stay within these boundaries, it’s hard to beat a low code system in producing your new application. You’ll get</p><ul><li>a way of enabling the business to closely collaborate with the development team;</li><li>great speed of development;</li><li>a consistent user experience;</li><li>and a very happy customer.</li></ul><p>But don’t go outside of the boundaries. The platform will turn against you and make your life <em>unnecessarily</em> hard, with delays and longer delivery times as a result.</p><p>Yet, I’m a professional low code developer who loves the concept of low code. The platform that comes with it enables me to better focus on what needs to be solved, rather than how to solve it. But I am also looking for the same advantages outside of the platform boundaries. Resorting to high code is an option I don’t like, because I think that the gap between high code and low code is too big. It requires a different set of developers, different tools and usually doesn’t align with the business very well.</p><p>In my ideal world, there is something in between. Something that is neither high or low code, as the high code example shows that these worlds are too far apart. I want a concept that builds the bridge between the two of them. A language that can be understood by both business and IT. With blocks that are small enough to create everything and can easily be combined into larger, let’s call them, pre-configured blocks. And with a representation of the business in mind, so the application reflects the way the business works. I would call this concept <strong>medium code</strong>. And I would like to explore more about this in a next article.</p><p>Thanks for staying with me. I’ve written my experience with low code, which might not be the same for everyone. The Pega platform is a great tool for building applications and I hope that’s also clear from the text.</p><p>What are your experiences with low code? And would you be interested in medium code? Please let me know in the comments.</p><p><a href="https://medium.com/maskingtech/an-introduction-to-medium-code-12a9e68947cd">An Introduction to Medium-Code</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a5613e983b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maskingtech/the-low-code-experience-from-a-developer-perspective-5a5613e983b9">The low code experience from a developer perspective</a> was originally published in <a href="https://medium.com/maskingtech">MaskingTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>