<?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 Japneet Singh Chawla on Medium]]></title>
        <description><![CDATA[Stories by Japneet Singh Chawla on Medium]]></description>
        <link>https://medium.com/@thedatasingh?source=rss-d28d05c13615------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EWZG1oTqqsF6s5lc8MczZA.jpeg</url>
            <title>Stories by Japneet Singh Chawla on Medium</title>
            <link>https://medium.com/@thedatasingh?source=rss-d28d05c13615------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:02:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thedatasingh/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[The Agentic War: When Two AI Agents Review Each Other’s Code and Nobody Reads It]]></title>
            <link>https://thedatasingh.medium.com/the-agentic-war-when-two-ai-agents-review-each-others-code-and-nobody-reads-it-868bcbb9a524?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/868bcbb9a524</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai-agent]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 18:34:27 GMT</pubDate>
            <atom:updated>2026-11-17T18:34:27.049Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bSOJ33eUlou9JIVK7bi32g.png" /></figure><h3>Agentic coding is powerful. Agentic coding without a human in the loop is a quiet risk.</h3><p>Over the last three or four months, I’ve noticed a new pattern in how code gets written and reviewed. I’ve started calling it <strong>the agentic war</strong>.</p><p>Let me be clear up front: I’m firmly in favour of agentic coding, agentic testing and everything that comes with it. I use agents every day. This isn’t a post against AI. It’s about a specific way of using it that worries me.</p><h3>What the agentic war looks like</h3><p>It goes something like this.</p><ol><li><strong>A developer writes code with an agent.</strong> They don’t fully understand what was written or how it works, but it looks right, so they raise a PR.</li><li><strong>The reviewer runs an agent on the PR.</strong> The agent reads the code and leaves comments.</li><li><strong>The developer runs an agent on the comments.</strong> The prompt is something like <em>“Get all the comments from this PR and fix them.”</em> Nobody checks whether the comments were valid in the first place.</li><li><strong>Even the communication is automated.</strong> The “Fixed, please re-review” message on Slack is written and sent by the agent, with no human involved.</li><li><strong>The reviewer runs the agent again.</strong> And the loop continues.</li></ol><p>On paper, this is a fully autonomous system: code written, reviewed, fixed and approved with no human intervention.</p><p>In practice, it’s two agents talking to each other while the humans who are supposed to own the work watch from the sidelines.</p><h3>Why it’s a problem</h3><h3>1. Hallucinations go unchecked</h3><p>Agents can be confidently wrong. If the reviewing agent flags a problem that doesn’t exist, or suggests a “fix” that misreads the system, the coding agent will happily implement it. Nobody stops to ask: <em>Was that comment actually right?</em></p><p>The validation step, the most important part of a code review, quietly disappears.</p><h3>2. The PR drifts away from its purpose</h3><p>Every PR exists for a reason: a requirement, a bug, a decision the team discussed. After a few rounds of unverified comments and automatic fixes, the code can slowly drift away from that purpose. Each change looks reasonable on its own. Together, they can turn into something nobody asked for.</p><h3>3. Nobody owns the context</h3><p>This is the risk that worries me most.</p><p>When something breaks in production, during an incident, an outage or any emergency, you need people who understand the code: what it does, why it was written that way, and what rules and policies it enforces.</p><p>In the agentic war, nobody has that context. The developer didn’t really write it. The reviewer didn’t really review it. So when it fails, people are left trying to understand the system in the middle of an incident, which is the worst possible time to learn.</p><h3>The fix: keep a human in the loop</h3><p>The answer isn’t to stop using agents. It’s to stop handing them ownership.</p><p>You don’t need to write every line yourself. But you do need to be in a position to:</p><ul><li><strong>Understand what’s being written</strong>, even if you aren’t writing it.</li><li><strong>Guide the agent</strong>, and use it to explore the unknowns in the codebase rather than skip past them.</li><li><strong>Validate every review comment</strong> before accepting a fix, whichever side of the PR you’re on.</li><li><strong>Bring your own judgement.</strong> Use your problem-solving and your knowledge of the system to choose the best approach, then let the agent implement it.</li></ul><p>As a reviewer, that means actually reading what your agent flagged and deciding whether it matters. As an author, it means questioning each comment before you let an agent “fix” it.</p><blockquote><em>Agents should do the work. Humans should still own it.</em></blockquote><h3>Summing up</h3><p>Agentic development is one of the biggest productivity shifts our industry has seen. But a loop of agents writing, reviewing and fixing each other’s work isn’t productivity. It’s a system with no owner.</p><p>The teams that get the most out of AI won’t be the ones that remove humans from the loop. They’ll be the ones where humans stay in the loop as the people who understand, decide and take responsibility.</p><p><em>Have you seen the agentic war on your team? I’d love to hear how you’re handling it in the comments.</em></p><p>Let’s connect on LinkedIn: <a href="https://www.linkedin.com/in/japneet-singh-chawla/">https://www.linkedin.com/in/japneet-singh-chawla/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=868bcbb9a524" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agents Made Development Faster. They Made Managing It Harder.]]></title>
            <link>https://thedatasingh.medium.com/agents-made-development-faster-they-made-managing-it-harder-4f84e7b05bfb?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f84e7b05bfb</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 06:45:51 GMT</pubDate>
            <atom:updated>2026-11-16T06:45:51.939Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c_7p2P4sWL_90fKMgPws4w.png" /></figure><h3>The new problems engineering managers face in the agentic era. Part 2 of a series.</h3><p>In <a href="https://claude.ai/artifact/BcqXhYzRQM8G6CNPpy9bXf">Part 1</a>, I wrote about how agentic development has flipped the software development life cycle. The stages are the same: plan, develop, test, deploy. But writing code is now the fastest part, and the time has moved into planning, specs and review.</p><p>That was the developer’s view. This part is about the manager’s.</p><p>If development has become this fast, you might expect managing it to get easier too. In my experience, it hasn’t. The problems have changed, and some of the new ones are harder to spot than the old ones.</p><h3>How requirements used to work</h3><p>It used to be a fairly linear process. Managers and senior people, who understood at a high level how things should work, gathered requirements. Those requirements were usually broad, so someone did the exploration, and from that came a concrete set of requirements for the feature.</p><p>The process still exists. What’s changed is who does each step, and how easy it is to skip understanding along the way.</p><h3>Challenge 1: The agentic war</h3><p>Here’s a pattern I’m seeing more often.</p><p>An agent writes the spec. The manager, who is also using agents now, hands that spec to a different agent for review. The reviewing agent comments, the writing agent revises, and the spec gets “approved”.</p><p>Two agents have just talked to each other, and nobody in the loop actually understands what we’re trying to build.</p><p>It’s fully agentic, and it feels productive. But it fails badly the moment the real requirement was misunderstood, because the spec is now confidently describing something nobody wanted.</p><blockquote><em>If you can’t explain the spec without your agent, you haven’t reviewed it.</em></blockquote><p>Once a spec exists, a manager’s job is to keep a sharp eye on what is wrong with it and what could go wrong. Agents can help with that. They can’t do the understanding for you.</p><h3>Challenge 2: The optimism trap in planning</h3><p>Because development is now so fast, there’s a quiet assumption creeping into planning: AI will help with development, testing and everything else, so everything will take less time.</p><p>That assumption leads us to underestimate effort. Plans get tight, and teams end up running neck and neck with their deadlines, where anything unexpected becomes a slip.</p><p>AI makes the work faster. It doesn’t make it free. Specs still need thinking, reviews still need attention, and integration with existing systems still surprises people. <strong>Always keep a real buffer.</strong></p><h3>Challenge 3: Slips show up early, if you’re looking</h3><p>There is a useful side to this. Because so much of the work happens quickly, problems surface early.</p><p>If an item is planned for seven days, you’ll usually know within the first two whether it’s going to stretch. The agent either got through the core of it or it didn’t.</p><p>That changes what good management looks like. Managers who check in early can re-plan, re-scope or unblock while there’s still time. Managers who wait for the deadline find out when it’s too late to do anything about it.</p><h3>Challenge 4: Reviewing the approach, not just the code</h3><p>Managers can, and should, use agents to help review the code their teams produce. It’s a good first pass.</p><p>But I still believe a human look at the code, and especially at the approach, is critical. An agent will tell you whether the code does what the spec says. It’s much less likely to ask whether this was the right way to solve the problem.</p><p>So as a manager, ask:</p><ul><li>Is this the right approach for our system, not just a working one?</li><li>What other ways could this problem have been solved?</li><li>What does this choice make harder for us six months from now?</li></ul><p>Agents answer the question you ask. Managers have to ask whether it was the right question.</p><h3>Challenge 5: Learning speed is the new moat</h3><p>There are two ways to use AI, for managers and engineers alike.</p><p>The first is to dump your questions into it and wait for answers. The second is to treat it as an assistive partner, something that helps you explore further, dig deeper into requirements, run competitor analysis and test your assumptions.</p><p>The first gets you answers. The second gets you understanding.</p><p>The advantage no longer goes to whoever asks the most questions or gets answers fastest. It goes to whoever <strong>learns</strong> fastest. For managers, that’s what lets you catch a weak spec, spot an optimistic plan or question an approach before it ships.</p><h3>Summing up</h3><p>Agentic development didn’t remove the manager’s job. It moved it.</p><p>Less of it is tracking whether code is getting written. More of it is understanding the real requirement, planning honestly with a buffer, noticing slips early and judging whether the approach is right. Those are exactly the parts that are hardest to hand to an agent, and the parts where an agent-only workflow fails most quietly.</p><p><em>Managers, what new challenges have you run into since your teams went agentic? Tell me in the comments.</em></p><p>Let&#39;s connect on LinkedIn: <a href="https://www.linkedin.com/in/japneet-singh-chawla/">https://www.linkedin.com/in/japneet-singh-chawla/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f84e7b05bfb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The SDLC Didn’t Change. Where We Spend Our Time Did.]]></title>
            <link>https://thedatasingh.medium.com/the-sdlc-didnt-change-where-we-spend-our-time-did-0da214bfe11a?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/0da214bfe11a</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[ai-agent]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 13:13:51 GMT</pubDate>
            <atom:updated>2026-11-13T13:13:51.546Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/554/1*u9b-Rh61Y1QkDlDNBTFCXw.jpeg" /></figure><p><em>How AI agents moved the work out of development and into planning and review. Part 1 of a series.</em></p><p>If you drew the software development life cycle today, it would look the same as it did five years ago: plan, develop, test, deploy. The stages haven’t moved.</p><p>What has moved, and sharply, is who does the work in each stage and how long each one takes.</p><p>I’m a Director of Engineering at TestMu AI (formerly LambdaTest), where I look after our grid platforms, including HyperExecute. Over the past year I’ve watched my teams’ day-to-day work change more than it did in the previous decade. This is Part 1, about <strong>development</strong>. In Part 2, I’ll write about how AI is changing the way engineering is <strong>managed</strong>.</p><h3>How it used to work</h3><p>For most of my career, development was the main event.</p><p>We’d spend some time planning what a feature should look like and how it should behave. Then engineers would spend most of the cycle building it. When a change spread across several services, the complexity grew fast and the effort grew with it. Testing, release and deployment followed, but the SDLC was built around development.</p><h3>How it works now</h3><p>Today most of those stages are agent-driven. Development has shrunk to the shortest part of the cycle, and the time has moved upstream into <strong>planning and spec preparation</strong>.</p><h3>The RFC is the new interface</h3><p>An RFC used to be a document for other engineers. Now it’s also how you instruct your agent: what to build, what the expectations are and what outcome you want to see.</p><p>Once you have a well-defined spec covering what you want and how it should be built, you hand it to an agent that has access to all the repositories you work on, and it writes the code. What comes back is only as good as what you put in. A vague spec gives you vague code.</p><h3>Exploring unknown code is no longer a superpower</h3><p>For the past two or three years we talked a lot about the 10x or 100x engineer, someone who could find their way through an unfamiliar codebase and quickly see what a change would and wouldn’t affect.</p><p>That advantage has largely gone. Anyone can now run an agent, explore the unknown parts of a codebase and map the impact of a change. And if you build a self-improving loop around your agent, it keeps getting better the more you use it.</p><h3>The hardest part is now review</h3><p>Once the agent has written the code, we reach what I think is now the most challenging stage. I see two kinds of engineers here.</p><p><strong>The first kind follows the agent blindly.</strong> The code compiles, the checks pass, and they move on without really understanding what was written.</p><p><strong>The second kind reads the code</strong>, works to understand it and asks whether it could be better.</p><p>I’m firmly in the second group. I regularly review code written by the different agents my teams use. Agents are on their own iterative learning journey, and they do learn from their mistakes, but I still find code that needs reworking. Most of the time the root cause goes back to the spec: while generating the code, the agent made implementation decisions that didn’t match what was really intended.</p><p>If you don’t review the code, you often won’t notice those flaws.</p><h3>New code vs. existing code</h3><p>In a brand-new codebase this matters less. Everything is new, everything gets tested, and any flaws come up and get fixed.</p><p>In an <strong>existing codebase</strong> it’s a different story. When you’re adding a feature to code that carries years of assumptions, implementation choices can make or break other parts of the system. One quiet decision can break something three services away. That’s where careful review stops being optional.</p><h3>Testing: catching up fast</h3><p>Testing still needs a lot of manual effort, but that’s changing quickly, and AI agents are now a real part of it.</p><p>Full disclosure: this is a space we build in. At TestMu AI we’ve built <a href="https://www.testmuai.com/kane-ai/">KaneAI</a>, an end-to-end testing agent for web and mobile, and <a href="https://github.com/LambdaTest/kane-cli">Kane CLI</a>, which brings it to the terminal. You describe a user journey in plain English, the agent runs it in a real browser or on a real device, checks the result, and helps you build test cases you can use to test your product end to end. It’s designed to be used by human developers and by AI coding agents.</p><p>The point isn’t any one tool. Once agents write code this fast, verification has to keep up, and that’s where testing is going.</p><h3>Deployment: a human stays in the loop</h3><p>Deployment is where AI has moved most slowly, and for good reason.</p><p>Most companies don’t yet have AI-driven deployment pipelines. Production is where organisations are most careful about what changes go out. Even where agents and automation are built into the pipeline, there’s still a human in the loop, and usually several people involved. I think that caution is right.</p><h3>Summing up</h3><p>The stage that used to take the most time in feature development, writing the code, now takes the least.</p><p>The new bottlenecks are clear thinking before the code is written and honest review after it. The engineers who do well in this era won’t be the fastest at typing or the best at digging through old code. They’ll be the ones who write the sharpest specs and still read the code.</p><p>In Part 2, I’ll look at the other side: how AI is changing the way engineering work is managed.</p><p><em>Which kind of engineer are you, the one who trusts the agent or the one who reads every line? I’d love to hear in the comments.</em></p><p><strong>Links</strong></p><ul><li>My LinkedIn Profile: <a href="https://www.linkedin.com/in/japneet-singh-chawla/">https://www.linkedin.com/in/japneet-singh-chawla/</a></li><li><a href="https://www.testmuai.com/kane-ai/">KaneAI: end-to-end testing agent</a></li><li><a href="https://github.com/LambdaTest/kane-cli">Kane CLI on GitHub</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0da214bfe11a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The “How” Is Solved. Now Comes the Hard Part.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://thedatasingh.medium.com/the-how-is-solved-now-comes-the-hard-part-fc567a5ef8c2?source=rss-d28d05c13615------2"><img src="https://cdn-images-1.medium.com/max/940/1*zn8zKuLwcKUNAqnfor-E8g.png" width="940"></a></p><p class="medium-feed-snippet">AI didn&#x2019;t kill engineering skill. It moved it &#x2014; and most people are still looking in the old place.</p><p class="medium-feed-link"><a href="https://thedatasingh.medium.com/the-how-is-solved-now-comes-the-hard-part-fc567a5ef8c2?source=rss-d28d05c13615------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://thedatasingh.medium.com/the-how-is-solved-now-comes-the-hard-part-fc567a5ef8c2?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc567a5ef8c2</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 07:07:40 GMT</pubDate>
            <atom:updated>2026-08-27T07:07:40.968Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Zero Lag, Total Silence: Debugging a Kafka Partition That Quietly Died]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://thedatasingh.medium.com/zero-lag-total-silence-debugging-a-kafka-partition-that-quietly-died-463908bbd8f1?source=rss-d28d05c13615------2"><img src="https://cdn-images-1.medium.com/max/940/1*llFnbs84iGWBbXKSCLXokQ.png" width="940"></a></p><p class="medium-feed-snippet">How a batch of messages vanished for days while every dashboard stayed green &#x2014; and what working alongside an AI taught me about where&#x2026;</p><p class="medium-feed-link"><a href="https://thedatasingh.medium.com/zero-lag-total-silence-debugging-a-kafka-partition-that-quietly-died-463908bbd8f1?source=rss-d28d05c13615------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://thedatasingh.medium.com/zero-lag-total-silence-debugging-a-kafka-partition-that-quietly-died-463908bbd8f1?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/463908bbd8f1</guid>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[kafka]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Tue, 25 Aug 2026 13:37:58 GMT</pubDate>
            <atom:updated>2026-08-25T13:37:58.618Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Screen Resolution and Cypress]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://thedatasingh.medium.com/screen-resolution-and-cypress-15fb91ff7ac?source=rss-d28d05c13615------2"><img src="https://cdn-images-1.medium.com/max/2090/1*LT-Qfr5gyHp8cZ90hKqvLg.jpeg" width="2090"></a></p><p class="medium-feed-snippet">Testing Web Application in different resolution with Cypress</p><p class="medium-feed-link"><a href="https://thedatasingh.medium.com/screen-resolution-and-cypress-15fb91ff7ac?source=rss-d28d05c13615------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://thedatasingh.medium.com/screen-resolution-and-cypress-15fb91ff7ac?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/15fb91ff7ac</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[cypress-testing]]></category>
            <category><![CDATA[testing-framework]]></category>
            <category><![CDATA[cypress]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Tue, 06 Dec 2022 13:12:51 GMT</pubDate>
            <atom:updated>2026-08-27T07:10:40.244Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Life of a Software Engineer- 23, Dec 2021]]></title>
            <link>https://thedatasingh.medium.com/life-of-a-software-engineer-23-dec-2021-60ee98846849?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/60ee98846849</guid>
            <category><![CDATA[life-of-a-programmer]]></category>
            <category><![CDATA[the-data-singh]]></category>
            <category><![CDATA[cypress]]></category>
            <category><![CDATA[personal-journal]]></category>
            <category><![CDATA[rackspace]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Thu, 23 Dec 2021 18:47:21 GMT</pubDate>
            <atom:updated>2021-12-23T18:47:21.192Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey Reader,</p><p>If you are following my blogs for past few days you must be aware of the work I am involved with nowadays,</p><p>I am very excited about moving this work to prod and this was not an easy task.</p><p>There is one realization that I have with all the big tasks that I get, In the beginning, everything looks very tough and hard to achieve, and gradually when you start working on the tasks, things start to unfold and you gain more and more confidence in yourself that you can do it.</p><p>This strange thing happens to me every time I start a big project.</p><p>Today, we had to set up our code on pre-prod and most of the time was spent in management and setup tasks.</p><p>With every hiccup that we faced in the dev testing process, we unveiled a new flow that we didn’t think about, this might be an example of bad management and planning or a classic problem with maintaining the old projects, all of these flows were related to the old product.</p><p>Do let me know what are your thought on this.</p><p>Today was a successful day with the QA team testing our new architecture and we have seen a decrease of 50–60% execution time. This will be a great milestone towards becoming the fastest remote cypress provider.</p><p>Stay tuned with me to know more about my journey.</p><p>Thanks for reading and do connect with me on <a href="https://www.linkedin.com/in/japneet-singh-chawla/">LinkedIn</a> and <a href="https://www.youtube.com/c/TheDataSingh">YouTube</a>.</p><p>The Data Singh</p><p>Also, check out my video on cracking Rackspace interview</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FWwSWbiZJ8dk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DWwSWbiZJ8dk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FWwSWbiZJ8dk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d4c3bd365c6179a38cccf3386a6cd8f7/href">https://medium.com/media/d4c3bd365c6179a38cccf3386a6cd8f7/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60ee98846849" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life of a Software Engineer 22, Dec 2021]]></title>
            <link>https://thedatasingh.medium.com/life-of-a-software-engineer-22-dec-2021-64b0e7ba88e5?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/64b0e7ba88e5</guid>
            <category><![CDATA[personal-journal]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[life-of-a-programmer]]></category>
            <category><![CDATA[product-based-companies]]></category>
            <category><![CDATA[life-of-an-engineer]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Thu, 23 Dec 2021 06:09:03 GMT</pubDate>
            <atom:updated>2021-12-23T06:09:03.858Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey Reader,</p><p>Yesterday I forgot to write my blog, so I decided to do it first thing in the morning before starting my work.</p><p>Yesterday was a busy day, we finally launched the new architecture on our staging environment.</p><p>Believe me, the bookish things and documentation don’t teach you things that real-life problem-solving will.</p><p>I have learned so many things in a course of a year about system design and how to handle different real-life situations in a product.</p><p>One thing that I have learned from all my experience is, you can never make a solid product, you make something according to the current needs and demands and then you evolve with the market, If you are not evolving with time, you will be left behind.</p><p>Take the example of Google, it has evolved so much with time, it has discontinued its products like Hangouts, Duo, etc which people didn’t use the evolved these into google meet and the ease of its integration with Google accounts has made it more usable.</p><p>This is true for almost all software products.</p><p>My initial results with this architecture are very interesting and we have seen a drop of around 50% in the execution time.</p><p>This is a milestone for our offering, lets see how customers perceive this advancement in the product.</p><p>I am going on a long vacation and lets see if I could write blogs during the journey.</p><p>Do follow me on <a href="https://www.linkedin.com/in/japneet-singh-chawla/">Linkedin</a>, <a href="https://www.youtube.com/channel/UCmi_UhOOIpp4gZJ3zrOGq7A">YouTube</a> and Medium for more digital Content.</p><p>Thanks for reading,</p><p>See you tomorrow</p><p><strong>The Data Singh</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FOChIRaTkuYw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DOChIRaTkuYw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FOChIRaTkuYw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/37870f5b81755e8614ce1f5e10d3afbe/href">https://medium.com/media/37870f5b81755e8614ce1f5e10d3afbe/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64b0e7ba88e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life of a Software Engineer 21, Dec 2021]]></title>
            <link>https://thedatasingh.medium.com/life-of-a-software-engineer-21-dec-2021-5ccd907d2ea5?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ccd907d2ea5</guid>
            <category><![CDATA[life-of-a-programmer]]></category>
            <category><![CDATA[life-of-software-engineer]]></category>
            <category><![CDATA[personal-journal]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Tue, 21 Dec 2021 20:22:27 GMT</pubDate>
            <atom:updated>2021-12-21T20:22:27.533Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey Readers,</p><p>Today was a very very hectic day. Waking up early in the morning is becoming more struggling every day due to a dip in temperature in Delhi.</p><p>Covid has shaken up the world and also the lives of engineers, we were lazy by birth but when you can wake up, open your laptop in bed and start working, why will you come out of bed.</p><p>I hope you are getting my sarcastic tone :P</p><p>My gym is going fine and I have completed the target of losing 250 grams in the last week.</p><p>Having done that I gifted myself some sweets. Sweets are something I can not resist and this is the one thing that has always helped me gain more weight.</p><p>Do tell me one thing which you can never resist.</p><p>Anyways, I feel good that I am able to maintain at least 4 days a week on my gym training.</p><p>Today I had an interview, I interviewed a candidate for SDE position and it went well, he was a new guy in it industry and had a good knowledge base.</p><p>It always feels good to know more people and understand what problem they are solving using the latest tech.</p><p>I have met so many people in past years but today one thing that was surprising was that the candidate knew me and knew The Data Singh.</p><p>It was a proud moment.</p><p>This has given me the motivation to work even harder on the different aspects of my life (Work and personal).</p><p>Let&#39;s see how long this continues.</p><p>I hope you are enjoying reading my blog every day.</p><p>Stay tuned with me to know more about my journey.</p><p>Thanks for reading and do connect with me on <a href="https://www.linkedin.com/in/japneet-singh-chawla/">LinkedIn</a> and <a href="https://www.youtube.com/c/TheDataSingh">YouTube</a>.</p><p>The Data Singh</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4hdDf9IPYeY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4hdDf9IPYeY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4hdDf9IPYeY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d0e098eb2b30350140afaee947b94fe/href">https://medium.com/media/2d0e098eb2b30350140afaee947b94fe/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ccd907d2ea5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life of a Software Engineer- 20, Dec 2021]]></title>
            <link>https://thedatasingh.medium.com/life-of-a-software-engineer-20-dec-2021-e396efe74bf4?source=rss-d28d05c13615------2</link>
            <guid isPermaLink="false">https://medium.com/p/e396efe74bf4</guid>
            <category><![CDATA[tech-lead]]></category>
            <category><![CDATA[the-data-singh]]></category>
            <category><![CDATA[life-of-software-engineer]]></category>
            <category><![CDATA[software-engineer]]></category>
            <category><![CDATA[life-of-a-programmer]]></category>
            <dc:creator><![CDATA[Japneet Singh Chawla]]></dc:creator>
            <pubDate>Mon, 20 Dec 2021 19:21:51 GMT</pubDate>
            <atom:updated>2021-12-20T19:21:51.564Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey Readers,</p><p>Hope you are doing well, I have very exciting news for you all. Today we tested our new architecture after fixing all the bugs in the happy flow.</p><p>You must be wondering what happy flow is !!!</p><p>Happy Flow is the base flow wherein the user interacts with the system in an expected way and all the services react in an expected manner.</p><p>We are 2 days behind the schedule but this was expected as we had to deliver some features while developing the new architecture.</p><blockquote>Choosing between New Features and Product Stability is a strong War, which is always won by the customers.</blockquote><p>If this is not the case with your company you should rethink your branch and company stratergy.</p><p>Again these are my thoughts and I don’t enforce my thoughts on anyone.</p><p>I have one of the longest calls of my WFH tenure, I went on a call with my colleague at 12:00 in the morning and we were on call until 7:30 with some breaks in between.</p><p>But the end result was a success and I am personally very happy. I know there will be many hiccups which I will have to fix tomorrow and I am confident that I will do that.</p><p>For an Engineer, there is no bigger happiness than taking their code to production.</p><p>And I am no different.</p><p>My today’s day was more or less revolved around making things work for us and a couple of days are going to be like that only.</p><p>Stay tuned with me to know more about my journey.</p><p>Thanks for reading and do connect with me on <a href="https://www.linkedin.com/in/japneet-singh-chawla/">LinkedIn</a> and <a href="https://www.youtube.com/c/TheDataSingh">YouTube</a>.</p><p>The Data Singh</p><p>Also, check out my latest video</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FjCPLf5eXcDo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DjCPLf5eXcDo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FjCPLf5eXcDo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f44dab2e0166ea552d67e9cd354ddddb/href">https://medium.com/media/f44dab2e0166ea552d67e9cd354ddddb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e396efe74bf4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>