<?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: Jay Patel</title>
    <description>The latest articles on DEV Community by Jay Patel (@jay_patel).</description>
    <link>https://dev.to/jay_patel</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3982135%2F2264fcf1-caa3-452f-be7d-7d1f472f5531.png</url>
      <title>DEV Community: Jay Patel</title>
      <link>https://dev.to/jay_patel</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jay_patel"/>
    <language>en</language>
    <item>
      <title>Stop Secret Leaks Before Merge: How I Built Secura for &lt;50ms In-Memory PR Security</title>
      <dc:creator>Jay Patel</dc:creator>
      <pubDate>Fri, 20 Nov 2026 03:46:16 +0000</pubDate>
      <link>https://dev.to/jay_patel/stop-secret-leaks-before-merge-how-i-built-secura-for-50ms-in-memory-pr-security-3dmi</link>
      <guid>https://dev.to/jay_patel/stop-secret-leaks-before-merge-how-i-built-secura-for-50ms-in-memory-pr-security-3dmi</guid>
      <description>&lt;p&gt;Every developer knows the sinking feeling of running &lt;code&gt;git push&lt;/code&gt; and realizing a split second later that a live Stripe key, AWS credential, or database connection string was hardcoded inside the diff. &lt;/p&gt;

&lt;p&gt;Once a secret enters a Git commit history—even in a private repository—you have to assume it is compromised. Revoking keys, rotating production secrets, and rewriting Git history (&lt;code&gt;git filter-repo&lt;/code&gt;) wastes hours of engineering time.&lt;/p&gt;

&lt;p&gt;Yet most existing secret scanners force teams into a bad trade-off:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Heavy CI/CD bottlenecks:&lt;/strong&gt; Traditional scanners spin up Docker containers, clone your entire repository onto third-party vendor disks, and add &lt;strong&gt;5 to 12 minutes&lt;/strong&gt; to every pull request check.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Alert fatigue:&lt;/strong&gt; Naive regex-only scanners blindly match strings across your codebase, spamming PRs with false alarms on mock test fixtures (&lt;code&gt;dummy_token_123&lt;/code&gt;), comments, and placeholder strings (&lt;code&gt;YOUR_API_KEY&lt;/code&gt;).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;To solve this without adding developer friction, I built &lt;strong&gt;Secura&lt;/strong&gt;—an autonomous pull request security gate that connects to GitHub in 30 seconds, inspects diffs in-memory in &lt;strong&gt;under 50ms&lt;/strong&gt;, and retains &lt;strong&gt;0% of your source code&lt;/strong&gt;.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Try Secura Live:&lt;/strong&gt; &lt;a href="https://secura.ink" rel="noopener noreferrer"&gt;secura.ink&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Install the GitHub App:&lt;/strong&gt; &lt;a href="https://github.com/apps/secura-security-scanner" rel="noopener noreferrer"&gt;github.com/apps/secura-security-scanner&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GitHub Repository &amp;amp; Docs:&lt;/strong&gt; &lt;a href="https://github.com/jay240322/Secura-security-scanning" rel="noopener noreferrer"&gt;github.com/jay240322/Secura-security-scanning&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devsecops</category>
      <category>security</category>
      <category>github</category>
      <category>python</category>
    </item>
    <item>
      <title>The awkward middle ground between full-stack and cloud infrastructure</title>
      <dc:creator>Jay Patel</dc:creator>
      <pubDate>Sat, 13 Jun 2026 13:00:06 +0000</pubDate>
      <link>https://dev.to/jay_patel/the-awkward-middle-ground-between-full-stack-and-cloud-infrastructure-23d7</link>
      <guid>https://dev.to/jay_patel/the-awkward-middle-ground-between-full-stack-and-cloud-infrastructure-23d7</guid>
      <description>&lt;p&gt;Hey guys,&lt;/p&gt;

&lt;p&gt;Lately, I’ve been trying to bridge the gap between my day-to-day work as a full-stack MERN dev and the infrastructure side of things as an associate cloud engineer.&lt;/p&gt;

&lt;p&gt;Honestly, the deeper I go down this rabbit hole, the more I realize how weirdly blurred the lines have gotten.&lt;/p&gt;

&lt;p&gt;It feels like full-stack devs are now expected to be mini-DevOps engineers who just casually containerize everything with Docker, write GitHub Actions CI/CD YAML files from scratch, and debug K8s cluster networking on a Tuesday afternoon. Meanwhile, cloud teams are playing a never-ending game of whack-a-mole, trying to figure out how to handle application secrets without losing their minds when a dev accidentally hardcodes an &lt;code&gt;.env&lt;/code&gt; variable.&lt;/p&gt;

&lt;p&gt;I’m really curious to see how other teams are splitting the bill on this in the real world.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you’re a full-stack dev:&lt;/strong&gt; How much of the cloud config do you &lt;em&gt;actually&lt;/em&gt; touch before handing it off? Are you just writing the &lt;code&gt;Dockerfile&lt;/code&gt; and throwing the image over the wall? Or are you actively configuring API Gateways, provisioning databases, and tweaking AWS IAM policies? Where do you think the boundary &lt;em&gt;should&lt;/em&gt; be?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;And for the DevSecOps / Cloud Architecture folks here:&lt;/strong&gt; What is the absolute biggest "please, for the love of clean architecture, don’t do this" mistake you see web devs make when they try to ship a Node/Express app to production?&lt;/p&gt;

&lt;p&gt;Is it running containers as root? Is it using &lt;code&gt;latest&lt;/code&gt; tags for base images in Docker? Or maybe passing production DB credentials as plain text in the CI pipeline?&lt;/p&gt;

&lt;p&gt;I’d love to hear some perspectives, hot takes, or absolute horror stories in the comments. How is your team handling the dev-to-cloud handoff right now? 👇&lt;/p&gt;

</description>
      <category>devops</category>
      <category>cloud</category>
      <category>webdev</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
