<?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: Feya Shah</title>
    <description>The latest articles on DEV Community by Feya Shah (@feya_shah_d38339cad4bf2ff).</description>
    <link>https://dev.to/feya_shah_d38339cad4bf2ff</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%2F3290713%2Fd8816cfb-22b8-4aba-b7ef-b5bde6033784.jpg</url>
      <title>DEV Community: Feya Shah</title>
      <link>https://dev.to/feya_shah_d38339cad4bf2ff</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/feya_shah_d38339cad4bf2ff"/>
    <language>en</language>
    <item>
      <title>I’m Building a Podcast-to-Clips Micro SaaS (Manually First)</title>
      <dc:creator>Feya Shah</dc:creator>
      <pubDate>Tue, 30 Dec 2025 08:20:04 +0000</pubDate>
      <link>https://dev.to/feya_shah_d38339cad4bf2ff/im-building-a-podcast-to-clips-micro-saas-manually-first-39o6</link>
      <guid>https://dev.to/feya_shah_d38339cad4bf2ff/im-building-a-podcast-to-clips-micro-saas-manually-first-39o6</guid>
      <description>&lt;p&gt;I’ve started building a small micro SaaS: turning long-form podcasts or videos into short clips for Instagram Reels, YouTube Shorts, etc.&lt;/p&gt;

&lt;p&gt;But here’s the important part: I’m starting completely manual. No AI. No automation. No backend.&lt;/p&gt;

&lt;h2&gt;
  
  
  And this post is about why.
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The idea&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The core problem is simple:&lt;/p&gt;

&lt;p&gt;Creators post long videos, but:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;they don’t have time to clip them&lt;/li&gt;
&lt;li&gt;they don’t know which moments will work as short-form&lt;/li&gt;
&lt;li&gt;or they just procrastinate on it&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;My idea is straightforward:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a creator sends a YouTube link (or video)&lt;/li&gt;
&lt;li&gt;I clip 2–5 short vertical videos&lt;/li&gt;
&lt;li&gt;add basic captions&lt;/li&gt;
&lt;li&gt;send them back&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That’s it.&lt;/p&gt;

&lt;p&gt;Why I’m not building AI or automation (yet)&lt;/p&gt;

&lt;p&gt;As a developer, the instinct is always:&lt;/p&gt;

&lt;p&gt;“Let me automate this.”&lt;/p&gt;

&lt;p&gt;But I’m deliberately not doing that at the start.&lt;/p&gt;

&lt;p&gt;Reasons:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;I want to validate real demand, not assumptions&lt;/li&gt;
&lt;li&gt;I want to understand what creators actually want&lt;/li&gt;
&lt;li&gt;I want feedback before writing serious code&lt;/li&gt;
&lt;li&gt;I don’t want to overbuild something nobody uses&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Right now, the product is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;me (yes, just me)&lt;/li&gt;
&lt;li&gt;simple tools&lt;/li&gt;
&lt;li&gt;a lot of learning&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  And that’s okay.
&lt;/h2&gt;

&lt;p&gt;*&lt;em&gt;The MVP approach&lt;br&gt;
*&lt;/em&gt;&lt;br&gt;
The MVP is intentionally boring:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No login&lt;/li&gt;
&lt;li&gt;No dashboard&lt;/li&gt;
&lt;li&gt;No payments&lt;/li&gt;
&lt;li&gt;No storage&lt;/li&gt;
&lt;li&gt;No fancy UI&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Just:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a simple landing page&lt;/li&gt;
&lt;li&gt;an intake form&lt;/li&gt;
&lt;li&gt;manual delivery&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  If people don’t want this when it’s simple, adding AI won’t magically fix it.
&lt;/h2&gt;

&lt;p&gt;*&lt;em&gt;Building in public&lt;br&gt;
*&lt;/em&gt;&lt;br&gt;
I’ve decided to document this journey openly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;decisions&lt;/li&gt;
&lt;li&gt;doubts&lt;/li&gt;
&lt;li&gt;progress&lt;/li&gt;
&lt;li&gt;mistakes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Not as a “success story”, but as a real build-in-public experiment.&lt;/p&gt;

&lt;p&gt;I recorded a short YouTube video explaining the idea and my approach:&lt;/p&gt;

&lt;p&gt;👉 Watch the video here:&lt;br&gt;
&lt;a href="https://www.youtube.com/watch?v=O2trQxOtVoU&amp;amp;t=4s" rel="noopener noreferrer"&gt;https://www.youtube.com/watch?v=O2trQxOtVoU&amp;amp;t=4s&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you have any suggestions for me, or would like to try out the tool and provide me some early feedback, please reach out!&lt;/p&gt;

</description>
      <category>saas</category>
      <category>buildinpublic</category>
      <category>startup</category>
      <category>product</category>
    </item>
    <item>
      <title>How Docker Works Internally: From Images to Containers</title>
      <dc:creator>Feya Shah</dc:creator>
      <pubDate>Wed, 02 Jul 2025 17:42:04 +0000</pubDate>
      <link>https://dev.to/feya_shah_d38339cad4bf2ff/how-docker-works-internally-from-images-to-containers-1gnh</link>
      <guid>https://dev.to/feya_shah_d38339cad4bf2ff/how-docker-works-internally-from-images-to-containers-1gnh</guid>
      <description>&lt;p&gt;After working with containerized systems across several projects, I’ve seen how often the fundamentals are misunderstood. In this post, I break down Docker’s core architecture — images, containers, and what really happens under the hood.&lt;/p&gt;

&lt;p&gt;🧱 Whether you're building scalable microservices or just getting your CI/CD right, understanding these internals matters.&lt;/p&gt;

&lt;p&gt;👉 Read it here: &lt;a href="https://feyashah.com/how-docker-works-internally-from-images-to-containers/" rel="noopener noreferrer"&gt;https://feyashah.com/how-docker-works-internally-from-images-to-containers/&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Docker #DevOps #SoftwareEngineering #Containers #BackendDevelopment
&lt;/h1&gt;

</description>
      <category>devops</category>
      <category>docker</category>
      <category>backenddevelopment</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Docker Finally Made Sense to Me — Here’s How 🐳</title>
      <dc:creator>Feya Shah</dc:creator>
      <pubDate>Tue, 24 Jun 2025 11:25:43 +0000</pubDate>
      <link>https://dev.to/feya_shah_d38339cad4bf2ff/docker-finally-made-sense-to-me-heres-how-1nb7</link>
      <guid>https://dev.to/feya_shah_d38339cad4bf2ff/docker-finally-made-sense-to-me-heres-how-1nb7</guid>
      <description>&lt;p&gt;Docker used to feel like this confusing DevOps thing I had to copy-paste my way through.&lt;br&gt;
But once I took the time to actually learn it, it changed how I build, test, and ship code.&lt;/p&gt;

&lt;p&gt;In short:&lt;/p&gt;

&lt;p&gt;Docker packages your app and everything it needs into a container — so it works anywhere the same way.&lt;/p&gt;

&lt;p&gt;No more “works on my machine” drama.&lt;br&gt;
No more dependency hell across projects or team machines.&lt;/p&gt;

&lt;p&gt;🧠 If you’re a developer who still feels shaky about containers, I broke it all down simply:&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://feyashah.com/docker-explained-a-simple-overview-for-developers" rel="noopener noreferrer"&gt;Read the full breakdown&lt;/a&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
