<?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 Monday to Merge on Medium]]></title>
        <description><![CDATA[Stories by Monday to Merge on Medium]]></description>
        <link>https://medium.com/@prasannakumar8332?source=rss-133cd6a510bd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*xIywdTgSIFGKekYCr3rk4A.jpeg</url>
            <title>Stories by Monday to Merge on Medium</title>
            <link>https://medium.com/@prasannakumar8332?source=rss-133cd6a510bd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:46:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@prasannakumar8332/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[How to prepare for the interviews while working a Full-time job]]></title>
            <link>https://medium.com/codetodeploy/how-to-prepare-for-the-interviews-while-working-a-full-time-job-bfec09028565?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfec09028565</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 14:59:46 GMT</pubDate>
            <atom:updated>2026-10-24T13:44:32.218Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Prepare for Technical Interviews With Just 1 – 2 Hours a Day</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ipNwdBeumVh7bUHc" /></figure><h3><strong>The problem isn’t always discipline</strong></h3><p>You may already have the motivation to move forward in your career. You know you want a better role, more challenging work, or a workplace where you can keep growing. Yet, after a full day of meetings, deadlines, and responsibilities, interview preparation can feel like one more thing you<br>cannot fit into your life.</p><blockquote><em>💥 </em><strong><em>Master AI &amp; Tech Skills</em></strong><br>💰 One Plan. Multiple Courses. More Savings.<br>🔥 Get Up to 50% OFF | ⏰ Limited-Time Offer<br><a href="http://trk.udemy.com/OYJoKA"><em>👉 </em><strong><em>Enroll Now &amp; Start Learning</em></strong></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ITogvtC6mF2BUF35Qsd9pg.png" /></figure><p>The problem isn’t necessarily a lack of discipline. Often, it’s the absence of a plan that fits your actual schedule.<br>Preparing for interviews while working full-time needs a system. This article is not a fixed syllabus telling every Java developer, frontend engineer, or backend engineer exactly what to study. Think of<br>it as a practical worksheet to help you identify what you need, organize your time, and build a preparation plan that works for you.</p><p>By the end, you should have a clearer idea of what to prepare, how to budget your time, and how to<br>keep moving even when work gets demanding.</p><h3>1. Decide what you are preparing for</h3><p>Before deciding how to prepare, get clear about what you are preparing for. Identify your target roles, review relevant job descriptions, and understand the interview rounds you are likely to face.</p><p>Write everything down in a notebook or document. It does not have to be neat or perfectly organized at first. Your goal at this stage is simply to get the full picture on paper — not to figure out how you will fit everything into your schedule yet.</p><p>Include the technical topics mentioned in job descriptions, concepts you already know but need to revise, projects you may need to explain, and skills you feel less confident about. Do not overlook communication. You might understand a concept well but struggle to explain it clearly under interview pressure. If that is a gap, add it to the list too.</p><p>Also map the interview process. One company may have three rounds and another four, but the broad areas often overlap. Group similar requirements together so you can see what preparation can serve multiple interviews.</p><p>At the end of this step, you should have a comprehensive list of what you need to work on. Do not worry yet about how long it will take. First, build the map.</p><h3>2. Build a schedule you can actually follow</h3><p>Now that you have your list, turn it into a plan. Start by grouping topics into categories that reflect the interview rounds or skill areas you identified. For example, you might group JavaScript fundamentals, framework concepts, system design, coding problems, and communication practice separately.</p><p>Within each group, distinguish between topics you need to learn from scratch and topics you already understand but need to revise. Avoid scheduling all the difficult, unfamiliar material together. Mix new learning with revision and more familiar topics. This gives you some variety and makes it easier to keep going when a topic feels demanding.</p><p>Next, break broad subjects into smaller, manageable topics. A category such as JavaScript could include closures, hoisting, promises, the event loop, and other concepts relevant to your target role. Smaller tasks are easier to estimate and easier to complete.</p><p>Then estimate how much time each topic will need. A quick revision might take an hour; a new or complex topic may require several sessions. Estimate the time you need to become comfortable with the material, not just the time needed to read it once. Add up the estimates to understand the overall size of the task.</p><p>Your first plan does not need to be perfect. You will adjust it as you learn more about your pace and workload. The purpose is to make the preparation manageable, not to create a schedule so rigid that one missed session throws everything off.</p><h3>3. Study the right things in the right order</h3><p>Once you have a topic list and time estimates, prioritize. Your available time may be limited, so start with the skills that matter most for your target role and interview process. Consider the expectations in job descriptions, the experience level you are applying for, and the gaps you identified in Step 1.</p><p>Next, calculate your realistic daily capacity. Can you usually study for one hour, two hours, or more? Be honest about your workload rather than planning for an ideal week that rarely happens.</p><p>Create a plan for different kinds of days. On a normal day, you might aim for two focused hours. On a demanding day, define a smaller minimum session that helps you maintain continuity. On a lighter day or during the weekend, you may have room for a longer session — but do not assume every free hour must be spent studying.</p><p>This distinction matters because your work schedule will not be consistent every day. A plan that only works when everything goes well is unlikely to last. Decide in advance what a realistic session looks like on both your best days and your busiest days.</p><p>Finally, use your total estimated hours and your realistic weekly capacity to set an approximate timeline. Treat it as a guide, not a guarantee. Some topics will take longer than expected, and that is normal.</p><h3>4. Make every study session count</h3><p>A schedule only helps if you can follow it and see your progress. Choose a simple way to track your sessions: a calendar, notebook, spreadsheet, or habit tracker. Mark each session when you complete it. The method matters less than using it consistently.</p><p>Give every session a clear outcome. Instead of writing “study JavaScript,” define a task such as “revise closures and explain two examples without notes.” A specific outcome makes it easier to start and helps you tell whether the session was useful.</p><p>Include revision in your schedule. Revisit topics you have already covered, test what you remember, and identify what still feels unclear. Learning a concept once does not mean you will be able to recall it confidently several weeks later.</p><p>Also practise explaining what you learn. After studying a topic, try to describe it as if an interviewer had asked you about it. Notice where you hesitate, where your explanation becomes vague, and which details you cannot justify. Those are useful signals for what to revisit.</p><p>Tracking completed sessions can also help you stay motivated. On days when progress feels slow, looking back at what you have already done can remind you that your effort is adding up.</p><h3>5. Turn your current job into preparation</h3><p>Your current job can become part of your preparation instead of being only the thing that takes time away from it. Look for opportunities to apply and explain the skills you are learning in your day-to-day work.</p><p>For example, if you are preparing JavaScript concepts and your organization is running a related knowledge-sharing session, volunteer to participate or present if the opportunity is appropriate. You could also practise explaining a technical decision to teammates, document a solution, or take part in discussions related to your target role.</p><p>These opportunities help you move beyond knowing a concept in theory. You get practice communicating it, answering questions, and connecting it to real situations. You may also learn from colleagues and build relationships across your organization.</p><p>You do not need to force every work task to fit your interview plan. Simply notice the useful opportunities already available and make better use of them.</p><h3>6. Practise interviewing, not just studying</h3><p>Studying and interviewing are different skills. When you study, you can follow your own train of thought and understand a topic in the way that makes sense to you. In an interview, you need to communicate that understanding clearly, respond to follow-up questions, and explain why your answer makes sense.</p><p>After learning a topic, practise teaching it to someone else — or explain it out loud to an imaginary listener. You can even use the familiar “rubber duck” technique: explain the concept to a toy or an empty chair as simply as possible. The goal is to make your explanation clear enough that someone unfamiliar with the topic could follow the main idea.</p><p>Do not stop at definitions. Practise explaining why something works, when you would use it, what trade-offs it involves, and what alternatives exist. Interviewers often ask follow-up questions because they want to understand how deeply you know a subject, not just whether you remember a definition.</p><p>When you struggle to explain something, treat that as feedback rather than failure. Return to the topic, fill the gap, and try again. The more often you practise explaining and defending your reasoning, the more familiar the interview format will feel.</p><h3>7. Start applying and learn from feedback</h3><p>Do not wait until you feel that you have mastered every topic before you begin applying. Once you have covered the important foundations and can explain them reasonably well, start taking interviews that fit your goals.</p><p>Real interviews can reveal gaps that are difficult to spot when you study alone. After each interview, write down the questions that challenged you, the concepts you could not explain clearly, and the areas where you need more practice. Use that feedback to update your preparation plan.</p><p>You can also create practice scenarios yourself. Ask an AI tool to act as an interviewer, question you on a topic, challenge your assumptions, and ask follow-up questions based on your answers. Try to answer before looking at hints, and ask for feedback on both accuracy and clarity.</p><p>The goal is not to stretch preparation endlessly. Work through the important items on your list, apply what you have learned, and use feedback to decide what to improve next. Preparation becomes more effective when it includes a cycle of learning, practice, feedback, and adjustment.</p><h3>8. Stay consistent without burning out</h3><p>Consistency is what turns a plan into progress. But consistency does not mean forcing yourself to complete an unrealistic workload every day. It means showing up regularly in a way you can sustain.</p><p>If you miss a session, avoid automatically doubling the next day’s workload to compensate. That can create a backlog that feels increasingly difficult to manage. Instead, return to the plan, adjust it if necessary, and continue with the next realistic session.</p><p>When a topic feels heavy, give it the time it needs and take short breaks when necessary. On especially busy days, use the smaller session you planned in advance. The aim is to preserve the habit without treating rest as failure.</p><p>Keep a record of your progress. Mark completed sessions on a calendar or track the topics you have covered. Looking back at where you started and how far you have come can help you stay motivated when the finish line still feels distant.</p><p>Pay attention to signs that your plan is becoming unsustainable. If you are regularly exhausted or unable to keep up, reassess the workload rather than blaming yourself. A preparation system should support your career growth while fitting into your life — not consume every part of it.</p><h3>Conclusion: Build a system that survives real life</h3><p>Preparing for interviews while working full-time is challenging, but it becomes more manageable when you stop relying on motivation alone and build a system around your actual circumstances.</p><p>Start by defining your target, listing the skills you need, estimating the time involved, and prioritizing what matters most. Build a schedule that accounts for both normal and demanding workdays. Track your sessions, revise regularly, practise explaining your reasoning, and use interviews and feedback to identify what to improve.</p><p>Most importantly, make the plan your own. Someone else may prepare faster, study longer, or have a different level of experience. Their timeline does not have to be yours. Some topics may take days; others may take weeks. Adjust your plan based on what you need and the time you realistically have.</p><p>You do not need a perfect plan. You need a workable one that you can return to, improve, and follow consistently. Start small, keep moving, and let steady progress do its work.</p><h3>Thank you for being a part of the community</h3><p><em>Before you go:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d9QTaaaxboQP_gKSLedW_w.png" /></figure><p>👉 Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏<strong>️️</strong></p><p>👉 Follow us: <a href="https://medium.com/codetodeploy"><strong>Medium</strong></a></p><p>👉 CodeToDeploy Tech Community is live on Discord — <a href="https://discord.gg/ZpwhHq6D"><strong>Join now!</strong></a></p><p><strong>Disclosure:</strong> This post includes affiliate and partnership links.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfec09028565" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codetodeploy/how-to-prepare-for-the-interviews-while-working-a-full-time-job-bfec09028565">How to prepare for the interviews while working a Full-time job</a> was originally published in <a href="https://medium.com/codetodeploy">CodeToDeploy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Interview Experience with JPMorgan chase: A deep dive into Technical Rounds and Salary…]]></title>
            <link>https://prasannakumar8332.medium.com/my-interview-experience-with-jpmorgan-chase-a-deep-dive-into-technical-rounds-and-salary-5dbcb26c679f?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dbcb26c679f</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Fri, 08 May 2026 08:38:28 GMT</pubDate>
            <atom:updated>2026-05-09T01:57:48.731Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Interview Experience with JPMorgan chase: A deep dive into Technical Rounds and Salary Negotiations</h3><p>Getting shortlisted at JPMorgan Chase wasn’t just luck. One of my friends from JPMorgan Chase referred me for a Software Engineer role, and after almost a month, I finally received a call saying I was shortlisted for the interview process. Since I already had the job description before applying, I tailored my resume carefully to match the role and highlight the skills they were specifically looking for.</p><p>In this blog, I’ll share my complete JPMorgan interview experience — from the initial screening round to technical and managerial discussions, the kind of questions asked, what the interviewers focused on, and the mistakes to avoid. If you’re preparing for a Software Engineer interview at JPMorgan or any product-based company, this post will give you a realistic idea of what the actual process looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c27B_RjPjCjSst3LWGYdqg.jpeg" /></figure><h3>Round 1</h3><p>The first round had a single interviewer on the panel. It started with a quick self-introduction followed by a detailed discussion about my previous projects, daily responsibilities, and the technologies I had worked on over the years.</p><p>The interviewer then asked me to rate myself in JavaScript out of 10. Since I’ve been working with JavaScript for almost 5 years, I rated myself around 8 — confident enough in my skills, but without sounding overconfident.</p><p>Most of the questions in this round were focused on JavaScript fundamentals and commonly asked frontend concepts. Nothing felt unnecessarily tricky or designed to confuse the candidate. Instead, the interviewer wanted to check conceptual clarity and practical understanding.</p><p>Some of the major JavaScript topics covered were:</p><ul><li>Difference between var, let, and const</li><li>Closures with real-time examples</li><li>ES6 concepts</li><li>Scope and hoisting</li><li>Practical JavaScript behavior questions</li></ul><p>The discussion then shifted heavily toward React fundamentals, which turned out to be one of the most important parts of this round. Initially, the questions started with basic React concepts and definitions, but once the interviewer realized I was comfortable with the fundamentals, the discussion gradually became deeper and more practical.</p><p>What made this round particularly interesting was the live coding discussion.</p><p>I was given a coding problem and asked to solve it in real time. But the challenge wasn’t just solving the initial problem. The interviewer continuously added new conditions, edge cases, and changing requirements throughout the discussion to test how I handled evolving scenarios.</p><p>This part alone lasted for almost 25 minutes.</p><p>The main focus areas were:</p><ul><li>Handling edge cases</li><li>Writing scalable and maintainable logic</li><li>Explaining the reasoning behind technical decisions</li><li>Real-world problem-solving ability</li><li>Adapting quickly to changing requirements</li></ul><p>The interviewer seemed more interested in understanding my thought process rather than expecting a perfect memorized answer. I explained my approach clearly while solving the problem, which helped keep the discussion interactive.</p><p>Overall, I was able to handle most of the follow-up scenarios well, and the interviewer seemed quite impressed with the approach and reasoning.</p><h3>Difficulty Level: 6/10</h3><p>If you have strong JavaScript fundamentals, good React basics, and decent hands-on coding experience, this round should feel manageable.</p><h3>Round 2</h3><p>The second round had two interviewers on the panel, both of them Tech Leads.</p><p>After a quick introduction from their side, the discussion started around my experience, interests, technical skill set, and responsibilities in previous projects.</p><p>Unlike the first round, this discussion was more focused on evaluating whether I could independently handle real-world project situations and production-level challenges.</p><p>A large portion of the interview revolved around scenario-based questions, especially related to React Native and mobile application development.</p><p>Some of the major discussion areas included:</p><ul><li>Handling slow-performing applications</li><li>Debugging production issues</li><li>Identifying performance bottlenecks</li><li>Improving application performance</li><li>Explaining technical decisions and trade-offs</li><li>Real-time project troubleshooting</li></ul><p>One thing I genuinely liked during this round was how interactive the conversation felt. Whenever I got stuck at a point, the interviewers gave small hints instead of making the discussion uncomfortable. It felt more like a collaborative technical discussion than a strict interrogation.</p><p>This round also included:</p><ul><li>Coding discussion</li><li>Unit testing concepts</li><li>Real-world debugging approaches</li></ul><p>So if you’re preparing for a similar role, I’d strongly recommend spending time on:</p><ul><li>React Native fundamentals</li><li>Performance optimization</li><li>Debugging strategies</li><li>Unit testing concepts</li><li>Scenario-based problem solving</li></ul><p>The entire discussion lasted close to an hour, but overall the interaction felt smooth, positive, and engaging throughout.</p><h3>Round 3 — Hiring Manager Round</h3><p>The third round had a single interviewer who was the Hiring Manager.</p><p>Unlike the previous technical rounds, this discussion focused more on communication skills, ownership, project experience, leadership mindset, and architectural thinking rather than deep technical implementation questions.</p><p>Most of the conversation revolved around:</p><ul><li>Previous project experience</li><li>Roles and responsibilities</li><li>Impact created in projects</li><li>Handling timelines and pressure</li><li>Ownership in real project environments</li><li>Working with teams</li><li>Decision making</li><li>Mentoring junior developers</li></ul><p>There were also behavioral questions around difficult production bugs, handling challenging situations, and how I approached responsibilities during critical project phases.</p><p>One of the most important questions asked was:</p><p><strong>“Why do you want to join JPMorgan Chase?”</strong></p><p>So make sure you prepare this answer properly instead of giving generic responses.</p><p>Interestingly, this round felt less like a traditional interview and more like a professional discussion. Toward the end, the conversation gradually shifted from evaluating my skills to discussing the actual role, team expectations, and the kind of work I would potentially handle if selected.</p><p>That honestly felt like a positive sign.</p><h3>Final Thoughts on the JPMorgan Chase Interview Process</h3><p>Overall, the interview experience at JPMorgan Chase was extremely positive, structured, and professional.</p><p>One thing I genuinely appreciated throughout the process was that the interviewers focused far more on:</p><ul><li>Real-world problem solving</li><li>Communication skills</li><li>Logical thinking</li><li>Ownership mindset</li><li>Practical experience</li></ul><p>…instead of asking unnecessarily tricky or confusing questions just for the sake of difficulty.</p><p>The biggest realization I had after this process was:</p><blockquote><em>Interviewers are not only looking for someone who can write code. They also want to understand how you think, communicate, approach problems, and handle real project situations under pressure.</em></blockquote><p>So if you’re preparing for a Software Engineer, Frontend Developer, ReactJS, or React Native interview at JPMorgan Chase, my suggestion would be:</p><ul><li>Focus strongly on JavaScript fundamentals</li><li>Be clear with React concepts</li><li>Practice scenario-based discussions</li><li>Prepare real project examples</li><li>Improve communication and explanation skills</li><li>Learn to explain your thought process confidently</li></ul><p>Hope this interview experience helps someone preparing for their upcoming interviews.</p><p>All the best for your preparation! Happy Coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dbcb26c679f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You’re Not Getting Recognized – Here’s the Real Reason]]></title>
            <link>https://prasannakumar8332.medium.com/youre-not-getting-recognized-here-s-the-real-reason-3dc5e85e9852?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dc5e85e9852</guid>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Thu, 02 Apr 2026 08:43:04 GMT</pubDate>
            <atom:updated>2026-04-02T08:43:04.518Z</atom:updated>
            <content:encoded><![CDATA[<p>You work hard. You deliver on time. You fix bugs no one else wants to touch. And still… someone else gets the credit.</p><p>Pause for a second.</p><p>It’s not because they’re smarter than you.</p><p>It’s not because they work harder.</p><p>It’s because they understand something you don’t.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*iZo77BIH5lR4m9T7qoFoYw.jpeg" /></figure><h4>The Uncomfortable Truth</h4><p>Hard work is invisible.</p><p>Recognition is not.</p><p>Most developers believe:</p><p>“My work will speak for itself.”</p><p>It won’t.</p><p>Not in meetings.</p><p>Not in performance reviews.</p><p>Not when promotions are decided.</p><h4>A Realization I Had</h4><p>At one point, I was doing everything right.</p><ul><li>Delivering consistently.</li><li>- Helping teammates.</li><li>- Taking ownership.</li></ul><p>But when appreciation came… my name wasn’t there.</p><p>Someone else – who spoke more, shared more, and positioned their work better – got noticed.</p><p>That’s when it clicked:</p><p>Visibility beats talent in corporate life.</p><p>Not always.</p><p>But often enough to decide your growth.</p><h4>Why This Happens</h4><p>Because companies don’t reward effort.</p><p>They reward:</p><ul><li>Impact they can see.</li><li>Value they can measure.</li><li>People they remember.</li></ul><p>If your work is invisible,</p><p>your effort is irrelevant.</p><h4>What Actually Works</h4><p>If you want recognition, you need to change how you operate.</p><h4>1. Communicate your work</h4><p>Don’t assume people know what you did.</p><ul><li>Share updates.</li><li>Highlight outcomes.</li><li>Make your impact visible.</li></ul><h4>2. Speak in meetings</h4><p>You don’t need to dominate.</p><p>But silence?</p><p>That guarantees invisibility.</p><h4>3. Own outcomes, not tasks</h4><p>Don’t say:</p><p>“I completed this feature”</p><p>Say:</p><p>“This improved load time by 30%”</p><h4>4. Build visibility, not noise</h4><p>This isn’t about bragging.</p><p>It’s about:</p><p>Making sure your work reaches the right people.</p><h4>Final Thought</h4><p>The workplace is not just about doing the work.</p><p>It’s about making sure the work is seen.</p><p>Ignore this…</p><p>and you’ll keep wondering why others move ahead faster than you.</p><h4>Follow for More</h4><p>I write about the real side of tech careers –</p><p>interviews, office politics, and growth strategies most people won’t tell you.</p><p>Follow if you want to grow faster than the average developer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dc5e85e9852" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Office Politics is Killing Your Career: 4 Brutal Rules to Win Without Losing Your Mind]]></title>
            <link>https://prasannakumar8332.medium.com/office-politics-is-killing-your-career-4-brutal-rules-to-win-without-losing-your-mind-97ea78bd066e?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/97ea78bd066e</guid>
            <category><![CDATA[burnout-prevention]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[office-politics]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Wed, 18 Jun 2025 06:49:49 GMT</pubDate>
            <atom:updated>2025-06-18T06:49:49.540Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A divided office space showing one side of a relaxed employee focused on personal growth, and the other side of a stressed worker overwhelmed by office politics." src="https://cdn-images-1.medium.com/max/1024/1*h2haai-jQCwWXcecIw7s3A.png" /></figure><p>Whether you like it or not, office politics shape your career. You can try to avoid it, but in most workplaces, it’s not <em>if</em> you’re involved — it’s <em>how deeply</em>. And if you’re not careful, it could be silently sabotaging your success.</p><p>In the world of office politics, the players with more power — not merit — usually win. It could be your boss favoring someone else over you. Or worse, they might be too lazy to contribute but still take credit for your work. No matter the reason, the frustration feels the same when your effort goes unnoticed.</p><p>And when you finally try to speak up, you’re suddenly labeled the troublemaker. That’s the harsh truth: You can’t ignore politics, and openly fighting it can backfire. So how do you protect yourself <em>and</em> keep your integrity?</p><h3>🧨 Rule #1: Never Give 100% (All the Time)</h3><blockquote><strong>🧠 Why Overworking Is a Trap</strong></blockquote><p>The more you work, the more work you’ll get. Sounds ridiculous — but it’s true. Your work is your <em>time, focus, and energy</em>. Not free currency.</p><p>If you’re consistently doing 10 hours of work for 8 hours of pay, you’re not being loyal — you’re being exploited. Be honest with your conscience. If you’re giving more than the respect, recognition, or compensation you’re receiving, that’s not dedication. That’s burnout in the making.</p><h3>⚡ Rule #2: Speak Up for Your Work</h3><blockquote><strong>🎯 Visibility &gt; Humility in the Corporate World</strong></blockquote><p>People will give updates on your work and subtly take credit. It seems harmless — but it’s not.</p><p>Always take credit for what you do. Document everything. Make your effort visible and traceable. This isn’t bragging — it’s self-preservation. The more your contributions are on record, the harder it is for anyone to hijack them.</p><h3>🚫 Rule #3: Don’t Be the “Go-To” Person for Everything</h3><blockquote><strong>⚖️ Respect Your Bandwidth</strong></blockquote><p>Being the “go-to” person might seem flattering. But that spotlight comes at a price — usually paid in your time, mental energy, and peace.</p><p>People will start offloading their work onto you. Tasks beyond your role. Unnecessary stress. You end up being everyone’s hero, but at your own expense. Learn to say no. Protect your calendar like it’s your sanity — because it is.</p><h3>💼 Rule #4: Don’t Stay at the Same Company for Years</h3><blockquote><strong>📈 Growth Comes From Moving, Not Sitting</strong></blockquote><p>Come on, bro — you’re not Jensen Huang (CEO of Nvidia). You don’t have stock options worth billions. Switch companies at least once every 3 years.</p><p>Staying too long can trap you in comfort, stagnation, and toxic office dynamics. Your market value grows when you move — roles get upgraded, salaries jump, networks expand.</p><p>Yes, emotional attachment to your job is real. But are you working for nostalgia or your family’s future?</p><p>Benchmark your compensation. If you’re behind, don’t just grind harder — plan your exit.</p><blockquote><em>📌 A detailed blog on why switching beats slogging is coming soon. Stay tuned.</em></blockquote><h3>🔍 TL;DR — 4 Rules to Outsmart Office Politics:</h3><ul><li><strong>Don’t overwork</strong> — match output to compensation.</li><li><strong>Take credit</strong> — protect your contributions.</li><li><strong>Say no</strong> — being helpful shouldn’t cost your sanity.</li><li><strong>Switch often</strong> — don’t let comfort kill your career.</li></ul><h3>🧭 Conclusion: Play Smarter, Not Harder</h3><p>These rules aren’t cynical — they’re survival strategies. In today’s workplace, <em>hard work without smart boundaries leads to burnout, not bonuses</em>.</p><p>Put your extra effort where it counts: <strong>your own growth</strong>.</p><p>If you owned a YouTube channel, an extra 10 hours a week would build <em>your</em> future. But spending 2 more hours at work? That rarely pays off long-term.</p><p>Invest your energy into yourself. Learn. Build. Create. The more you grow, the less politics can affect you — and the better you’ll navigate any workplace.</p><h3>🪙 Golden Rule: Everything is Business.</h3><p>In business, you either <strong>learn</strong> or <strong>earn</strong>. If you’re doing neither, you’re just surviving. Don’t play the politics game or fight it. Just outgrow it.</p><h3>💬 Found this relatable?</h3><p>Hit 💖, leave a comment, or tag that friend quietly burning out. Follow me for more no-BS takes on <strong>career, coding, and corporate survival</strong>.</p><p>#CorporateLife #OfficePolitics #CareerGrowth #Productivity #WorkplaceTruths</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97ea78bd066e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code with INTENT]]></title>
            <link>https://prasannakumar8332.medium.com/code-with-intent-96165ac11167?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/96165ac11167</guid>
            <category><![CDATA[code-readability]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[refactoring]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Thu, 17 Apr 2025 05:15:33 GMT</pubDate>
            <atom:updated>2025-04-17T05:15:50.705Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week, I was reviewing a codebase and noticed that it required significant effort to read. It wasn’t because the code was overly complicated or poorly formatted, but for some reason, it was difficult to follow and felt hard to read. I decided to investigate what might have gone wrong and attempted to rewrite the entire code with a different approach. Although I didn’t change the logic, I rewrote the code to improve its readability. While I can’t share the exact codebase here, I can provide some examples to illustrate what I mean. Let’s dive in!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cftIms9ca-D88-uC" /></figure><h3><strong>The order of arguments in conditionals matter.</strong></h3><p>Imagine you are building a website that requires age verification. At some point, you need to add a condition to check if the user’s age is above 18 years. This exact scenario happened in my case. Someone had written the condition as follows:</p><pre>if (18 &lt;= age) { doSomething() }</pre><p>Although it is not a difficult condition to read and understand, it made me stop and think for a while to grasp the intent. This experience helped me realize the importance of subtle etiquette when writing conditions.</p><blockquote><strong>Putting the variable on the left mirrors how we speak in everyday language</strong></blockquote><p>I rewrote the same condition in a way that made it much easier to read and process in my mind.</p><pre>if (age &gt;= 18) { doSomething() }</pre><p>okay now what if there are two variables?</p><pre>if (totalTasks &gt; completedTasks) ❌<br>if (completedTasks &lt; totalTasks) ✅</pre><p>Then put the more stable reference variable on the right side.</p><p>Don’t just blindly write code. Communicate Intent</p><p>Happy coding!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96165ac11167" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Interview Journey with Deloitte: A Deep Dive into Technical Rounds and Salary Negotiations]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://prasannakumar8332.medium.com/my-interview-journey-with-deloitte-a-deep-dive-into-technical-rounds-and-salary-negotiations-7fdf6b9d9ed5?source=rss-133cd6a510bd------2"><img src="https://cdn-images-1.medium.com/max/600/1*YX3pb6d4K6I-DOqX-MQwlw@2x.jpeg" width="600"></a></p><p class="medium-feed-snippet">My interview experience at Deloitte for Senior Frontend Engineer</p><p class="medium-feed-link"><a href="https://prasannakumar8332.medium.com/my-interview-journey-with-deloitte-a-deep-dive-into-technical-rounds-and-salary-negotiations-7fdf6b9d9ed5?source=rss-133cd6a510bd------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://prasannakumar8332.medium.com/my-interview-journey-with-deloitte-a-deep-dive-into-technical-rounds-and-salary-negotiations-7fdf6b9d9ed5?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fdf6b9d9ed5</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Tue, 14 Jan 2025 14:54:28 GMT</pubDate>
            <atom:updated>2025-01-14T15:06:39.575Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How I Conquered My Nerves and Nailed My Interviews]]></title>
            <link>https://prasannakumar8332.medium.com/how-i-conquered-my-nerves-and-nailed-my-interviews-5460f97599b2?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5460f97599b2</guid>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Sun, 03 Nov 2024 15:32:28 GMT</pubDate>
            <atom:updated>2024-11-03T15:32:28.310Z</atom:updated>
            <content:encoded><![CDATA[<p>Interview anxiety is something many people struggle with, myself included. Early in my career, passing an interview — whether it was a technical screening or an HR conversation — felt like a monumental challenge. But over time, I learned strategies that helped me take control, and now I’m here to share tips to help you do the same.</p><p>In the beginning, attending interviews was daunting. The process was intense: impressing the interviewer, answering tricky questions, focusing on vocabulary, tackling technical questions, managing the “uhms” and “ahs” — all of it was overwhelming. No matter how much I practiced in front of the mirror, one unexpected question could still unravel my confidence entirely.</p><p>But then, I realized that my issue wasn’t necessarily with my knowledge, confidence, or even appearance. The real problem was how I approached the interview itself. Through trial and error, I discovered ways to change my mindset and manage the process more effectively.</p><p>In this post, I’m sharing some insights that helped me overcome my interview anxiety. I hope these tips guide you as you prepare for your next interview — and I’ll be back soon with even more strategies to help you excel!</p><blockquote><strong>The Importance of an Honest Resume</strong></blockquote><p>One of the biggest mistakes people make when preparing for interviews is with their resume. I’m not talking about technical skills or the skills you might be tempted to exaggerate — I’m talking about being completely honest in your resume. Your confidence starts with your resume. Imagine walking into a test where you know exactly what will be on the question paper — that’s how it should feel when you review your resume before an interview.</p><p>Many candidates make the critical error of adding skills or experiences that they aren’t genuinely comfortable with, only to be caught off guard in the interview. Do you think you can outsmart an experienced interviewer with a few well-chosen words? It rarely works. Instead, keep your resume focused on the skills and experiences you know thoroughly. That way, when any question arises from your resume, you’ll be prepared, and your confidence will be solid.</p><p>Tip: just keep only the things you are aware of and no drama here, please!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*93iKUKPsXJmV7KJH.jpg" /></figure><blockquote>Mastering the “Tell Me About Yourself” Question</blockquote><p>A lot of candidates stumble over the classic “Tell me about yourself.” It might seem intimidating, but this question isn’t as tough as it appears. However, if you find yourself struggling or fumbling with vocabulary right from the start, it can feel like your confidence is plummeting — and this first impression sets the tone for the rest of the interview.</p><p><strong>Tip:</strong> Prepare a concise, well-structured response of around 300 words that takes 2–3 minutes to deliver. Think back to the memorization techniques we all used in school and practice until you’re comfortable. During this part of the interview, there’s no need to overthink or add extra details — just focus on delivering a clear and confident introduction.</p><p>Having this prepared response will help you start strong, avoid unnecessary pauses, and make a solid first impression.</p><blockquote><strong>Keep the examples at your fingertips</strong></blockquote><p>When interviewing candidates, I’ve noticed that many struggle to provide a clear example when asked how they’ve applied certain skills in their work. This can lead to confusion and may expose a lack of preparedness, causing confidence to waver in front of the interviewer. Why does this happen? Often, it’s because candidates haven’t prepared concrete examples to illustrate their skills.</p><p><strong>Tip:</strong> Think of yourself as an author of your own story. If you list a skill on your resume, make sure you have a clear, specific example ready to discuss. For instance, in most of the interviews I’ve attended, I was asked about closures in JavaScript. So, I prepared by writing out a concise piece of code and an explanation to walk the interviewer through my understanding of closures. Having these prepared responses can boost your confidence, helping you to articulate your skills clearly and make a lasting impression.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*R-y-GhxEcvem_i-s.png" /><figcaption>Have examples for each</figcaption></figure><blockquote><strong>Practice storytelling</strong></blockquote><p>This is my favorite part of the interview process — answering scenario or role-based questions. After addressing technical and example-based questions, interviewers often move on to prompts like, <em>“If you were in this position, what would you do?”</em> or <em>“Tell me about a time when you handled a challenging scenario.”</em></p><p>These questions are an excellent opportunity. While the interviewer may believe they’re testing you, this is your chance to turn the tables and impress them. Here’s a key tip: buy yourself time. An interview typically lasts 60 to 90 minutes, and if you can engage with this question for 10–15 minutes, you’ll take up valuable interview time while demonstrating your thought process and confidence.</p><p><strong>Tip:</strong> Think of this as the “About” section of your professional story. Tailor your response to make it engaging, compelling, and memorable. You’re the hero of this story, so focus on showing your ownership and leadership. Get into the details, share the specific actions you took, and present yourself as a problem-solver who made a real impact. Adding these elements will capture your interviewer’s attention and allow you to stand out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n7ImIPBXHBpEiYsi.jpg" /><figcaption>This is how i saved my team from collapsing</figcaption></figure><blockquote><strong>Wrapping Up</strong></blockquote><p>Interviews can be intimidating, but with the right mindset, preparation, and a few strategic tricks, you can turn them into opportunities to showcase your true potential. Remember, it’s all about confidence, honesty, and crafting a story that highlights your unique strengths.</p><p>I hope these tips help you feel more prepared for your next interview! Stay tuned, as I’ll be sharing more blogs on this topic to dive deeper into each strategy. If you found this helpful, give it a like, share with friends, and let’s keep growing together in this journey to master interviews. Good luck, and remember — you’ve got this!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5460f97599b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Rise of AI: How Tools Like ChatGPT and Midjourney Are Revolutionizing Our Lives]]></title>
            <link>https://prasannakumar8332.medium.com/the-rise-of-ai-how-tools-like-chatgpt-and-midjourney-are-revolutionizing-our-lives-2f7d896df767?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f7d896df767</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[chatgpt]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Mon, 01 Jul 2024 15:17:12 GMT</pubDate>
            <atom:updated>2024-07-01T15:17:12.184Z</atom:updated>
            <content:encoded><![CDATA[<p>Artificial intelligence has experienced significant advancements in recent years, and this is only the beginning! Tools such as ChatGPT and Midjourney have demonstrated the impressive capabilities of AI, integrating these technologies deeply into our daily lives.</p><p>A recent study suggests that AI could potentially replace 300 million jobs. Every 6–7 years, new trends emerge, and currently, AI is at the forefront. Learning how to use AI tools is essential to keeping up with this trend.</p><p>While AI may displace some jobs, it will also create numerous new opportunities. One emerging field is prompt engineering, where professionals ensure that AI tools function optimally by providing the right inputs.</p><p>Many individuals have witnessed the capabilities of AI with tools like ChatGPT but are unsure how to utilize them effectively. This blog post will guide you through using ChatGPT in eight different scenarios. First, let’s briefly explore what ChatGPT is.</p><p><strong>What is ChatGPT?</strong><br>ChatGPT is a powerful chatbot capable of assisting with tasks like writing emails, essays, and code. It could become an invaluable assistant in your future endeavors.</p><p>Initially developed based on the GPT-3.5 model and further enhanced with GPT-4, ChatGPT has evolved from accepting only text inputs to now handling visual inputs as well. For instance, you can provide ChatGPT with a website mockup, and it will generate the necessary code to build the site.</p><p><strong>Converting a Mockup to a Website with ChatGPT</strong><br>The potential applications of ChatGPT are limited only by your imagination. However, it is essential to learn how to use this tool effectively. This blog will demonstrate how to utilize ChatGPT in various everyday scenarios. ChatGPT is available for free, but for $20 a month, you can access a faster version based on GPT-4.</p><p>Having briefly reviewed what ChatGPT is, let’s dive into its practical applications.</p><ol><li><strong>Summarizing</strong></li></ol><p>With new books being published daily in fields like finance, motivation, and programming, it’s challenging to find time to read them all. ChatGPT can help by summarizing books. For example, let’s ask ChatGPT to summarize “Animal Farm” by George Orwell:</p><p>“Summarize ‘Animal Farm’ by George Orwell.”</p><p>As you can see, ChatGPT provides a concise summary. While reading the full book is ideal, summaries can help you decide whether to invest time in a particular book.</p><p><strong>2. Recommendation</strong></p><p>Finding the best products or books can be time-consuming. ChatGPT can streamline this process by providing recommendations. Suppose you want to find the best books on data science:</p><p>“Recommend 5 best books on data science.”</p><p>ChatGPT quickly lists recommended books along with their features, making it easier to find quality resources. You can use ChatGPT for various recommendations, including holidays, movies, and tech products.</p><p><strong>3. Marketing</strong></p><p>While you may excel in your field, marketing might not be your strength. ChatGPT can assist with creating marketing content, such as Facebook ads. For example:</p><p>“Create a Facebook ad for the best web development agency.”</p><p>ChatGPT generates a compelling ad, saving you the cost of hiring an agency. It can also help with email campaigns and social media posts, making marketing more accessible.</p><p><strong>4. Creating Content</strong></p><p>Content creation is a valuable skill today, helping you grow professionally and expand your network. ChatGPT can assist in generating catchy titles for your content. For instance:</p><p>“I want to build an AI-powered education platform. Suggest 10 catchy names for this startup idea.”</p><p>ChatGPT provides creative names for your startup, which you can also use for blog posts or YouTube channels.</p><p><strong>5. Personal Development</strong></p><p>Real-life stories can be inspiring, but reading lengthy biographies can be daunting. ChatGPT can summarize the lives of successful individuals for motivation. For example:</p><p>“Tell me the true story of Steve Jobs, the Apple founder, to motivate me.”</p><p>ChatGPT offers a brief yet inspiring overview of Steve Jobs’ journey, highlighting his successes and challenges.</p><p><strong>6. Simplifying Complex Issues</strong></p><p>Complex topics can be challenging to understand. ChatGPT simplifies these concepts. For example:</p><p>“Explain quantum computing like I’m 5.”</p><p>ChatGPT breaks down quantum computing into simple terms, making it easier to grasp.</p><p><strong>7. Improving Your Writing Skills</strong></p><p>If you’re looking to improve your English skills, ChatGPT can help refine your writing. For instance:</p><p>“Rewrite this sentence more formally: ‘I want to receive payment. Can you send the invoice?’”</p><p>ChatGPT transforms the sentence into a more formal version. It can also correct grammar, improve text fluency, and translate content.</p><p><strong>8. Preparing for Interviews</strong></p><p>Interviews can be stressful, but ChatGPT can help you prepare by acting as an interviewer. For example:</p><p>“Act as an interviewer and ask me 10 difficult questions as a data scientist.”</p><p>ChatGPT provides challenging questions to help you practice. Additionally, it can guide you on salary negotiations:</p><p>“How do I respond if the interviewer asks me for a salary?”</p><p>By using these strategies, you can better showcase your skills and negotiate effectively.</p><h3>Wrap-Up</h3><p>AI tools, particularly ChatGPT, are becoming increasingly vital in our lives. By learning to use ChatGPT effectively, you can save time and money while enhancing your daily activities. In this blog, we explored eight different scenarios for using ChatGPT, from summarizing books to preparing for interviews. ChatGPT can also assist with coding, resume writing, screenwriting, and design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f7d896df767" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Master the Art of Code Reviews: 5 Expert Tips for Seamless Collaboration and Happy Engineers!]]></title>
            <link>https://prasannakumar8332.medium.com/master-the-art-of-code-reviews-5-expert-tips-for-seamless-collaboration-and-happy-engineers-f2683fc9102b?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2683fc9102b</guid>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[practice]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Wed, 31 Jan 2024 14:17:43 GMT</pubDate>
            <atom:updated>2024-01-31T14:17:43.690Z</atom:updated>
            <content:encoded><![CDATA[<h3>“Master the Art of Code Reviews: 5 Expert Tips for Seamless Collaboration and Happy Engineers! 💻🚀”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PTvWII-lgu3r_GLC2BHmFQ.jpeg" /></figure><p>Code reviews can be a challenging aspect of the development process, often involving more interpersonal skills than technical prowess. Like many others, I only realized this when I found myself navigating the intricacies of peer reviews.</p><p>It’s natural for individuals to feel a sense of offense when their work is critiqued, even if the feedback is not intended to be personal. This dynamic can be exacerbated by differences in organizational hierarchy or experience levels, making it crucial to handle reviews with tact.</p><p>While not everyone may readily embrace suggestions, it falls upon you to uphold coding standards and guide your peers. Through my own experiences, I’ve come to appreciate the pivotal role of effective communication in minimizing friction and convincing others with concise input.</p><p>Here are a few recommendations to ensure a smoother process for suggesting changes without bruising anyone’s ego:</p><p>🚀 Code Review Tips for Stellar Collaboration! 🌟</p><p>Navigating the delicate art of code reviews? Here are some tips to foster effective communication and maintain a positive collaborative spirit:</p><p>1️⃣ Phrase Comments as Questions:<br> ❌ “Fix this”<br> ✅ “Did we consider the case of X?” <br> Remember, softening feedback with questions fosters understanding without discouraging the engineer’s hard work.</p><p>2️⃣ Facilitate Face-to-Face Conversations:<br> ❌ Tons of comments back and forth<br> ✅ “Have 10 mins. I noticed a difference from what I had in mind. Can you explain it to me? I may have missed something.”<br> When comments pile up, consider a brief conversation to clear up any confusion.</p><p>3️⃣ Coding Style Suggestions with Empathy:<br> ❌ “Don’t use 2 functions, use one”<br> ✅ “Nit: Would it be more readable with 1 function?” <br> Acknowledge the autonomy of engineers and offer suggestions without blocking the pull request.</p><p>4️⃣ Embrace Disagreement, Trust the Team:<br> ❌ “OMG, what a jerk, they didn’t listen to me.”<br> ✅ “I don’t love what they did, but it passes the acceptance criteria, and I trust their judgment.”<br> Recognize that conflicts may arise, but trust in the team’s expertise even in moments of disagreement.</p><p>5️⃣ Seize Teaching Opportunities:<br> ❌ “Google how this works and figure it out”<br> ✅ “I noticed you used this function/operator. The code works, but it isn’t optimal. I’d love to show you the concepts behind that if you have time.”<br> Encourage a learning mindset by offering guidance and turning code reviews into valuable learning experiences.</p><p>Effective code reviews not only enhance code quality but also strengthen team bonds. Let’s build a culture of constructive collaboration! 💻🤝 #CodeReview #Collaboration #TechTips</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2683fc9102b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Name Booleans Values]]></title>
            <link>https://prasannakumar8332.medium.com/auxiliary-name-the-booleans-ed954fa9f3c6?source=rss-133cd6a510bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed954fa9f3c6</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Monday to Merge]]></dc:creator>
            <pubDate>Fri, 22 Dec 2023 08:07:23 GMT</pubDate>
            <atom:updated>2023-12-22T08:28:30.731Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been reviewing code for a few months now and many people are not naming the variables right. Especially the booleans, so “How to name the boolean values?”</p><p>A boolean variable serves as a truthiness holder in programming. Naming variables, especially boolean ones, is often considered one of the most challenging aspects of programming due to its subjective nature. Finding a good name for variables, particularly boolean ones, can be time-consuming. Proper naming is crucial to enhance program readability, aiding fellow programmers in understanding the ideology and thoughts behind the code. Effective communication and networking systems are built collaboratively by peer coders.</p><p>This post aims to share insights on designing meaningful boolean variable names and provides a helpful list of examples to guide you.</p><p>Tips on Naming Conventions:</p><p><em>Categorization:</em> Categorizing these tips provides a perspective on tackling naming complexities.</p><p>Approach: When naming boolean variables, always approach from the positive side in your naming convention. Embrace the truthiness of the boolean, making it easier to comprehend. For instance:</p><ul><li>isVisible is more comfortable than isInvisible.</li><li>!isVisible is simpler than !isInvisible.</li></ul><p>By adopting a positive perspective, unnecessary complexity is reduced, especially when dealing with negation statements related to the variable.</p><p>Prefer Nouns: Simplify names using easily recognizable nouns. Stick to the formula: is/has + Noun. Prefer nouns over verbs for simplicity. For example:</p><ul><li>shouldShow can be simplified to isVisible.</li></ul><p>Stay in the Present: Use present tense in variable names. For example:</p><ul><li>isVisible is preferable over wasVisible.</li></ul><p>Present tense aligns with the code execution, making it more straightforward.</p><p>Examples: Here’s a list of good boolean variable names compared to less optimal ones to help illustrate the concepts discussed in this post.</p><pre>+=================+===============================================+<br>|      Good       |                  Not so good                  |<br>+=================+===============================================+<br>| isOpen          |  isClosed                                     |<br>+-----------------+-----------------------------------------------+<br>| isVisible       |  isInvisible, isHidden, isShowing, show, hide |<br>+-----------------+-----------------------------------------------+<br>| isResolved      | isRejected                                    |<br>+-----------------+-----------------------------------------------+<br>| isRight, isGood | isWrong, isLeft, isBad                        |<br>+-----------------+-----------------------------------------------+<br>| hasValue        | isEmpty                                       |<br>+-----------------+-----------------------------------------------+<br>| isDefined       | isUndefined                                   |<br>+-----------------+-----------------------------------------------+<br>| isOwner         | isOwning, own, wasOwner, willBeOwner          |<br>+-----------------+-----------------------------------------------+</pre><p>Naming boolean values is an important aspect of writing clean and readable code. Here are some best practices for naming boolean variables:</p><p>1. <strong>Use Positive Affirmations:</strong><br> — Choose names that reflect the positive state or action.<br> — Example: Instead of `isNotRunning`, use `isRunning`.</p><p>2. <strong>Use Clear and Concise Names</strong>:<br> — Keep names short and to the point while maintaining clarity.<br> — Example: Instead of `userIsLoggedIn`, use `isLoggedIn`.</p><p>3. <strong>Avoid Negations</strong>:<br> — Try to avoid using negations in boolean variable names.<br> — Example: Instead of `isNotEnabled`, use `isEnabled`.</p><p>4.<strong> Be Explicit</strong>:<br> — Make sure the name clearly indicates the purpose or condition.<br> — Example: Instead of `flag`, use a more descriptive name like `isFlagSet`.</p><p>5.<strong> Consistent Naming Conventions</strong>:<br> — Follow a consistent naming convention across your codebase.<br> — Example: If you use camelCase for variables (`isRunning`), stick to it consistently.</p><p>6. <strong>Use Question Form for Functions:</strong><br> — When dealing with functions returning boolean values, consider using a question form.<br> — Example: Instead of `validate()`, use `isValid()`.</p><p>7.<strong> Group-Related Booleans:</strong><br> — If you have multiple boolean values related to a specific functionality, group them with a common prefix.<br> — Example: `isLoading`, `isSuccessful`, `hasError`.</p><p>8. <strong>Avoid Ambiguity</strong>:<br> — Ensure that the name is not ambiguous and clearly represents the intended meaning.<br> — Example: Instead of `flag`, use a more specific name like `hasPermission`.</p><p>9. <strong>Consider Enumerations:</strong><br> — For multiple related boolean values, consider using enumerations or bit flags.<br> — Example: Instead of multiple boolean variables, use an enum like `Status { Pending, Approved, Rejected }`.</p><p>10. <strong>Update Names When Conditions Change</strong>:<br> — If the meaning or conditions change, update the variable name accordingly.<br> — Example: If the condition represented by `isActive` changes, update the name to reflect the new meaning.</p><p>Remember, the goal is to make your code easily understandable for both yourself and other developers who may work with your code.</p><p>Thanks a lot for reading this article. If you like it or have some suggestions, feel free to chip in via comments. Have a nice day!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed954fa9f3c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>