<?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 Daniel Sobrado on Medium]]></title>
        <description><![CDATA[Stories by Daniel Sobrado on Medium]]></description>
        <link>https://medium.com/@dalamar01977?source=rss-e0a8b9037932------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Okve7nvMJn844GUz.</url>
            <title>Stories by Daniel Sobrado on Medium</title>
            <link>https://medium.com/@dalamar01977?source=rss-e0a8b9037932------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:50:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dalamar01977/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[Code vs No-Code]]></title>
            <link>https://medium.com/@dalamar01977/code-vs-no-code-3250445e8e38?source=rss-e0a8b9037932------2</link>
            <guid isPermaLink="false">https://medium.com/p/3250445e8e38</guid>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[low-code]]></category>
            <dc:creator><![CDATA[Daniel Sobrado]]></dc:creator>
            <pubDate>Tue, 19 Jul 2022 17:12:21 GMT</pubDate>
            <atom:updated>2022-07-19T17:12:21.089Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gkQQgDuHDfwiPuTX6RbR6A.jpeg" /></figure><p>Recently, there has been a lot of discussion on No-Code and Low-Code platforms. Largely as a result of the market’s scarcity of coding talent.</p><p>Senior management that frequently lacks practical technical knowledge, they come up with no code solutions to address their skill gap.</p><p>The demonstrations and sales pitches make fantastic claims that anyone can achieve great results with just a few mouse clicks.</p><p>Because coding is too complicated and there aren’t nearly enough skilled workers on the market, adopting No-Code seems like the right approach.</p><p>That’s nothing new; No-Code has always existed, fluctuating in popularity. It has never taken over programming, and it won’t this time either.</p><blockquote>“Because complexity and flexibility in our industry are trade-offs.”</blockquote><p><strong>You’ll probably succeed with no-code if all you need to do is something straightforward and repetitive with a established process and a well known number of actions and results.</strong> However, if you need something customized and with some edge cases that the sales demo didn’t cover, things get tricky.</p><p>When using a no-code tool, you may be able to customize it more by employing workarounds and sophisticated approaches at the cost of increased complexity, necessitating the hiring of skilled personnel with that specific technology knowledge, which is what you originally want to avoid.</p><p>You might also be <strong>limited by vendor lock-in, support SLAs, and, perhaps, a lack of public forums with quick answers</strong> (e.g. Stack Overflow).</p><p>Because there is no one solution that fits all problems, using a proprietary no-code technique may result in you bouncing from one problem to another if your problem statement is complex in nature.</p><p>Additionally, the product might not meet your future technical requirements or it might demand a higher level of sophistication, frequently in the form of specialized vendor development, inline coding, or challenging workarounds that weren’t mentioned in the initial sales pitch, and this could result in delays and unexpected complexity.</p><p>The key to selecting the appropriate tool, whether it calls for coding or a more basic tool with all of its limitations, is knowing your problem statement and future roadmap.</p><p>The truth is that there are some processes that are established and simply configurable with straightforward workflows, requiring little to no innovation in that area and requiring no complex logic to be deployed. These are typically unmistakable victories. (e.g. JIRA, ServiceNow…)</p><p>In contrast, it’s often not possible to simply replace code with workflows in generalist tools without suffering a significant loss in versatility that may eventually become problematic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3250445e8e38" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>