<?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 Amaresh Pati on Medium]]></title>
        <description><![CDATA[Stories by Amaresh Pati on Medium]]></description>
        <link>https://medium.com/@amareshpati?source=rss-269f08352e58------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PEWrZIY3BGIbQfnN9m1hIg@2x.jpeg</url>
            <title>Stories by Amaresh Pati on Medium</title>
            <link>https://medium.com/@amareshpati?source=rss-269f08352e58------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:10:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amareshpati/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[Git Adventures — — Part 1: Five Developers, One Repo, and the “It Works on My Machine” Era]]></title>
            <link>https://amareshpati.medium.com/git-adventures-part-1-five-developers-one-repo-and-the-it-works-on-my-machine-era-61b41341a05a?source=rss-269f08352e58------2</link>
            <guid isPermaLink="false">https://medium.com/p/61b41341a05a</guid>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Amaresh Pati]]></dc:creator>
            <pubDate>Tue, 10 Mar 2026 04:51:01 GMT</pubDate>
            <atom:updated>2026-03-10T04:51:01.239Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1_m4y8_KzlVw_lTUZc3AA.png" /></figure><p>Every software project begins the same way.</p><p>Someone says, “Let’s build something amazing.”</p><p>Ten minutes later, someone asks:</p><blockquote>“Wait… who created the Git repo?”</blockquote><p>This is the story of a five-person development team starting their first project together.</p><p>Meet the team.</p><p>Virat — — The Repo Master Responsible for repositories and access control.</p><p>Amaresh — — The Architect designs the project structure and keeps the codebase organised.</p><p>Johnny, Danny, Ronaldo — — The Feature Crew: Three developers who will build features, write code, and occasionally break things.</p><p>Today is Day 1.</p><p>And the project begins with the most important step in any software project.</p><p>Creating the repository.</p><h3>Chapter 1 — — The Repo Is Born</h3><p>Virat opens his terminal and announces that the project officially begins.</p><pre>mkdir project-hyperdrive<br>cd project-hyperdrive</pre><p>Now he initialises Git.</p><pre>git init</pre><p>Git responds:</p><pre>Initialized empty Git repository</pre><p>Behind the scenes, something important just happened.</p><p>Git created a hidden folder called:</p><pre>.git</pre><p>This folder stores everything Git needs:</p><ul><li>commit history</li><li>branches</li><li>logs</li><li>references</li><li>repository metadata</li></ul><p>Without .gitthe folder is just a normal directory.</p><p>With .git It becomes a version-controlled project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hku259BuUSc3rCRs.png" /></figure><h3>Chapter 2 — — The Architect Builds the Foundation</h3><p>Virat turns to Amaresh.</p><p>The repository exists now, but a repository without files is like a city without buildings.</p><p>Amaresh prepares the initial project structure on his machine.</p><p>He checks what Git sees.</p><pre>git status</pre><p>Output:</p><pre>Untracked files:<br>README.md<br>src/<br>config/</pre><p>Git sees the files but does not track them automatically.</p><p>Developers must tell Git which files should be tracked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3vAiDoTbm4DqG3Z-.png" /></figure><h3>Chapter 3 — — Connecting the Two Worlds</h3><p>Virat created the repository on his machine, and Amaresh prepared the project on his laptop.</p><p>Johnny asks:</p><blockquote>“How are we working in the same repository?”</blockquote><p>Virat explains.</p><pre>Local Repository → developer machines<br>Remote Repository → shared server</pre><p>Virat connects his repository to the remote server.</p><pre>git remote add origin https://company-repo/project.git<br>git push -u origin main</pre><p>Amaresh connects his machine to the same repository.</p><pre>git remote add origin https://company-repo/project.git<br>git pull origin main</pre><p>Now both machines share the same Git history.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j0l7nvXRkizILmXT.png" /></figure><h3>Chapter 4 — — Teaching Git What to Remember</h3><p>Amaresh stages the project files.</p><pre>git add .</pre><p>The dot (.) means add everything inside the current directory.</p><p>Git workflow:</p><pre>Working Directory → Staging Area → Commit History</pre><p>Staging allows developers to choose which files should go into the next commit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lVmHZueVtnurBELF.png" /></figure><h3>Chapter 5 — — The First Commit</h3><p>Amaresh creates the first commit.</p><pre>git commit -m &quot;Initial project setup&quot;</pre><p>A commit is a snapshot of the project at a specific moment.</p><p>Each commit records:</p><ul><li>changes</li><li>author</li><li>time</li><li>commit message</li></ul><h3>Chapter 6 — — Sharing the Repo With the Team</h3><p>Virat grants repository access to the team.</p><p>Johnny clones the repository.</p><pre>git clone https://company-repo/project.git</pre><p>Danny checks the status.</p><pre>git status</pre><p>Output:</p><pre>On branch main<br>Your branch is up to date with origin/main</pre><p>Everyone is synchronised.</p><h3>Chapter 7 — — The Branching Rules</h3><p>The main The branch must always remain stable.</p><p>Developers create branches for their work.</p><h3>Feature</h3><pre>feat/login-system<br>feat/payment-module</pre><h3>Bugfix</h3><pre>bugfix/login-validation<br>bugfix/crash-on-start</pre><h3>Hotfix</h3><pre>hotfix/security-patch<br>hotfix/payment-crash</pre><h3>Chore</h3><pre>chore/update-dependencies</pre><h3>Docs</h3><pre>docs/setup-guide</pre><h3>Refactor</h3><pre>refactor/auth-module</pre><h3>Style</h3><pre>style/code-formatting</pre><h3>Test</h3><pre>test/auth-tests</pre><h3>Performance</h3><pre>perf/query-optimization</pre><h3>Release</h3><pre>release/v1.0</pre><p>Workflow:</p><pre>Create branch → Commit → Push → Pull Request → Review → Merge</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TJ0gFlzYFojLO6G_.png" /></figure><h3>Chapter 8 — — The Feature Crew Begins</h3><p>Amaresh assigns tasks.</p><p>Johnny:</p><pre>git checkout -b feat/authentication</pre><p>Danny:</p><pre>git checkout -b feat/profile-system</pre><p>Ronaldo:</p><pre>git checkout -b feat/service-integration</pre><p>Three developers.</p><p>Three branches.</p><p>One repository.</p><p>And somewhere in the future…</p><p>A merge conflict is waiting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1AHJ3_PqzeFii01C.png" /></figure><h3>End of Part 1</h3><p>What the team learned:</p><ul><li>git init</li><li>git status</li><li>git add</li><li>git commit</li><li>git remote</li><li>git push</li><li>git clone</li><li>git branch</li></ul><p>Branch naming examples:</p><pre>feat/<br>bugfix/<br>hotfix/<br>docs/<br>chore/<br>refactor/<br>style/<br>test/<br>perf/<br>release/</pre><h3>What Happens in Part 2</h3><p>In the next part, the team will learn:</p><ul><li>PR creation</li><li>git log</li><li>git diff</li><li>git show</li><li>git stash</li><li>resolving merge conflicts</li></ul><p>Follow the series for Part 2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1_m4y8_KzlVw_lTUZc3AA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61b41341a05a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tools AI Can’t Replace (And I use almost daily)]]></title>
            <link>https://amareshpati.medium.com/tools-ai-cant-replace-and-i-use-almost-daily-f284cb578a49?source=rss-269f08352e58------2</link>
            <guid isPermaLink="false">https://medium.com/p/f284cb578a49</guid>
            <dc:creator><![CDATA[Amaresh Pati]]></dc:creator>
            <pubDate>Tue, 17 Feb 2026 04:51:00 GMT</pubDate>
            <atom:updated>2026-02-17T04:51:00.801Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mtPl1GsEEYe8N9KHhE8CwA.png" /></figure><p>As developers, we keep discovering tools that quietly make our lives easier.</p><p>Not flashy. Not hyped. Just… effective.</p><p>These are three tools I keep coming back to because they <strong>remove friction from my workflow</strong>.</p><p>They save time, reduce mental load, and let me focus on building features instead of fighting setup, data, or formats.</p><h3>DummyJSON — An Instant Backend for Frontend Work</h3><p>🔗 <a href="https://dummyjson.com/">https://dummyjson.com</a></p><p>When I start working on a new feature, backend readiness is often the bottleneck.</p><p>DummyJSON removes that problem entirely.</p><p>It gives you ready-to-use REST APIs with realistic data — users, products, posts, todos, comments, and more — without any setup.</p><h3>Why it’s genuinely useful</h3><ul><li>Create <strong>custom APIs</strong> using your own JSON</li><li>Ready endpoints like /products, /users, /todos, /posts</li><li>Full HTTP support: GET, POST, PUT, PATCH, DELETE</li><li>Pagination, search, and filtering built in</li><li>Zero setup. Zero configuration.</li></ul><h3>How it helps me</h3><ul><li>I build UI and business logic without waiting on backend completion</li><li>I can test real-world scenarios like loading states and empty responses</li><li>No need to maintain mock servers or fake data generators</li></ul><p>Instead of guessing how data <em>might</em> look, I work with something close to production from day one.</p><h3>📨 DummyInbox — Clean Email Testing Without Noise</h3><p>🔗 <a href="https://dummyinbox.com/">https://dummyinbox.com</a></p><p>Testing email-based flows using your real inbox gets messy fast.</p><p>DummyInbox fixes this with the simplest possible approach.</p><p>You get disposable email addresses instantly — no signup, no login, no tracking.</p><h3>Why I keep using it</h3><ul><li>Instant temporary email addresses</li><li>Auto-expiring inboxes</li><li>No spam in personal or work email</li><li>Unlimited usage, completely free</li></ul><h3>Where it fits in my workflow</h3><ul><li>Testing signup and onboarding flows</li><li>Verifying OTPs and confirmation emails</li><li>QA testing notification and alert emails</li></ul><p>It does one job — and does it really well.</p><h3>🔍 JSON Crack — Making Sense of Messy JSON</h3><p>🔗 <a href="https://jsoncrack.com/editor">https://jsoncrack.com/editor</a></p><p>If you work with APIs, you <em>will</em> deal with large, deeply nested JSON responses.</p><p>JSON Crack turns that chaos into clarity.</p><p>Paste your JSON and instantly get a visual tree or graph of the structure.</p><h3>Features that actually matter</h3><ul><li>Interactive visualization of JSON structures</li><li>Supports JSON, YAML, CSV, XML, TOML</li><li>Built-in formatter and validator</li><li>Easy format conversion</li><li>Export visuals for documentation or sharing</li></ul><h3>How I use it in real life</h3><ul><li>Understand complex API responses copied from Postman</li><li>Debug unexpected nested fields quickly</li><li>Explain payload structures to teammates without long explanations</li></ul><p>Scrolling raw JSON is painful.</p><p>Visualizing it saves time and mental energy.</p><h3>🧠 Why These Tools Stick With Me</h3><p>ToolProblem SolvedReal ImpactDummyJSONBackend dependencyFaster frontend developmentDummyInboxEmail testing clutterClean QA, zero inbox pollutionJSON CrackJSON complexityFaster debugging &amp; understanding</p><p>They don’t replace thinking.</p><p>They <strong>remove unnecessary effort</strong> — and that’s exactly what good tools should do.</p><h3>👏 Shoutout Where It’s Due</h3><p>A big shoutout to <strong>Ovi</strong></p><p>👉 <a href="https://github.com/Ovi">https://github.com/Ovi</a></p><p>For building and maintaining <strong>DummyJSON</strong> and <strong>DummyInbox</strong>.</p><p>These tools are a great example of developer-first thinking:</p><ul><li>simple</li><li>reliable</li><li>and focused on real problems we face every day</li></ul><p>Open-source tools like these quietly power a lot of our workflows — and they deserve more appreciation.</p><h3>Final Note</h3><p>I’ve tried many productivity tools.</p><p>Most don’t survive daily usage.</p><p>These three did — because they solve real problems I face while building products.</p><p>No hype. Just utility.</p><p>If you’re a frontend, mobile, or full-stack developer, chances are these tools will quietly improve your workflow too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f284cb578a49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I Started Wrapping Everything in React Native ?]]></title>
            <link>https://amareshpati.medium.com/why-i-started-wrapping-everything-in-react-native-b29aca00acfe?source=rss-269f08352e58------2</link>
            <guid isPermaLink="false">https://medium.com/p/b29aca00acfe</guid>
            <dc:creator><![CDATA[Amaresh Pati]]></dc:creator>
            <pubDate>Thu, 05 Feb 2026 11:51:00 GMT</pubDate>
            <atom:updated>2026-02-05T11:51:00.874Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EcLFbpasNXrRLiYEeRk3xg.png" /></figure><h3>Why I Started Wrapping Everything in React Native ?</h3><p>I’ve been working with React Native for about 4 years now, and one thing I’ve learned the hard way is this:<br><strong>nothing stays permanent</strong>.</p><p>Libraries get deprecated.<br>Best practices change.<br>Things that were “recommended” last year suddenly feel wrong today.</p><p>At some point I started asking myself:</p><blockquote><strong><em>Why am I fixing the same problem again and again, just because a library changed?</em></strong></blockquote><h3>The Pattern I Kept Seeing</h3><p>Let’s be honest — React Native apps don’t die quickly.<br>They live for years.</p><p>But during that time:</p><ul><li>FlatList starts struggling with performance</li><li>FlashList shows up and becomes the new standard</li><li>SafeAreaView from react-native is no longer enough</li><li>We move to react-native-safe-area-context</li></ul><p>And suddenly you’re touching <strong>dozens of files</strong> for what is essentially <strong>one decision change</strong>.</p><p>That’s when I realized — <br><strong>the mistake was never the library choice, it was how tightly my app depended on it.</strong></p><h3>The Simple Rule I Follow Now</h3><blockquote><strong><em>Never use core or third-party components directly across the app.<br>Wrap them once. Own them.</em></strong></blockquote><p>I started creating a <strong>top layer of base components</strong>.</p><h3>Example 1: Lists (FlatList → FlashList)</h3><h3>What I stopped doing</h3><p>Using FlatList directly everywhere:</p><pre>import { FlatList } from &#39;react-native&#39;;</pre><p>Because I already know how this story ends.</p><h3>What I do instead: AppFlatList</h3><pre>// AppFlatList.tsx<br>import React from &#39;react&#39;;<br>import { FlatList, FlatListProps } from &#39;react-native&#39;;<br><br>export function AppFlatList&lt;T&gt;(props: FlatListProps&lt;T&gt;) {<br>  return (<br>    &lt;FlatList<br>      {...props}<br>      removeClippedSubviews<br>      windowSize={5}<br>      initialNumToRender={10}<br>    /&gt;<br>  );<br>}</pre><p>Usage stays simple:</p><pre>&lt;AppFlatList<br>  data={data}<br>  renderItem={renderItem}<br>  keyExtractor={(item) =&gt; item.id}<br>/&gt;</pre><p>Now when performance becomes an issue (and it will), I don’t panic.</p><h3>Later… switching to FlashList</h3><pre>// AppFlatList.tsx<br>import { FlashList, FlashListProps } from &#39;@shopify/flash-list&#39;;<br><br>export function AppFlatList&lt;T&gt;(props: FlashListProps&lt;T&gt;) {<br>  return &lt;FlashList {...props} estimatedItemSize={60} /&gt;;<br>}</pre><p>That’s it.</p><p>No screen changes.<br>No refactor weekends.<br>No stress.</p><h3>Example 2: Base Component Deprecation (SafeAreaView)</h3><p>This one hit me multiple times.</p><p>Earlier we all used:</p><pre>import { SafeAreaView } from &#39;react-native&#39;;</pre><p>Later we were told:</p><blockquote><em>“Use react-native-safe-area-context instead.”</em></blockquote><p>Now imagine SafeAreaView used <strong>everywhere</strong>.</p><p>Painful, right?</p><pre>// AppSafeAreaView.tsx<br>import React from &#39;react&#39;;<br>import { SafeAreaView } from &#39;react-native-safe-area-context&#39;;<br><br>export function AppSafeAreaView({ children, style }) {<br>  return (<br>    &lt;SafeAreaView style={[{ flex: 1 }, style]}&gt;<br>      {children}<br>    &lt;/SafeAreaView&gt;<br>  );<br>}</pre><p>Usage:</p><pre>&lt;AppSafeAreaView&gt;<br>  &lt;HomeScreen /&gt;<br>&lt;/AppSafeAreaView&gt;</pre><p>Now I don’t care:</p><ul><li>if API changes</li><li>if padding logic changes</li><li>if Android/iOS behavior differs later</li></ul><p>I’ve isolated it.</p><h3>This Slowly Became My Default Style</h3><p>Now I do this for almost everything:</p><ul><li>AppText → font scaling, typography updates</li><li>AppButton → design system changes</li><li>AppInput → validation, focus handling</li><li>AppImage → caching, placeholders</li><li>AppPressable → analytics hooks later</li></ul><p>Every time I hesitate and think</p><blockquote><em>“Should I just use this directly?”</em></blockquote><p>I remember how many times I’ve regretted that decision.</p><h3>Why This Matters (Real Talk)</h3><p>React Native evolves fast.<br>Your app doesn’t.</p><p>So either:</p><ul><li>you chase changes every year<br><strong>or</strong></li><li>you design your app to absorb them calmly</li></ul><p>Wrapping components doesn’t slow you down.<br><strong>Refactoring later does.</strong></p><h3>Final Thought</h3><p>This isn’t about over-engineering.<br>It’s about respecting the fact that <strong>change is guaranteed</strong>.</p><blockquote><em>I don’t wrap components because I expect problems today.<br>I wrap them because I know future-me will be tired.</em></blockquote><p>And honestly?<br>Future-me deserves better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b29aca00acfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>