<?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 Zarana Desai on Medium]]></title>
        <description><![CDATA[Stories by Zarana Desai on Medium]]></description>
        <link>https://medium.com/@zarana-desai?source=rss-701035c0acdc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ltZRzLJ3SPiGhNzBZzxKXg.jpeg</url>
            <title>Stories by Zarana Desai on Medium</title>
            <link>https://medium.com/@zarana-desai?source=rss-701035c0acdc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:24:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zarana-desai/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[Code Reviews That Actually Improve Code (Not Egos)]]></title>
            <link>https://medium.com/@zarana-desai/code-reviews-that-actually-improve-code-not-egos-c7011003fc22?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7011003fc22</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Fri, 02 Jan 2026 15:34:40 GMT</pubDate>
            <atom:updated>2026-01-02T15:34:40.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y2c83umWZIc5KX65NRTvuQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@disruptxn?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Desola Lanre-Ologun</a> on <a href="https://unsplash.com/photos/person-using-black-and-red-acer-laptop-computer-on-table-YgOCJz9uGMk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>A console statement made it to production. Along with it, an internal API field — never meant for the UI — quietly slipped through. No crashes. No alerts. Just wrong behavior in plain sight.</p><p>Let’s ask this: <strong>what would have made this impossible to ship?</strong></p><p>Is this a tooling failure? To some extent.</p><p>A simple MR checklist item like:</p><blockquote>“Any temporary or debug code left behind?”</blockquote><p>would have caught it.</p><p>Even better, the pipeline should have failed. An ESLint rule banning console.log outside of development would have stopped the change before a human ever looked at it.</p><p>But let’s pause here.</p><p>Tooling didn’t approve the request. A reviewer did. Which leads to a more important question: <strong>How was the MR approved?</strong></p><p>The code passed tests. The diff looked reasonable. Nothing screamed “broken.” And that’s exactly the problem.</p><p>The review thread explodes over things like:</p><ul><li>❌ “Can you rename hasApproved to isApproved?”</li><li>❌ “This ternary is hard to read; please refactor to an if.”</li><li>❌ “Please alphabetize these imports.”</li></ul><p>Don’t get me wrong — these are important considerations. They improve readability, consistency, and long-term maintainability. But they are <strong>hygiene checks, not correctness checks</strong>.</p><p>In this case, attention went to polishing surface-level details while a contract breach slipped through unnoticed — because no one paused to question whether that boundary should exist at all.</p><p>A reviewer’s job is <em>not</em> to make the code prettier <em>first</em>. It is to answer these questions, but not limited to:</p><ol><li>Is the behavior correct? Are the boundaries/contracts respected?</li><li>Is any existing behaviour subtly altered?</li><li>Is this logic in the right layer?</li><li><em>Then</em>, is it readable, idiomatic, and consistent?</li></ol><p>When step 4 crowds out steps 1–3, bugs slip through despite<strong> “thorough” </strong>reviews. Code reviews are not lint checks, and they’re definitely not ego boosters disguised as helpful feedback.</p><h3>Ego in Code Reviews (Even When You’re Trying to Be Helpful)</h3><p>Ego in code reviews isn’t always loud or hostile. Often, it hides behind politeness and “helpful” comments.</p><h4>The Comfort of Style Feedback</h4><p>Style-related comments are appealing because they’re easy to make and hard to dispute:</p><ul><li>They’re quick to spot</li><li>They rarely require deep context</li><li>They don’t challenge ownership or intent</li><li>They almost never make the reviewer feel wrong</li></ul><p>High-impact questions — like <em>“Could this logic break if the API or data shape changes?”</em> — are harder. They require slowing down, understanding ownership, and sometimes risking an uncomfortable conversation.</p><p>It’s much easier to default to low-risk feedback and tell ourselves we were being helpful.</p><h4>How Ego Sneaks In (Quietly)</h4><p>Ego can also show up in subtler ways, even with good intentions:</p><ul><li>Correcting minor style differences instead of focusing on behavior</li><li>Over-explaining things everyone already understands</li><li>Treating reviews as a performance or authority check</li><li>Assuming our way of writing is the “right” way</li></ul><p>The tricky part is that most of us do this unconsciously. The key is to notice it, pause, and ask:</p><blockquote>Am I commenting to make the code safer, or to make myself feel right?</blockquote><p>Focusing on the former keeps reviews productive, ego-free, and genuinely valuable to the team.</p><h3>The Cost of Missing the Real Question</h3><p>The most costly bugs aren’t the ones that crash immediately. They’re the ones that quietly do the wrong thing.</p><p>The team debated the naming of a new structure in a merge request. A few changes later, something unrelated fails. Confidence erodes. Debugging takes longer. And by then, no one remembers which MR introduced the issue — because at the time, everything looked fine and the review felt thorough.</p><p>That’s the real cost: not a single bad change, but a codebase that slowly becomes harder to trust.</p><h3>When Not to Comment</h3><p>Not every difference needs to be corrected. Silence can be a sign of good judgment.</p><p>You can skip commenting when:</p><ul><li>It’s a harmless style preference</li><li>Formatting will be handled by tooling</li><li>The change doesn’t affect behavior, ownership, or boundaries</li></ul><p>The next time you open a merge request to review, try this: before commenting on style, ask yourself what could quietly go wrong here. If you find something, say it. If not, maybe that rename can wait. Because the most dangerous bugs are the ones that look fine during review.</p><h3>The Time I Let the UI Do Too Much — and a Reviewer Caught It</h3><p>In one of my very first projects, I made what felt like a harmless decision. We needed to display a simple count in the UI. Instead of having the backend return the number, I returned a list of IDs and let the UI calculate the count.</p><p>My reasoning was simple: <em>maybe we’d need those IDs later to show a list.</em></p><p>Along with those IDs came additional metadata — data that was never meant to leave the backend. Nothing broke, and the UI worked exactly as expected.</p><p>But a boundary had already been crossed.</p><p>Luckily, the issue was caught in code review. My reviewer asked a simple, high-impact question:</p><blockquote>“Should the UI really be responsible for this count, or should the backend provide it?”</blockquote><p>Tests had passed, the UI looked correct, and nothing was broken. But in hindsight, it <em>could have been</em> a big problem if it had shipped to production.</p><p>Back then, I wouldn’t have shared this story — I felt like it was a huge blunder as soon as I saw the review comment. In retrospect, it was a design decision that crossed a layer it shouldn’t have, exactly the kind of thing good code reviews are meant to catch.</p><h3>A Reviewer’s Mental Checklist (Ego-Free)</h3><p>Before commenting, ask yourself this:</p><ul><li>Am I reducing risk, or just expressing preference?</li><li>Would this comment matter if I weren’t the reviewer?</li><li>If I were to leave only one comment, which one would matter most?</li><li>Does this comment help the code, or my sense of correctness?</li></ul><p>That last one hits hard.</p><p>So far, we’ve looked at how reviewers can miss critical issues. But responsibility isn’t one-sided — authors can also unintentionally block important feedback.</p><h3>“My Baby” Syndrome (When Authors Stop Hearing Feedback)</h3><p>Ego in code reviews doesn’t belong only to reviewers. It shows up on the author side too — often more quietly, and often more defensively. There’s a subtle mindset shift that happens once we’ve spent enough time on a piece of code:</p><p><em>I wrote this. I understand it. Therefore, it must be right.</em></p><p>That’s “my baby” syndrome. Like a parent with their child, it’s hard to believe something you’ve nurtured could be wrong.</p><p>The code feels familiar. The trade-offs feel justified. Every line has a story behind it. So when feedback comes in, it can feel less like a question about the code — and more like a challenge to our judgment.</p><h4>How It Shows Up</h4><p>“My baby” syndrome rarely looks like outright refusal. It shows up as:</p><ul><li>Defending decisions before fully understanding the comment</li><li>Explaining <em>why</em> something was done instead of reconsidering <em>whether</em> it should exist</li><li>Treating suggestions as misunderstandings rather than signals</li><li>Needing extra proof before questioning our own assumptions</li></ul><p>None of this comes from bad intent. When you’ve lived inside a change for days, it’s hard to see it the way a reviewer does — as an isolated change rather than accumulated reasoning.</p><h4>Why It’s Dangerous</h4><p>This mindset is especially risky because:</p><ul><li>The code often <em>does</em> work</li><li>Tests often <em>do</em> pass</li><li>The author often <em>does</em> know the system well</li></ul><p>Which makes it easy to dismiss feedback that targets boundaries, contracts, or future risk — the very things reviews are meant to protect.</p><p>The result isn’t loud conflict. It’s quiet resistance.</p><h4>How to Counter It (As an Author)</h4><p>Familiar code feels correct — sometimes, too correct. To avoid missing real issues:</p><ul><li>Treat every comment as a signal, not a verdict</li><li>Ask yourself: <em>“If I hadn’t written this, would this concern still matter?”</em></li><li>Separate explaining intent from evaluating impact</li><li>Remember: reviewers don’t see your mental model — only your code</li></ul><p>Good reviewers challenge assumptions. Good authors let them.</p><p>Code reviews succeed or fail as a system. Reviewers need to look past what’s easy to comment on. Authors need to stay open to concerns that challenge familiar decisions. When both happen, reviews catch the mistakes that matter.</p><p>When they don’t, the code still “looks fine” — until it isn’t.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7011003fc22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Role Integrity: Showing Up the Way Your Work Title Says You Can]]></title>
            <link>https://medium.com/@zarana-desai/role-integrity-showing-up-the-way-your-work-title-says-you-can-6a8b2e4cabca?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a8b2e4cabca</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[upskilling]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Sat, 22 Nov 2025 09:34:29 GMT</pubDate>
            <atom:updated>2025-11-22T09:34:29.607Z</atom:updated>
            <content:encoded><![CDATA[<p>Every role comes with a certain expectation — not the HR checklist kind, but the unspoken “this is who you are at work now” kind. And every now and then, in the middle of all the growing and upskilling that you do, you might drift a little away from the expectation. Not on purpose — it just happens. You get comfortable with one part of the job, you avoid the parts that feel “too big,” or you quietly let others take the lead, even though <em>you</em> have the title that says you should. I’ve definitely had days where I’m spending my time on work that isn’t as complex or high-impact as my role usually expects. And days where I know I should be taking charge… but I’m just vibing in the background instead.</p><p>And that pattern shows up in other moments, too. I caught myself doing this recently — during some upskilling time, I somehow gravitated straight back to backend, even though frontend is where I genuinely needed the practice.</p><p>Noticing that pattern made something click for me. That’s where this idea of role integrity comes in.</p><p>I’m not talking about hiding behind a job description or saying “that’s not my job” every time something unexpected shows up. I mean the exact opposite, actually. I’m talking about <strong>showing up the way your title says you can</strong> — the way people expect you to.</p><p>When people talk about “staying true to your title,” they often imagine some rigid, boxy interpretation of work:<br><em>“These are my responsibilities, these are yours, and I’m not crossing any line.”</em></p><p>But that’s not what role integrity is about — at all.</p><p>There’s a huge difference between <strong>growing in alignment with your title</strong> and <strong>avoiding anything that feels uncomfortable under the excuse of your title</strong>.</p><h3>🌱 Title-Aligned Growth (the good kind)</h3><p>Let’s start with the good side of this — title-aligned growth.<br>To me, it’s basically when you let your job title nudge you in the right direction. Not pressure you, not box you in… just guide your growth a little. Your title becomes a reminder of what you <em>can</em> do, not just what you’ve already mastered.</p><p>And that shows up in small, everyday ways.</p><h3>✔️ If you’re a full-stack engineer…</h3><p>It doesn’t mean you must be a pro in every layer, but it <em>does</em> mean you should be willing to touch them.</p><ul><li>If your front-end skills are weaker, you still try.</li><li>If a bit of DevOps is needed, you give it a shot or collaborate closely.</li><li>If a system architecture decision comes up, you contribute your perspective.</li></ul><p>Your title says you can handle the full stack — so lean into that identity, even if one part is “your favorite.”</p><h3>✔️ If you’re a senior engineer…</h3><ul><li>You step in and guide when things get unclear.</li><li>You mentor without being asked.</li><li>You think beyond just tickets.</li><li>You raise risks early, propose solutions, not problems.</li></ul><p>Being senior doesn’t just mean more years or harder tasks — it’s a mindset, a presence. To me, the clearest sign of a senior presence is when people naturally follow your lead — without you having to ask for it.</p><h3>🧱 Title-Aligned Avoidance (the bad kind)</h3><p>Now, on the flip side, there’s title-aligned avoidance. This is when your job title becomes more of a shield than a guide. You stick to the parts you already feel confident in and quietly avoid anything that might stretch you, challenge you, or expose a gap you don’t want to look at yet.</p><p>You know what this looks like:</p><h3>❌ “I’m developing the frontend, so I’m not touching the API development at all.”</h3><p>Translation: <em>I don’t want to look unprepared.</em><br>But avoiding it completely limits your own versatility and your team’s agility.</p><h3>❌ “I’m not DevOps, so I won’t even try to understand the deployment pipeline.”</h3><p>Translation: <em>I’m choosing comfort over growth.</em><br>But understanding DevOps generally makes you a better engineer, period.</p><p>People sometimes push back on this idea with the classic “jack of all trades, master of none” line. And sure — being stretched too thin is real. Nobody is saying your role should turn you into a Swiss Army knife who’s mediocre at everything and excellent at nothing. If you’re a database developer, I’m not asking you to write me a React Component (I’m not stopping you either🙂). But to grow, you need to stay open to the parts of your role you <em>should</em> touch.</p><p>The point is: <strong>avoidance isn’t specialization.</strong><br>Avoidance is just… avoiding. And over time, it keeps you safe but also stuck, slowly creating a mismatch between your title and how you actually show up.</p><p>So yeah — that’s my whole take on role integrity.<br>Not “stay in your lane,” not “only do what’s written on a piece of paper,” but simply: <em>show up the way your title says you can. </em>A little more ownership, a little more courage, a little less hiding. That’s really all it comes down to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a8b2e4cabca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The view from here: A rookie coder’s log]]></title>
            <link>https://medium.com/@zarana-desai/the-view-from-here-a-rookie-coders-log-b3546f903982?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3546f903982</guid>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Thu, 14 Aug 2025 17:04:52 GMT</pubDate>
            <atom:updated>2025-08-14T17:04:52.338Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Perpetual Rookie, By Choice</strong></h3><p>Right now, my “view” is a blend of two worlds — one window shows code I’m confident in, the other is a frantic search — <em>the</em> <em>best way to handle rearrangement of data on the front-end and persist the changes at the back-end</em>. The coffee is lukewarm, the to-do list is growing, and the feeling is oddly familiar: I’m a rookie.</p><p>Not a rookie, as in “just started coding” — I’ve been at this for over eight years (yes, I started coding in the ninth grade). Rookie, because tech changes faster than I can ever keep up with. Every time I learn something, a new tool or idea comes along, and it feels like I’m back to square one... And that’s the thrill. This log is my attempt to capture that view — with equal parts confidence, challenge, and curiosity.</p><h3>The Mindset That Ages Well</h3><p>The longer I code, the more I realize:</p><ul><li><strong>Being a “pro” is knowing you’ll never know it all.</strong> The pace at which tech is advancing makes me realize that we’re all permanent students. Today’s <em>cutting-edge</em> <em>technology </em>could be history in the next month. You either accept yourself as a lifelong learner, or be a goner.</li><li><strong>Old patterns adapt.</strong> Experience teaches me <em>how</em> to learn, not just <em>what</em> to learn. An issue that had been bugging a colleague of mine for hours was solved by a senior within 2 minutes, <em>literally. </em>My first thought? “Yeah, she’s a Principal Engineer, she’d know things we don’t.” But why? When I asked her how she knew this, her answer was — “I faced this problem once in the past”. Well, there you go. Now I know this too, and when I face it again, I’ll know what to do. Someone once told me — <em>Count your experience in the number of mistakes you made or the number of problems you solved. Not in the number of years you’ve worked</em>.</li><li><strong>Questions are currency.</strong> The better I get at asking questions, the closer I will be to solving problems. More often than not, I’ve thought to myself, “This question is silly. If you’ve thought of this question, so did your seniors, and already incorporated a solution to this”. Sometimes, the questions turn out to be <em>not-so-silly </em>after all :)</li></ul><h3>Tiny Victories, Big Fuel</h3><p>In this ever-refreshing race, small wins sometimes seem huge:</p><ul><li>Finally making sense of a new code-flow that looked like complete gibberish last week. Now I know where this var is<em> actually</em> being initialized!</li><li>Seeing a feature work the way I wanted, that too, with the cleanest and fastest code I’ve ever written.</li><li>Fixing a bug in minutes that would’ve eaten up my whole day a few months ago.</li></ul><p>These wins remind me: I’m still learning, sure, but I’m not starting from zero. All those years of figuring stuff out do add up. And honestly, it’s these tiny moments that make the late nights and head-scratching worth it. They’re like quiet high-fives to myself — proof that I’m moving forward, even if it’s one small win at a time.</p><h3>My Survival Kit for the Ever-Changing Dev World</h3><p>The rookie mindset isn’t a weakness — it’s a survival skill. It’s what will keep me from becoming obsolete. A few things that make this continuous rookie life easier:</p><ul><li><strong>Version control:</strong> For when you realize “yesterday’s code” was actually smarter than “today’s code.” Commit! Commit! Commit!</li><li><strong>Note-taking:</strong> Future Me doesn’t deserve breadcrumbs, but a whole damn feast.</li><li><strong>Healthy skepticism:</strong> Just because it’s “the latest” doesn’t mean it’s “the greatest.”</li></ul><p><em>(These tips work for Gen-Z situationships, too! )</em></p><h3>The Messy Middle Nobody Talks About</h3><p>There are days when the learning curve feels more like a learning wall.</p><ul><li>Impostor syndrome? Still visits. It’s quieter now, but it’s there. The difference now is, I take it as a sign that I’m pushing myself into new territory — and that’s where the real growth happens.</li><li>Overwhelm? Oh yes. Every time I see “Top 10 Tools You <strong>Need</strong> to Learn This Year,” I need to remind myself I don’t have to learn them <em>all right now.</em></li><li>Burnout? Been there. Learned the hard way that pacing myself matters way more than trying to prove I can do it all (Pace &gt;&gt;&gt;&gt; Pride ).</li></ul><h3>The Road Is the Goal</h3><p>My roadmap isn’t about becoming “an expert in everything” (as much as I’d like to, sometimes). It’s about:</p><ul><li><strong>Keep learning on purpose.</strong> Not just because I have to, but because it keeps the work interesting and makes me curious about what else I could try.</li><li><strong>Pick my battles.</strong> Not every shiny new tool is worth my time — I focus on the ones that help me, and I’m okay letting the rest pass me by, for now.</li><li><strong>Grow the skills that last.</strong> Things like problem-solving and communication only get stronger the more I use them, and they’ll still matter no matter how much the tech world changes.</li></ul><p>The rookie’s journey is infinite, and that’s the point. The goal isn’t to finish, it’s to keep moving forward. Some days, I’ll be the one asking the “silly” questions. Other days, I’ll be the one with the quick, two-minute fix that surprises someone else. Both roles are valuable. Both mean I’m still in the game.</p><p>If you ask me where I see myself in five years, I hope my answer is: “Still a rookie. Just a better one.” And if that means more late nights, more lukewarm coffee, and more little high-fives to myself — I’m in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3546f903982" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vibe Coding: Fun for Hacks, Risky for Production]]></title>
            <link>https://medium.com/@zarana-desai/vibe-coding-fun-for-hacks-risky-for-production-008f9de73e93?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/008f9de73e93</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Sun, 27 Apr 2025 17:52:45 GMT</pubDate>
            <atom:updated>2025-04-27T17:52:45.603Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever found yourself refactoring code by simply chatting with AI — asking it to clean up a function with too many parameters or reduce its cognitive complexity? Feels like magic when it works. You type a quick prompt, and voilà — a solution is delivered, and the code is refactored in seconds.</p><p>Now, while this may seem like a casual use of AI, <strong>this isn’t quite what I’d call vibe coding</strong>. Not all AI-assisted coding is vibe coding.</p><h3>What is Vibe Coding?</h3><p>A little while ago, Andrej Karpathy casually dropped a tweet and gave a name to something many of us had been doing without realizing: <strong>vibe coding</strong>.</p><blockquote>There’s a new kind of coding I call “vibe coding”, where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It’s possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. I ask for the dumbest things like “decrease the padding on the sidebar by half” because I’m too lazy to find it. I “Accept All” always, I don’t read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I’d have to really read through it for a while. Sometimes the LLMs can’t fix a bug so I just work around it or ask for random changes until it goes away. It’s not too bad for throwaway weekend projects, but still quite amusing. I’m building a project or webapp, but it’s not really coding — I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.</blockquote><p><strong>Vibe coding</strong> is when you let the AI fully take the wheel. You throw prompts at it, accept whatever it spits out, barely glance at the diffs, and somehow — somehow — it just works. You’re not reviewing. You’re not questioning. You’re just vibing.</p><p>But here’s the catch: this is great for quick fixes and small projects.<br>When it comes to production-ready code, though? Relying too heavily on AI can be… well, let’s just say <em>spicy</em>. AI can help you refactor — but you can’t just let it take over without fully understanding what’s happening under the hood.</p><h3>My Little Vibe Coding Experiment</h3><p>I actually unknowingly vibe coded once — before I even heard the term. I was trying to test if clicking on a section of a pie chart could filter values on a data grid. Instead of writing the code myself, I started throwing random prompts at the AI. Every time it gave me code, I pasted it in without even blinking. No reading, no verifying. Just pure “vibe, feel, build.” And it worked!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SUlF_Rg013tWAVYM452QHA.png" /></figure><p>But why did I approach it this way? Was it because I was rushing to meet a deadline? Or was I just doing it for fun?<br>Neither, actually. Sure, using LLMs purely for the joy of seeing them work their magic is pretty cool — it’s a fun way to appreciate how far technology has come. But letting AI handle everything just to meet a production deadline? That’s dangerous territory.<br>The real reason I did it was simple: I wanted to verify if my idea could even be built. I was testing possibilities, not building a final product. At no point did I consider deploying that code anywhere close to production.</p><h3>Vibe Coding vs Responsible AI-Assisted Coding</h3><p>This is super important: <strong>Not all AI-assisted coding is vibe coding.</strong></p><p>When I asked AI to help refactor a method because SonarQube warned me there were too many parameters — that wasn’t vibe coding.<br>I reviewed the output. I understood what it was doing. I thought about the consequences.</p><p>That’s using AI as a tool. A teammate. <strong>Vibe coding</strong> is different — it’s when you stop caring about what’s actually happening and just ride the wave. You can be serious about your code and still use AI responsibly. You can vibe — but you better be watching the vibes carefully when you’re working on something real.</p><h3>When Vibe Coding Can Become Dangerous</h3><p>But here’s the thing — Bring that same chaotic energy into your production backend, and things start to fall apart.</p><ul><li>Silent bugs sneak in.</li><li>Security holes you didn’t think to check get deployed.</li><li>Technical debt piles up before you even realize it.</li></ul><p>Production software needs engineers, not just vibes. It needs people who think, question, review, and optimize. Because when users are depending on your service, you don’t get to say, <em>“Oops, I was just vibing, bro.”</em></p><h3>It’s “Vibe, Feel, Build” — Not “Design, Engineer, Optimize”</h3><p>When you’re vibe coding, you’re not meticulously architecting systems or optimizing every little thing. You’re just <em>vibing</em> — throwing prompts at the AI, watching what comes out, and rolling with it.</p><p>And honestly? That’s perfectly fine — <strong>as long as you know that’s the game you’re playing</strong>. The important part is being aware of which mode you’re in.<br>If you’re hacking together a quick prototype, experimenting for fun, or building a weekend project — vibe away!</p><p>But if you’re shipping code to production, working on something that people will actually use and rely on — then it’s time to slow down, read every line, and think like an engineer again.</p><p>That brings me to something important: <strong>using AI to help you code isn’t a sin. </strong>You shouldn’t feel guilty for accepting a smart suggestion or for letting AI handle the boring boilerplate. In fact, that’s exactly what it’s good at — taking some of the grunt work off your plate so you can focus on the interesting parts.</p><p>Now, when AI does a lot of the heavy lifting, it’s natural to wonder:<br><strong>“Am I still a coder?” </strong>The answer is: absolutely, yes. You’re still the one asking the right questions, setting the direction, validating the answers, and stitching everything together. Coding isn’t just about typing syntax — it’s about solving problems, making decisions, and building things that work. Whether you write every character yourself or collaborate with an AI, <strong>you’re still a coder</strong>. You’re just coding smarter.</p><p>That said, here’s the thing:<br>We need to ask ourselves — <strong>is this the future, or are we cutting corners? </strong>When AI is doing so much of the work, are we pushing the boundaries of what’s possible with technology, or are we simply taking the easier, faster path at the cost of quality and craftsmanship?</p><p>Just remember: <strong>AI should be your co-pilot, not your autopilot.</strong><br>You’re still the one flying the plane.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=008f9de73e93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fear of the Unknown: How I Learned to Lean Into It]]></title>
            <link>https://medium.com/@zarana-desai/fear-of-the-unknown-how-i-learned-to-lean-into-it-fde767d9d11e?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/fde767d9d11e</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Sun, 02 Mar 2025 18:40:09 GMT</pubDate>
            <atom:updated>2025-03-02T18:40:09.506Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oPbUyHIAVjO-fG-MrOl7Pg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sickhews?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Wes Hicks</a> on <a href="https://unsplash.com/photos/foggy-gray-concrete-road-rsBVnIf7WDE?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>“Growth happens outside your comfort zone” — something I often hear. But, stepping into the unknown has always been daunting for someone like me, who has been a bit of a pampered kid. I feared unwanted outcomes, the possibility of failure, and the discomfort that came with trying something new. However, over time, I’ve realized that fear isn’t necessarily a bad thing. In fact, it’s often a sign that I’m on the verge of something meaningful.</p><p>Stepping into the unknown can feel terrifying. I’ve faced this fear multiple times, especially when exploring new domains in my work where I had no prior experience. When I first encountered a completely unfamiliar area at work, it felt like stepping into my own version of Area 51. Thoughts like <em>“What if I fail?”</em> and <em>“What if I look incompetent?”</em> clouded my mind. The fear of not knowing enough or making mistakes felt overwhelming. But then, I remembered a simple rule I believe in: <strong>Do what makes you nervous.</strong></p><p>Instead of seeing fear as a roadblock, I started looking at it like a compass.</p><p><em>Why does this make me nervous?</em> → Because it’s new and challenging.</p><p><em>What’s the worst that can happen?</em> → I might fail. I will know what <strong>couldn’t </strong>and <strong>didn’t </strong>work. I’ll move on to the next challenge.</p><p><em>What’s the best that can happen?</em> → I’ll gain new skills, confidence, and opportunities.</p><p>Fear and excitement are two sides of the same coin. The thing that you fear is also the same thing that can make you better. Rather than trying to master everything at once, I decided to:</p><ul><li><strong>Learn from others: </strong>This is one rare piece of advice that I think can work in almost every issue you ever encounter. <em>Are you facing a runtime error in your code?</em> Hundreds of people on Stack Overflow have already solved it for you. <em>Confused about filing taxes?</em> Your elder cousin has been there, suffered through it, and is ready to pass on their wisdom (or at least their CA’s number). <em>Trying to impress a date?</em> Someone on Reddit has already done the trial and error — copy the smoothest move and hope for the best. In my case, we already had a couple of subject matter experts in the organization who were wholeheartedly willing to help. Additionally, I had an enthusiastic and extremely curious teammate, from whom I learned to be confident in my skin and ask questions about everything.</li><li><strong>Embrace trial and error: </strong>Instead of fearing mistakes, I started seeing them as feedback. Every error pointed me toward what didn’t work, helping me refine my approach. The faster I failed, the faster I learned, and soon, the things that once seemed impossible started making sense.</li><li><strong>Build Confidence Through Action: </strong>The more I engaged with the new domain, the more comfortable I became. At first, everything felt foreign, but by taking small steps each day, I slowly built confidence. Repetition turned confusion into clarity, and what once felt intimidating became something I could tell you while I’m sleepy. <em>Action — not endless overthinking — is the best cure for self-doubt: </em>I remember reading this somewhere (not in the exact words, though).</li></ul><p>Expect discomfort, but don’t run from it. Take small and imperfect steps, you’ll at least get somewhere. Small, imperfect steps are always better than waiting for the perfect moment (because spoiler alert: it never comes). Trust that you’ll figure it out. Think about everything you once didn’t know — riding a bike, trigonometry, moving on from a breakup. At some point, all of it was <em>unknown</em> to you. And yet, you figured it out. If you’ve done it before, you can do it again.</p><p>The best things happen in the unknown. So, the next time you feel nervous about something new, don’t let it stop you. Let it guide you. Because on the other side of fear? That’s where the good stuff is. The question now is: <strong>“The Unknown is Calling. Are You Ready to Answer?”</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fde767d9d11e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[To feature-flag, or to not feature-flag]]></title>
            <link>https://medium.com/@zarana-desai/to-feature-flag-or-to-not-feature-flag-4fa3d03a5359?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fa3d03a5359</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[releases]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Sun, 19 May 2024 09:23:42 GMT</pubDate>
            <atom:updated>2024-05-19T09:24:44.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Y1-cj5Y0q3kwaWP4" /><figcaption>Photo by <a href="https://unsplash.com/photos/black-flat-screen-computer-monitor-cYyqhdbJ9TI">Radowan Nakif Rehan</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>Feature flags are like the Swiss Army knife of software development — handy, versatile, but also a bit mysterious. This brings me to ask: “To feature-flag or not to feature-flag, that is the deployment question”, not unlike Hamlet, when he says, “To be or not to be, is the question”, pondering his existence. But what exactly are feature flags, and how can they transform the way we deploy code?</p><p>Feature flags are conditional statements in the code that determine whether a feature is enabled or disabled. Feature flags are typically implemented using if-else statements, configuration files, or environment variables. They allow developers to control the visibility and behavior of features in real-time without changing code. Are feature flags the same as feature toggles?</p><p>With what little experience I have in the area of deployments and releases, I understand that feature flags and toggles may not be used interchangeably. A toggle implies that something can have two states: on and off. A feature toggle, therefore, is binary, which is often not the case with feature flags.</p><p><em>The Feature Flagging Odyssey</em></p><p>Imagine this: you’re on the brink of releasing a groundbreaking new feature to your users. But what if something goes wrong? Enter feature toggles and flags — the superheroes of the coding world. With a simple toggle, you can control the visibility of your new feature, gradually roll it out to different user segments, and quickly revert back if needed. It’s like having a safety net for your code, ensuring smooth sailing even in the face of uncertainty.</p><p><em>The Dark Side of the Flag</em></p><p>But beware, for with great power comes great responsibility. Feature flags, while incredibly useful, can also become a double-edged sword if not wielded carefully. Too many flags scattered across your codebase can lead to confusion and complexity, hindering rather than enhancing your development process. It’s essential to strike the right balance and adopt best practices for managing feature flags effectively.</p><p><em>Finding Harmony in the Flagverse</em></p><p>So, how can we make the most of feature flags without succumbing to their pitfalls? The key lies in thoughtful planning, clear communication, and continuous iteration. By establishing clear guidelines for when and how to use feature flags, collaborating closely with stakeholders, and soliciting feedback from users, we can harness the full potential of feature flags while mitigating their risks.</p><p><em>Empowering Innovation with Feature Flags</em></p><p>Feature flags are all about being flexible and trying new things. By using feature flags, teams can develop software step-by-step, testing changes quickly and safely. By embracing feature flags, teams can adopt a more iterative and data-driven approach to development, enabling rapid experimentation, A/B testing, and gradual feature rollouts.</p><p><em>Conclusion</em></p><p>Whether you’re a seasoned developer or just starting out on your coding journey, feature flags offer a powerful tool for navigating the complexities of modern development. So, to feature-flag or not to feature-flag? The choice is yours, and with the right approach, it can lead to a more innovative and resilient software development journey.</p><p><em>Questions to ponder:</em></p><p>1. How long should feature flags remain in your code?</p><p>2. Is feature-toggling an effective rollback strategy?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fa3d03a5359" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Human Side of Tech]]></title>
            <link>https://medium.com/@zarana-desai/the-human-side-of-tech-dcd4ebaa3c4?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcd4ebaa3c4</guid>
            <category><![CDATA[solutions]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Sat, 05 Aug 2023 18:08:58 GMT</pubDate>
            <atom:updated>2023-08-08T11:33:13.506Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QM4AIEtMb0Z9Wj2TqLV1Tw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@ikukevk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kevin Ku</a> on <a href="https://unsplash.com/photos/w7ZyuGYNpRQ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Beyond lines of code and intricate algorithms lies the essence of technology — its potential to empower and enrich humanity. In a world where technology knows no bounds, it consistently defies the status quo, forever reinventing itself. While technological advancements have brought immense benefits, they have also raised important questions about the human side of tech.</p><p>The “human side of tech” refers to the aspect of technology that focuses on its impact on individuals, society, and human experiences. I place our interactions with the digital realm under the human element of technology and how it fosters our emotions, actions, and associations. More often than not, this part is overlooked.</p><p>The human side of tech encompasses any ethical implications of innovations, emotional impact, digital well-being, user experience, human-computer interaction, and many more aspects that are not immediately apparent to me due to my limited experience in the field.</p><p><strong>Ethical Challenges</strong></p><p>Making appropriate ethical considerations before moving forward with any decision is quite fundamental. We may not know it, but we do subconsciously calculate the ethical implications of our actions (at least some of us). This practice, when applied in designing or developing solutions, ensures that technology empowers a user, rather than manipulating or influencing them. Some of the key ethical considerations are ensuring a user’s privacy and protecting their data, avoiding any algorithmic bias, preventing digital manipulation, and most important of them all — the environmental impact. If you think that as a developer your actions don’t really affect the environment, trust me, you’re not alone. I was under the same misconception before I read this: <a href="https://www.ibm.com/blog/green-coding/">https://www.ibm.com/blog/green-coding/</a></p><p><strong>Emotional Impact and Digital Wellbeing</strong></p><p>Technology has the power to evoke emotions in us — joy, excitement, frustration, and even anxiety. Designing for emotional impact requires understanding users’ emotional needs, motivations, and pain points. Addressing potential negative emotional impacts, such as privacy concerns or intrusive notifications, is crucial to avoid user dissatisfaction and potential technology rejection. As technology becomes increasingly pervasive in our lives, it is crucial to ensure that it enhances, rather than hinders, our overall well-being. Ultimately, the emotional impact of technology plays a significant role in shaping user experiences and can profoundly influence how users perceive and interact with digital products and services.</p><p><strong>User Experience</strong></p><p>User experience revolves around how users interact with the technology and perceive it. It goes beyond mere functionality to encompass the emotional, cognitive, and behavioral responses that users have during their digital interactions. The empathy-driven design ensures that technology resonates with users on a deeper level, making them feel understood and valued. Inclusivity must be the foremost concern of UX designers today, as people become more woke. Inclusive UX design ensures that all users, regardless of their abilities or characteristics, can interact with technology effectively and have a positive experience.</p><p><strong>Following a people-first approach</strong></p><p>A people-first approach in the human side of tech prioritizes the needs, values, and well-being of individuals over technological advancements or profit-driven motives. A people-first approach involves understanding users’ perspectives through user research, empathy-driven design, and continuous feedback loops. It ensures that technology is accessible, inclusive, and respectful of diverse user backgrounds and abilities. Now this does not mean you wait idly by and wait for the users to come to tell you what they want through feedback. According to a piece in The Wall Street Journal, “Customers can’t describe the experience they want to have, let alone begin to imagine what they expect in the future.” The people-first approach differs slightly in this case. That’s quite a broad topic and possibly requires writing a dedicated article on it.</p><p>If you’ve read some of my work, you probably know that I like to end with questions and not statements. “Did the chicken come first or the egg?” — is too clichéd. Let me ask you this — does the world continue to innovate as technology continues to evolve, or does the technology continue to evolve as the world continues to innovate?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcd4ebaa3c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I would learn to code (if I could start over)]]></title>
            <link>https://medium.com/@zarana-desai/how-i-would-learn-to-code-if-i-could-start-over-8fc3fb46271e?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fc3fb46271e</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Thu, 08 Jun 2023 17:11:36 GMT</pubDate>
            <atom:updated>2023-06-08T17:11:36.139Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/675/0*iizxZlt7I5JQLmAs" /><figcaption><em>Joan Gamell/Unsplash</em></figcaption></figure><p>I’ve been coding for over 8 years now, enjoyably so. Whenever I’ve been asked, “How do I begin my journey in coding?”, and believe it or not, I’ve been asked this more times than you can think, I have a different answer every time. Every. Single. Time. Now that’s not because I’m biased toward my friends and give others arbitrary advice, or I am just completely whimsical to give inconsistent suggestions, but because every learner has been at a different stage when they’ve asked me this question.</p><p>I begin to imagine how I would respond to it, if my 15-year-old self asked me this question today, considering all the experience and learning I have accumulated over the years. I have done a few things right (some by choice, and some by sheer luck) and there are things that I would like to change. I write this article as an answer to this question.</p><p>I was in 8th grade when I started coding for the first time. I hadn’t voluntarily opted to code, nor was I into it at first. I started my journey of coding with C. I hadn’t done this by choice, and if you ask me today, I’d say this was just the way it was — neither right nor wrong (I’ll justify this later). A year later, I began learning Java, and before you ask me why not C++, let me tell you I had no choice in the matter as Java was a part of my curriculum, and I could not afford to learn two languages at once. Two years later, I began learning C++. Elaborating on my previous statement, that having C as the first coding language to learn was neither right nor wrong because had I learned Java before C, I’d have had the same problem-solving skills developed. However, learning C first helped me grasp low-level concepts quite smoothly, without having to worry a lot about syntax.</p><p>Something that I would have liked to go differently is that before beginning with Java, C++ would have been a better choice as it is a natural progression from C, and C -&gt; C++ -&gt; Java would have been a better transition from procedural programming to object-oriented programming.</p><p>Coming to the language I learned after Java, the one that has become my favorite, is Python. I would love Python like it is my only biological child, in a house full of stepchildren. Many people would think that Python is a good first programming language for beginners, but I believe that you can only truly value Python and its plethora of features after you’ve been with C and Java. Another way of looking at it is that C, C++, and Java use { } (curly brackets) to separate blocks of code which can be easily understandable to newbies, while Python’s M.O. is indenting blocks of code, which can be overwhelming. Moreover, Python is quite a dynamic type of language when it comes to variables, whereas C, C++, and Java are static. Having to make correct type declarations would only prove beneficial in the learning process, and you won’t be shielded from any errors if you fail to do so.</p><p>Once I’d learned the basics of one coding language, learning other languages was a cakewalk. Once you understand fundamental programming concepts such as variables, control structures (e.g., loops, conditionals), functions, and data types, transferring that knowledge to another language becomes more straightforward. Once you become comfortable with one language’s syntax, learning the syntax of another language becomes less challenging.</p><p>Various sources would have helped me learn these coding languages. Numerous coding languages have thriving communities and extensive learning materials. These valuable resources, including tutorials, documentation, and online forums, offer ample guidance and support for individuals seeking to acquire a new programming language. Taking advantage of these existing resources can facilitate the learning journey and make it more manageable.</p><p>However, only watching videos, or going through books is not the way to go. Getting hands-on practice is the key. Moreover, if we explore a little more, and do more than just what is asked of us, we learn better. For example, if I’m asked to print a statement “HELLO WORLD!” using Python, I would try playing around with this question. I would try printing this string along with an integer. You’ll see it gives me an error, and I’ll have to convert the integer to a string before printing. However, no such error is thrown when I try to do the same thing in Java.</p><p>So now that I’ve learned coding the right way (that suits me), what do I do next? Only checking whether a string is a Palindrome is not going to help me solve real-world problems (at least not directly). Once I’ve been thorough with my concepts of coding, I would try implementing them to solve a comparatively complex problem. Say, I’m generating a program to decide what I’m supposed to wear every day. Now this is a real-world problem since I’m very indecisive when it comes to picking out clothes. So I come up with a solution that builds a random outfit for me daily. Now, to make it a bit more complex, I add functionality where the top and bottom of the outfit go together and are not completely random. Taking the complexity level further, I can add a functionality to only suggest outfits using clothes that are in my wardrobe and have not gone to the laundry. Furthermore, if I don’t like wearing black on Saturdays, that can be taken into account as well.</p><p>Here’s how I would learn to code if I could start over. Remember that learning to code is a continuous journey, and there are always new things to explore and learn. My coding journey didn’t stop at Python, and I explored more languages, frameworks, and libraries for more complex solutions in programming (let’s talk about that in another article). Enjoy the process, be persistent, and never stop learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fc3fb46271e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Placements: The benefit of hindsight]]></title>
            <link>https://medium.com/@zarana-desai/placements-the-benefit-of-hindsight-6cf84cbbc4c6?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cf84cbbc4c6</guid>
            <category><![CDATA[freshers]]></category>
            <category><![CDATA[placement]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[students]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Sun, 27 Nov 2022 17:08:55 GMT</pubDate>
            <atom:updated>2022-11-27T17:08:55.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*0TwPlXvcQaLde6Sh.png" /><figcaption>Source: <a href="https://teresas.ac.in/placement/">https://teresas.ac.in/placement/</a></figcaption></figure><p>I’m sure every engineering student will relate to the fact that they’ve been hearing <strong>“Start preparing for placements today itself!” </strong>practically since the first day they stepped into college. Well, nowadays, even the parents of engineering aspirants are quite aware and they always have a question about the placement statistics of an institution where they’re enrolling their ward.</p><p>Personally, “placements” — the word itself was associated with fear and apprehension. Keyword — <em>was. </em>Today, I cannot think of any better experience. Truly, preparing for placements requires you to be extremely disciplined, determined and rigorous, but I’ve often noticed students add an extra ingredient to the process — <strong>stress.</strong></p><p>I’ve often been asked this question by my juniors, as to when they should start preparing for placements, and I still haven’t figured out the answer to this. Honestly, I never actually started <em>preparing</em>. I have been solving programming problems online as far as my memories of engineering go. The intention was not to <em>prepare</em> for placements, but to improve my problem-solving skills. I wouldn’t want to promote any specific platform, but I remember getting my hands dirty on all of them. I occasionally surfed the internet to rummage through websites that provide you content like <strong>Top 100 questions asked in engineering interviews for freshers </strong>or something. Surprisingly, most of the questions were those that I would study for my semester exams. I had no idea what the fuss was about. On second thought, I used to feel the need to verify these with my seniors who were placed, just in case I was directed to wrong websites, only to find out similar questions had been asked of them.</p><p>Another question that I usually get asked is “What programming languages should we learn?”. I’ve always found it tricky to answer this question, mostly due to the fact that according to me, learning a programming language only means learning the syntax and the use of different libraries the language has to offer. The foundation step is to build a certain logical expertise and problem solving skills, which is in turn your goal. In interviews, you are mostly asked to write the <strong>pseudo-codes </strong>for problems and not the entire code in a particular language. This also depends on the company you’re interviewing for.</p><p>This brings me to the next question — “Should I target a specific company or should I be consider them equally?”. Honestly, the only person who can answer this question is the person who asked it. If you are passionate about a particular company, the work they do, the tech stack they use, then definitely be excited about it. But at the same time, be open to other opportunities.</p><p>The training and placement cells of every institute have definitely shared their experience with students and also guided them throughout, and there’s a lot more that you can learn by attending events conducted by those cells than you learn by reading this article. My intention here is to express my views and share my personal practices that might help others develop a perspective, or maybe gain confidence in already existing views.</p><p>Coming to the end of the article, I’ve got one last thing to share (might sound a tad bit philosophical). According to me, the right time to start ‘preparing’ for placements is the moment you think of the question “When should I start preparing for placements?”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cf84cbbc4c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Consider these things before accepting any job offer]]></title>
            <link>https://medium.com/@zarana-desai/consider-these-things-before-accepting-any-job-offer-52399898b89f?source=rss-701035c0acdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/52399898b89f</guid>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[worklife]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[jobs]]></category>
            <dc:creator><![CDATA[Zarana Desai]]></dc:creator>
            <pubDate>Tue, 23 Aug 2022 14:27:29 GMT</pubDate>
            <atom:updated>2022-08-23T14:51:28.079Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*VTH8Cv3cQUNHk7qc.png" /></figure><p><em>“How much are they offering?” </em>or better yet, <em>“Package kitna hai?”</em> is what you hear very often during the placements in your Final Year of Engineering. If you’re lucky enough, you are asked this in your third year itself, after bagging a pre-placement offer. Maybe, you’re not surprised when people ask you this because you’ve asked this to your seniors during your first and second years.</p><p>If, by reading the first paragraph you think that the article is about learning etiquettes and not asking people their salary, <strong>it’s</strong> 𝐧𝐨𝐭. Evident from the title, we’ll talk about the factors one should consider before accepting a job offer.</p><p>As students, we often tend to ask this question as soon as someone brings up their job, and it’s quite natural. We’ve been studying our entire lives, and someday soon, we’re going to start earning too. It’s exciting! It’s not at all abnormal to be curious about how much you’ll be paid when you enter the market. Besides, thinking about the future and imagining yourself earning that sum has its own allure. But more often than not, people usually make the mistake of not asking more questions.</p><p>So, what are the questions that you <em>should be asking? </em>Keep in mind, that even though important, a huge paycheck is not what working is all about. There are other equally important factors that must be considered while applying for jobs or accepting them.</p><p>Firstly, understand the organizational culture. Try and analyze if your thoughts and beliefs resonate with that of the company. An effective culture is the common denominator in some of the most successful companies. Hence, if the organizational culture improves overall performance, it is quite mandatory that the beliefs and values of the company be firmly upheld.</p><p>Next, learn what the company’s attrition rate is. Get to know how long do employees with your job role last in the company. Analyze the career advancement of individuals in that organization. Does the company promote from within? Ensure that you will have enough growth opportunities once you join the organization.</p><p>Does the organization believe in <strong>“Customer is the king, but employees come first”? </strong>It is really important that you have a good work-life balance and when you see your boss’ text on your phone, you don’t feel stressed. Do the employees foster mutual respect? Are the leaders empathetic? Do you think your voice is heard? Build your network and ask these questions to the current employees, if not the interviewer.</p><p>Make sure you accept a role where the work won’t bore you, and that you are recognized for the work you do. Not in the sense of being selfish and demanding credit, a genuine and deserving appreciation will make you feel empowered.</p><p>There is a plethora of factors, apart from the ones mentioned above, that one must consider before shaking hands. Sadly, everyone’s focus is on the CTC. Attending various sessions where you are explained the importance of these things will help you make the right choice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52399898b89f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>