<?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 Priyabrata Naskar on Medium]]></title>
        <description><![CDATA[Stories by Priyabrata Naskar on Medium]]></description>
        <link>https://medium.com/@priyabrata-naskar?source=rss-89e260570bb2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*67K60GulyDfVa_HX</url>
            <title>Stories by Priyabrata Naskar on Medium</title>
            <link>https://medium.com/@priyabrata-naskar?source=rss-89e260570bb2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:17:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@priyabrata-naskar/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[AI is Making You Dumber — Or Is It?]]></title>
            <link>https://priyabrata-naskar.medium.com/ai-is-making-you-dumber-or-is-it-ba21102b9fe8?source=rss-89e260570bb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba21102b9fe8</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[android-development]]></category>
            <category><![CDATA[androiddev]]></category>
            <dc:creator><![CDATA[Priyabrata Naskar]]></dc:creator>
            <pubDate>Sun, 02 Mar 2025 13:16:58 GMT</pubDate>
            <atom:updated>2025-04-19T18:43:08.442Z</atom:updated>
            <content:encoded><![CDATA[<h3>AI is Making You Dumber - or Making you a Productive Developer?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mbdhXiFgcG8kC-4njZprkw.jpeg" /></figure><p>Move fast. Ship code. Or slow down. Understand deeply.</p><p>Which one makes you a better engineer?</p><blockquote>When I first started coding, experienced developers warned me: “Don’t just copy-paste from Stack Overflow — understand what you’re using.” Back then, even if you copied code, you still had to figure out where to place it and how to make it work within your system.</blockquote><p>Fast forward to today — AI makes that process even easier. Feed it some context, and it writes entire functions, fixes bugs, and refactors your code in seconds. Copy-pasting is practically effortless now.</p><p>But here’s the catch: If you only rely on AI to code fast, are you truly learning?</p><p>At the same time, going deep — truly understanding algorithms, system design, and architectural decisions — takes time. It feels slow. Yet, this depth is what separates great engineers from those who just assemble code.</p><p>Looks Contradictory, Right?</p><p>The best engineers don’t choose between speed and depth. They master both.</p><p>But in an AI-driven world, how do we strike the right balance?</p><p>Let’s break it down.</p><h4>The Power of Speed 🚀</h4><p>In software development, moving fast has immense value:</p><ul><li>Rapidly iterating on ideas</li><li>Shipping features and getting real user feedback</li><li>Debugging and fixing issues swiftly</li></ul><blockquote>In the past, developers copied code from Stack Overflow — sometimes without fully understanding it. Today, AI tools like ChatGPT and Copilot take this a step further, generating entire functions, auto-completing code, and even optimizing performance instantly.</blockquote><p>But here’s the problem: 🚨 Speed without understanding is risky. If you don’t know why something works, you won’t know how to fix it when it breaks.</p><p>Blind reliance on AI — just like blind copy-pasting from Stack Overflow — can lead to fragile, unmaintainable code. That’s where slow thinking comes in.</p><h4>Thinking Beyond the Code 🧠</h4><p>Deep understanding takes time. Mastering algorithms, design patterns, and architecture requires deliberate effort.</p><p>This depth is what separates great engineers from those who just put pieces together. If you’ve ever:</p><blockquote>— Spent hours debugging a tricky issue, only to have a breakthrough moment</blockquote><blockquote>— Dove into internals to optimize performance</blockquote><blockquote>— Refactored code to be more elegant after truly understanding the problem</blockquote><blockquote>— you’ve engaged in slow thinking.</blockquote><p>The challenge? S<strong>low thinking doesn’t give instant gratification</strong>. But the engineers who invest in deep learning ultimately move faster in the long run — because they build a solid foundation.</p><h4>The Bridge Between Fast and Slow Thinking 🤖</h4><p>AI isn’t just a tool for writing code faster — it can also help us learn deeply.</p><p>It can:</p><ul><li><strong>Speed up execution</strong> — AI-generated code, auto-completions, and instant debugging.</li><li><strong>Enable deeper learning </strong>— Breaking down complex concepts, explaining solutions step by step.</li></ul><p>Instead of using AI just to code faster, use it to think better:</p><blockquote>➡️ Need to iterate quickly? Let AI generate boilerplate code and move fast.</blockquote><blockquote>➡️ Want to truly understand an algorithm? Ask AI to explain it like a mentor would.</blockquote><p>AI isn’t just a shortcut for productivity — it’s a tool for mastering both fast and slow thinking.</p><h4>🔑 Real Skill:</h4><p>At its core, software engineering isn’t about memorizing syntax or even writing perfect code. It’s about problem-solving.</p><p>And the best engineers? They aren’t just great coders. They’re great learners.</p><p>Mastering both fast and slow thinking makes you a better learner:</p><ul><li>Be curious enough to go deep.</li><li>Be action-oriented enough to move fast.</li></ul><p>This mindset will future-proof your career. Technology will change. AI will evolve. <strong>But the ability to learn how to learn?</strong> That will always be your biggest advantage.</p><h4>⚖ Final Thoughts️</h4><p>So, how do you balance thinking fast and thinking slow?</p><ul><li>Know when to move fast. When shipping features, debugging, or iterating — bias for action.</li><li>Know when to slow down. When learning new concepts, designing systems, or debugging complex issues — go deep.</li><li>Use AI as a tool for both. Speed up execution while also deepening your understanding.</li></ul><p>At the end of the day, <strong>engineering is both an art and a science</strong>. The best engineers don’t just write code — they think.</p><p>What do you think? Do you struggle more with moving fast or going deep? How do you balance them in your work?</p><p>If you liked the article💌, please let me know by pressing on the clap👏 button below. Feel free to follow me on <a href="https://www.linkedin.com/in/priyabrata-naskar">LinkedIn</a>. ❣️</p><p>P.S. You can clap 50 times on Medium! Just long press that little icon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba21102b9fe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why ViewStub Improves App Performance | Android Interview Question | ViewStub Internals]]></title>
            <link>https://priyabrata-naskar.medium.com/view-stub-internals-deep-dive-into-android-c252af1f4015?source=rss-89e260570bb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c252af1f4015</guid>
            <category><![CDATA[android-development]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[androiddev]]></category>
            <dc:creator><![CDATA[Priyabrata Naskar]]></dc:creator>
            <pubDate>Sun, 17 Mar 2024 05:44:48 GMT</pubDate>
            <atom:updated>2024-03-27T03:25:36.923Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*0PMZpUbBpZsvFe3PI5n75w.png" /><figcaption>Magical Box aka ViewStub</figcaption></figure><p>Did you ever get a use case where you have a rarely used view? So, you’ve decided to keep the visibility of view <strong>GONE</strong> and <em>set visibility</em> to <strong>VISIBLE</strong> on specific cases. Here, inflating the view i.e. <strong>loading the layout resource</strong> every time for a rarely view, is redundant. Can we improve the performance? But, improving performance is boring. So let’s have an interesting story.</p><p>Okay! Let’s imagine you have 2 magical boxes. One box can hide itself and when you call it, it brings out a toy.🧸 Let’s call it “<strong>Include</strong>”.</p><p>The other box is special. Because it can turn invisible and when it does, it brings out a surprise toy from inside it! It doesn’t show anything until we tell it to. Let’s call it “<strong>ViewStub</strong>”.🪄</p><p>When we decide it’s time to show something, like a new toy,🚂 we make the ViewStub visible. When it becomes visible, it magically brings out a special toy from inside it. This special toy is a drawing🌇 or a picture that we’ve made before and stored inside the ViewStub.</p><p>Now, instead of calling it a “toy,” let’s call it “<strong>layout resource.</strong>” It’s like a picture we want to show on the screen. And the ViewStub is like a special hiding place for these pictures.</p><p>When we want to show a <strong>view or bunch of views</strong> from the ViewStub, we just say, “Hey ViewStub, it’s time to show us what you’ve got!” And it brings out the picture for us to see.</p><p><strong>But here’s the cool part:</strong> We can also decide what type of <strong>view</strong> we want to show later. We can tell the <strong>ViewStub</strong>, “Hey, next time you show us something, make sure it’s this specific picture.” So, when it decides to show us something, it picks that specific picture🚂 we asked for.</p><h3>What is ViewStub?</h3><p>Android Documentation says: “ViewStub is an <strong>invisible</strong>, <strong>zero-sized View</strong> that can be used to <strong>lazily inflate</strong> layout resources at runtime.”</p><p>Let’s see how we can use ViewStub:</p><p>First, in XML, we declare the UI:</p><pre>&lt;ViewStub android:id=&quot;@+id/banner_stub&quot;<br>android:inflatedId=&quot;@+id/banner&quot;<br>android:layout=&quot;@layout/layout_banner&quot;<br>android:layout_width=&quot;120dip&quot;<br>android:layout_height=&quot;40dip&quot; /&gt;</pre><ul><li><strong>id</strong>: ViewStub defined can be found using the id “banner_stub”.</li><li><strong>inflatedId:</strong> This attribute is used to set the id of the inflated View. Once the view is inflated using the layout “layout_banner” can be found using “banner”. We can set it programmatically by using the <strong>setInflatedId()</strong> method.</li><li><strong>layout:</strong> This attribute is used to supply an identifier for the layout resource to inflate. We can set it programmatically by using <strong>setLayoutResource(int)</strong> method.</li></ul><pre>//declare<br>var stub: ViewStub? = null<br><br>//initialize in onCreate()<br>stub = findViewById(R.id.banner_stub)<br>val inflatedView: View = stub?.inflate()</pre><h3>How ViewStub work internally?</h3><ol><li>ViewStub itself is a zero-sized view. It’s dumb &amp; lightweight. Let’s deep-dive into the source code of ViewStub Class.</li></ol><pre>/***<br>** A Simplified Version for explanation<br>***/<br>public ViewStub(Context context, AttributeSet attrs, int defStyleAttr, int defStyleRes) {<br>  super(context);<br>  mInflatedId = a.getResourceId(R.styleable.ViewStub_inflatedId, NO_ID);<br>  mLayoutResource = a.getResourceId(R.styleable.ViewStub_layout, 0);<br>  mID = a.getResourceId(R.styleable.ViewStub_id, NO_ID);<br>  a.recycle();<br>  setVisibility(GONE);<br>  setWillNotDraw(true);<br>}</pre><ul><li>In its constructor, we can see, that its visibility is set to <strong>GONE</strong> and setWillNotDraw flag is also enabled.</li></ul><p>2. Once we <strong>inflate</strong> the ViewStub or set its visibility to <strong>VISIBLE</strong> or <strong>INVISIBLE</strong>, the layout resource is inflated. Before inflation ViewStub exists in the view hierarchy, helping to maintain a <strong>flat view tree</strong>.</p><p>3. Once ViewStub is <strong>inflated</strong>, it replaces itself in its parent with an inflated view or views. Let’s see how this happens under the hood.</p><pre>/***<br>** A Simplified Version of inflate() method which returns the view<br>***/<br><br>//access parent view<br>final ViewParent viewParent = getParent();<br>if (viewParent != null &amp;&amp; viewParent instanceof ViewGroup)<br>final ViewGroup parent = (ViewGroup) viewParent;<br>   <br>   //this inflates the view with layout resource that was previously <br>   //set by setLayoutResource() and returns inflated view<br>    final View view = inflateViewNoAdd(parent);<br>    <br>    //here&#39;s the most interesting part where viewstub replaces itself with it&#39;s parent<br>    replaceSelfWithView(view, parent);<br>    mInflatedViewRef = new WeakReference&lt;&gt;(view);<br><br>   mInflateListener.onInflate(this, view);<br>     return view;<br>   }<br>}</pre><p>Now let’s have a look into the setVisibility method of ViewStub. This method also inflates the view in case visibility is passed as <strong>VISIBLE</strong> or <strong>INVISIBLE</strong></p><pre>/***<br>** A Simplified Version of setVisibility(int) method<br>***/<br><br>if (mInflatedViewRef != null) {<br>//in case view is already inflated and present<br>//in view hierarchy just update visibility<br> View view = mInflatedViewRef.get();<br>  if (view != null) {<br>   view.setVisibility(visibility);<br>   }<br><br> } else {<br>   super.setVisibility(visibility);<br>    if (visibility == VISIBLE || visibility == INVISIBLE) {<br>     //here&#39;s the actual magic happends where <br>     //we&#39;re calling inflate() internally<br>     inflate();<br>     }<br>  }<br>}</pre><h3>Why to use ViewStub?</h3><ul><li>When there is a complex view that you want to render occasionally, viewstub is the way to go. ViewStub will <strong>reduce memory usage</strong> and speed up UI rendering by loading the views at runtime only when they are needed.</li><li>When you want to inflate the view lazily at runtime or based on some UI logic.</li><li>ViewStub will help you keep the <strong>View Hierarchy flat</strong> when the actual layout is not in use.</li></ul><p>If you liked the article💌, please let me know by pressing on the clap👏 button below. Feel free to follow me on <a href="http://www.linkedin.com/in/priyabrata-naskar">LinkedIn</a>. ❣️</p><p>P.S. You can clap 50 times on Medium! Just long press that little icon.</p><p>What next do you want me to write ✍️ on?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c252af1f4015" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview Experience Zomato | SDE 1 | Android]]></title>
            <link>https://priyabrata-naskar.medium.com/interview-experience-zomato-sde-1-android-4bbdca38dc2a?source=rss-89e260570bb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bbdca38dc2a</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[android-development]]></category>
            <dc:creator><![CDATA[Priyabrata Naskar]]></dc:creator>
            <pubDate>Sun, 18 Feb 2024 13:06:21 GMT</pubDate>
            <atom:updated>2025-12-27T05:06:24.412Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Zomato Interview Experience | SDE" src="https://cdn-images-1.medium.com/max/1024/1*UMz7Mq142riGvYLaNQxg9Q.png" /><figcaption>Zomato Interview Experience</figcaption></figure><blockquote>Picture this: You’re scrolling through LinkedIn, casually browsing your network updates, when suddenly, a message pops up. It’s not just any message; it’s an invitation into the world of Zomato, where culinary delights meet cutting-edge technology. This is the beginning of my journey through the Zomato interview process — an experience I’m excited to share with you. 💫</blockquote><ul><li><strong>Application Process:</strong> Zomato hires through referral only. I received a DM over LinkedIn regarding the opening, igniting the spark that would lead me through the doors of one of the most innovative tech companies in the culinary sphere. With a simple exchange of resumes, the stage was set for what would become a memorable adventure.</li><li><strong>Phone Call Screening:</strong> A week after initiating contact📱, had a conversation with EM over the call. He shared about the interview process. From probing questions about my current role to a nuanced exploration of my experiences, this screening process was converted into the first round of interviews.</li><li><strong>First Round:</strong> This round was focused on Android fundamentals as my experience was mostly in Android Domain. The interviewer wasted no time in delving into topics ranging from <strong>Coroutines Internals </strong>to<strong> Performance Optimisation</strong>. We discussed different topics like <strong>Activity Lifecycle</strong>, <strong>RecyclerView</strong>, <strong>Views,</strong> <strong>View Model Internal </strong>&amp; its working, and other important topics related to Android. Then he slightly moved towards <strong>App Performance </strong>and<strong> </strong>other optimation stuff around Android. After android discussions, the interviewer asked about a DSA question to test problem-solving ability. He asked me to explain about the approach. Then he extended that question &amp; asked for further solution.</li><li><strong>Second Round:</strong> In this round, the Interviewer started with <strong>Mobile System Design📱</strong>. He asked me to design a small feature of the Zomato Application. Then he asked some questions on <strong>Coroutines</strong> and <strong>Threads</strong>. He asked me to implement some design patterns. After System design, he shared a Leetcode Medium problem and asked me to write ✍️ the solution on Google Docs.</li><li><strong>Third Round:</strong> The Hiring Manager round was scheduled after a couple of weeks of the 2nd round. This round is to set the expectations and discuss compensation and location.</li></ul><p>After 2 days I received the offer letter 💌. If you liked the article, please let me know by pressing on the clap button below. Feel free to follow me on <a href="https://www.linkedin.com/in/priyabrata-naskar">LinkedIn</a>.</p><p>I’ve curated a list of high paying start-ups to help you streamline your job search process : <a href="https://1kstartup.com/">https://1kstartup.com</a></p><p>P.S. You can clap 50 times on Medium! Just long press that little icon.</p><p>What next you want me to write ✍️ on?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bbdca38dc2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>