<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Meg</title>
    <description>The latest articles on DEV Community by Meg (@megsignable25).</description>
    <link>https://dev.to/megsignable25</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3584337%2F9c290c58-73f4-40de-9412-23c6532c5f20.png</url>
      <title>DEV Community: Meg</title>
      <link>https://dev.to/megsignable25</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/megsignable25"/>
    <language>en</language>
    <item>
      <title>Are we building smarter tech stacks or just adding more tools?</title>
      <dc:creator>Meg</dc:creator>
      <pubDate>Mon, 27 Oct 2025 15:54:45 +0000</pubDate>
      <link>https://dev.to/megsignable25/are-we-building-smarter-tech-stacks-or-just-adding-more-tools-43gn</link>
      <guid>https://dev.to/megsignable25/are-we-building-smarter-tech-stacks-or-just-adding-more-tools-43gn</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;“We’ve already moved from paper to digital…but now we’re entering what I call the era of 'digitaler'. Not more tools, but better-connected ones. Not digitising for the sake of it, but simplifying the digital world we already live in.” - Andy Jackson, Lead Product Manager at Signable&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That line from a recent piece by our product team really stuck with me. At Signable, we’ve been talking a lot about what “digitaler” means in practice. It’s so easy for businesses to chase more tech - more integrations, dashboards, tools - in the name of progress. But is it actually making things simpler for teams, or just moving the complexity somewhere else?&lt;/p&gt;

&lt;p&gt;So I wanted to throw this question to the Dev community:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How do you balance building or using APIs that simplify versus APIs that add another layer?&lt;/li&gt;
&lt;li&gt;What makes an API “developer-friendly” to you? Documentation, setup speed, sandboxing, consistency?&lt;/li&gt;
&lt;li&gt;And what’s one thing you wish more SaaS platforms understood about how devs actually use their APIs?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you’re curious, here’s the full piece that inspired this post: &lt;a href="https://www.signable.co.uk/the-digitaler-era-apis-for-a-smarter-tech-stack/?utm_source=dev.to&amp;amp;utm_medium=referral-pr&amp;amp;utm_campaign=api&amp;amp;utm_content="&gt;The ‘Digitaler’ Era: APIs for a Smarter Tech Stack&lt;/a&gt;. Would love to hear your takes, especially from anyone who’s built or integrated an eSignature or workflow API. What’s working, what’s painful, and what would you change?&lt;/p&gt;

</description>
      <category>api</category>
      <category>saas</category>
      <category>automation</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
