<?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 Mohd Sohail Ansari on Medium]]></title>
        <description><![CDATA[Stories by Mohd Sohail Ansari on Medium]]></description>
        <link>https://medium.com/@thecodephilic-guy?source=rss-666f3fa16809------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tnZZH0Y9-A3TkqZI2dUeJA.jpeg</url>
            <title>Stories by Mohd Sohail Ansari on Medium</title>
            <link>https://medium.com/@thecodephilic-guy?source=rss-666f3fa16809------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:55:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thecodephilic-guy/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[Why is React So Popular Among Devs?]]></title>
            <link>https://thecodephilic-guy.medium.com/why-is-react-so-popular-among-devs-0f6ff86066bd?source=rss-666f3fa16809------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f6ff86066bd</guid>
            <category><![CDATA[dom]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[virtual-dom]]></category>
            <dc:creator><![CDATA[Mohd Sohail Ansari]]></dc:creator>
            <pubDate>Fri, 19 Sep 2025 16:13:30 GMT</pubDate>
            <atom:updated>2025-09-19T16:13:30.744Z</atom:updated>
            <content:encoded><![CDATA[<p>Long ago… (okay, not that long ago), we — well not me, but the devs of that time, used to write plain Vanilla JavaScript. (Fancy name, but it just means “no frameworks, just pure JS”).</p><p>The whole idea in frontend development is simple: update the DOM (Document Object Model). Think of the DOM as a big tree that keeps track of all the HTML elements on a page.</p><p>Now, here’s the catch. Updating that DOM back then was like asking your grandpa to run a marathon. Every time you removed or added something, the browser would repaint the entire DOM. Results…? Laggy websites, slow updates, and frustrated users.</p><h3><strong>Fast forward to 2013</strong></h3><p>The devs at Facebook publically dropped something magical: <strong>React</strong>!!</p><p>React didn’t make websites beautiful (that’s CSS), nor did it make websites smart (that’s backend). What it did was something way more important, it made updating the DOM fast. Like really fast.</p><p>And this speed? That’s one of the biggest reasons why React is still ruling the frontend world.</p><h4><strong>The Secret Sauce: Virtual DOM</strong></h4><p>Here’s how React pulled it off:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*bnjU7FVq0f2LcND3.png" /></figure><p>‣ React creates a Virtual DOM, basically a copy of the real DOM, but much lighter.</p><p>‣ When something changes (like a new button appears), React updates this Virtual DOM first.</p><p>‣ Then it compares the Virtual DOM with the Real DOM using a process called diffing.</p><p>‣ Finally, it updates only the parts that changed, instead of repainting the whole tree.</p><p>So instead of repainting the entire house when one bulb goes out, React just changes that one bulb. Efficient, right?</p><p><strong>But wait, there’s more…</strong></p><p>DOM speed isn’t the only reason devs love React. A few more reasons why React became everyone’s favorite:</p><blockquote><strong>1. Component-based architecture</strong></blockquote><p>Build small, reusable Lego-like pieces of UI and combine them. Makes code cleaner, easier, and reusable.</p><blockquote><strong>2. JSX (yes, the “</strong><a href="https://lnkd.in/p/gH5ayfRC"><strong>HTML inside JS</strong></a><strong>” thing 👀)</strong></blockquote><p>Looks like HTML, but it’s actually JavaScript. Makes writing UI code less painful and more readable.</p><blockquote><strong>3. Huge ecosystem + community</strong></blockquote><p>Need a calendar component? A chart? A toast notification? Someone already built it. Just npm install and boom!</p><blockquote><strong>4. Backed by Facebook + Big Tech adoption</strong></blockquote><p>When giants like Facebook, Instagram, Netflix, and Airbnb are using it, people feel safe betting on it.</p><h4>Conclusion</h4><p>React became popular because it solved a real problem: slow DOM updates. Add to that its component-based structure, JSX, and massive ecosystem, and it’s no surprise devs still flock to it.</p><p>So next time someone asks, “Why React?” you can simply say</p><p><strong><em>“Because it makes websites faster, easier, and prettier to build.”</em></strong></p><p>Thanks for reading! If you made it this far, you’re awesome.</p><p>PS: If I got something wrong, feel free to correct me in the comments (because hey, we’re all learning here)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0f6ff86066bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Interview Experience at an early-stage Startup — What I Learned, Mistakes I Made, and Tips for…]]></title>
            <link>https://thecodephilic-guy.medium.com/my-interview-experience-at-an-early-stage-startup-what-i-learned-mistakes-i-made-and-tips-for-f0418eca88de?source=rss-666f3fa16809------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0418eca88de</guid>
            <category><![CDATA[interview-experience]]></category>
            <category><![CDATA[dos-and-donts]]></category>
            <category><![CDATA[early-stage-startup]]></category>
            <category><![CDATA[interview-tips]]></category>
            <category><![CDATA[django]]></category>
            <dc:creator><![CDATA[Mohd Sohail Ansari]]></dc:creator>
            <pubDate>Tue, 17 Jun 2025 14:06:45 GMT</pubDate>
            <atom:updated>2025-06-17T14:06:45.627Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Interview Experience at an early-stage Startup — What I Learned, Mistakes I Made, and Tips for You</h3><p>I don’t know why I didn’t write about this experience earlier, but here it is — my interview story at <strong>Ume App</strong> for a <strong>Backend Developer (Django)</strong> role.</p><h3>How it Started</h3><p>About two months ago, I applied for a backend role at Ume App (Startup). It was a Django-based API development position. To be honest, Django isn’t my primary stack — but I applied anyway, thinking <em>“Let’s see what happens!”</em></p><p>Surprisingly, I got a response within 24 hours. They asked me to solve an assessment (pretty common these days). I completed and submitted it within the given timeframe. A few days later, I got invited to the <strong>technical interview </strong>(smooth, isn’t it?)</p><h3>The Interview Experience</h3><p><strong>Duration:</strong> Exactly 1 hour (the meeting ended automatically with a timer — quite neat!).</p><p>Here’s how it went:</p><ol><li><strong>Introduction</strong></li></ol><p>The interviewer introduced himself — <strong>Utkarshar</strong>, with 2+ years of experience in full-stack development (Next.js, React, Django).</p><p>Then I introduced myself — a 3rd-year Computer Science student with a backend focus (APIs, databases, etc.). I casually mentioned photography as a hobby.</p><p><strong>2. The Hobby Funnel 😄</strong></p><p>He asked: “What camera do you use for photography?”</p><p>I said: “Just my phone.”</p><p>“Which one?”</p><p>“Realme 7.”</p><p>“What’s the aperture?”</p><p>“f/1.8.”</p><p><em>He smiled,</em> “1.8 is good. Let’s begin with the tech now…”</p><p>That’s when I knew this was going to get real! 😂</p><p>Despite Django not being my primary stack, I managed to complete the assessment earlier. (Yes, I “vibe-coded” it — don’t do this. More on that later.)</p><h3>What Was Asked?</h3><p>Here’s a breakdown of what the interview covered:</p><ol><li><strong>Technical Questions</strong> (Django, MVT lifecycle, middlewares, CORS, signals, etc.)</li><li><strong>Easy DSA Problem</strong> (finding duplicates in a JSON array)</li><li><strong>Database Questions</strong> (like ACID properties, source of truth)</li><li><strong>Assessment Extension</strong> (add new features or logic)</li><li><strong>Wrap-up Discussion</strong></li></ol><p>If you’re curious about exact questions or want advice on any section — feel free to leave a comment!</p><h3>✅ Do’s and ❌ Don’ts — Based on My Experience</h3><h4>✅ Do’s:</h4><ol><li><strong>Be confident</strong> — It’s better to calmly admit what you don’t know than to fumble through guesses.</li><li><strong>Prepare fundamentals</strong> — Know the basics of the tech stack you’ve applied for.</li><li><strong>Understand your past work</strong> — Be ready to explain your previous projects in depth.</li><li><strong>Practice DSA</strong> — At least cover easy-level questions (especially array/string problems).</li><li><strong>Know your tools</strong> — If you mention using Docker, Git, Postman, etc., be ready to show it.</li><li><strong>Be honest about your experience</strong> — If something isn’t your strong suit, let them know upfront (like I did with Django).</li><li><strong>Ask clarifying questions</strong> — If a problem or question is unclear, it’s okay to ask for more details.</li></ol><h4>❌ Don’ts:</h4><ol><li><strong>Don’t lie or fake knowledge</strong> — Interviewers can sense it quickly.</li><li><strong>Don’t rely on AI tools</strong> — I was asked to turn off GitHub Copilot as soon as I opened VS Code.</li><li><strong>Don’t vibe code</strong> — Especially during prep. If you’re serious, code with structure and intent.</li><li><strong>Don’t break eye contact</strong> — Especially during online interviews. It shows nervousness or disinterest.</li><li><strong>Don’t skip DBMS theory</strong> — Questions on ACID, transactions, and consistency models often come up.</li><li><strong>Don’t assume Stack Overflow/ChatGPT can save you during an interview</strong> — Use them to learn, not copy.</li></ol><h3>My Key Learnings</h3><ul><li><strong>Stick to your strengths:</strong> Apply for roles aligned with your expertise — unless you’re prepared to put in extra effort to learn.</li><li><strong>Deep-dive into your stack:</strong> Learn the internals. Django isn’t just about views and models; it’s about signals, middlewares, deployment, CORS, and more.</li><li><strong>Don’t misuse AI tools while learning:</strong> They can become a crutch rather than a ladder.</li><li><strong>Be interview-ready:</strong> Even for early-stage startups, the technical depth can be impressive.</li><li><strong>Talk about what you know, not what you memorized.</strong></li><li><strong>Stay calm:</strong> Pressure is part of the game. How you handle it is what really sets you apart.</li></ul><h3>Final Thoughts</h3><p>It’s been a while since this interview happened, and I may have missed a few small details — but I hope this blog gives you a solid idea of how interviews at early-stage startups can go.</p><p><strong>If you found this post helpful, feel free to share it with your fellow devs.</strong></p><p>Got any questions or want to connect? Drop a comment or DM me on <a href="https://www.linkedin.com/in/sohail-ansari-19435b269/">LinkedIn</a>.</p><p>Also, if you’re into photography, we might just vibe! Say “Hi” on Instagram: <a href="https://www.instagram.com/thephotophilic_guy">@thephotophilic_guy</a></p><p>Thanks for reading!</p><p>— — — — — — — — — —</p><p><strong>Mohd Sohail Ansari</strong></p><p>Backend Developer | Tech Explorer | Hobbyist Photographer</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0418eca88de" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>