<?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: creativity coder</title>
    <description>The latest articles on DEV Community by creativity coder (@creativity_coder_2a6c5d6f).</description>
    <link>https://dev.to/creativity_coder_2a6c5d6f</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%2F3764786%2Fd15734d7-874c-490b-ab74-e1f34fbbe57d.jpg</url>
      <title>DEV Community: creativity coder</title>
      <link>https://dev.to/creativity_coder_2a6c5d6f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/creativity_coder_2a6c5d6f"/>
    <language>en</language>
    <item>
      <title>Why We Chose PostgreSQL Over NoSQL for our Multi-Tenant SaaS Boilerplate</title>
      <dc:creator>creativity coder</dc:creator>
      <pubDate>Tue, 02 Jun 2026 20:32:02 +0000</pubDate>
      <link>https://dev.to/creativity_coder_2a6c5d6f/why-we-chose-postgresql-over-nosql-for-our-multi-tenant-saas-boilerplate-emj</link>
      <guid>https://dev.to/creativity_coder_2a6c5d6f/why-we-chose-postgresql-over-nosql-for-our-multi-tenant-saas-boilerplate-emj</guid>
      <description>&lt;p&gt;As the lead architect at Creativity Coder, I evaluate database paradigms daily. While NoSQL (like MongoDB) offers incredible flexibility for rapid prototyping, we've firmly standardized on PostgreSQL with Prisma ORM for all our B2B SaaS deployments in 2026.&lt;/p&gt;

&lt;p&gt;Why? Relational integrity. When building custom CRM systems or financial tools, eventual consistency is unacceptable. You need strict ACID guarantees. By utilizing Row-Level Security (RLS) in Postgres, we can architect multi-tenant SaaS platforms that are secure by default, isolating tenant data at the database layer rather than relying purely on application-level filtering.&lt;/p&gt;

&lt;p&gt;In this guide, I'll walk you through how Creativity Coder sets up scalable Next.js + Postgres architectures for high-growth startups...&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>database</category>
      <category>postgres</category>
      <category>saas</category>
    </item>
    <item>
      <title>Hi developers👋 I’m the founder of Creativity Coder</title>
      <dc:creator>creativity coder</dc:creator>
      <pubDate>Tue, 10 Feb 2026 17:38:26 +0000</pubDate>
      <link>https://dev.to/creativity_coder_2a6c5d6f/hi-developers-im-the-founder-of-creativity-coder-4bo</link>
      <guid>https://dev.to/creativity_coder_2a6c5d6f/hi-developers-im-the-founder-of-creativity-coder-4bo</guid>
      <description>&lt;p&gt;Hi everyone,&lt;/p&gt;

&lt;p&gt;I’m Kenil Sangani, the founder of Creativity Coder, a small team building web and app products for startups and growing businesses.&lt;/p&gt;

&lt;p&gt;I didn’t start this company because I wanted to “write code for clients.” I started it because I kept seeing the same pattern over and over again:&lt;/p&gt;

&lt;p&gt;Projects failed after they were shipped.&lt;/p&gt;

&lt;p&gt;Not because the code was ugly. Not because the developer didn’t know React or Node.&lt;/p&gt;

&lt;p&gt;But because:&lt;/p&gt;

&lt;p&gt;Architecture wasn’t thought through.&lt;br&gt;
Permissions were added too late.&lt;br&gt;
Performance was “someone else’s problem.”&lt;br&gt;
Scaling was assumed, not designed.&lt;br&gt;
At some point, I realized:&lt;/p&gt;

&lt;p&gt;Writing code is easy. Building systems is the hard part.&lt;/p&gt;

&lt;p&gt;At Creativity Coder, we spend more time thinking than coding:&lt;/p&gt;

&lt;p&gt;How will this behave with 10× users?&lt;br&gt;
What happens when roles, plans, and permissions grow?&lt;br&gt;
Where will this break six months from now?&lt;br&gt;
Our stack is usually React, Node.js, MongoDB/PostgreSQL, Nginx, but tools change. Principles don’t.&lt;/p&gt;

&lt;p&gt;Why I’m here on dev.to&lt;br&gt;
I’m not here to teach basic syntax or sell services.&lt;/p&gt;

&lt;p&gt;I’m here to share:&lt;/p&gt;

&lt;p&gt;Real production bugs I’ve personally fixed.&lt;br&gt;
Mistakes I made as a founder and developer.&lt;br&gt;
Architecture decisions that hurt and helped.&lt;br&gt;
Lessons from building SaaS features like auth, roles, payments, and scaling.&lt;br&gt;
If you’re a developer who:&lt;/p&gt;

&lt;p&gt;Cares about long-term maintainability.&lt;br&gt;
Wants to build things that don’t collapse after launch.&lt;br&gt;
Or has been burned by “quick fixes” before.&lt;br&gt;
You’ll probably relate to what I’ll post next.&lt;/p&gt;

&lt;p&gt;Thanks for reading. Looking forward to learning with this community 👋&lt;/p&gt;

&lt;p&gt;Kenil Sangani&lt;br&gt;
Founder, Creativity Coder&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>programming</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
