<?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 Parth Makawana on Medium]]></title>
        <description><![CDATA[Stories by Parth Makawana on Medium]]></description>
        <link>https://medium.com/@parthmakawana?source=rss-47a1c64319b7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*HD6rdp6_Q_P6AZWQ-ERg2w.jpeg</url>
            <title>Stories by Parth Makawana on Medium</title>
            <link>https://medium.com/@parthmakawana?source=rss-47a1c64319b7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:02:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@parthmakawana/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[Stop the Microservices Madness: You don’t have a Monolith problem, you have a Design problem.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://parthmakawana.medium.com/stop-the-microservices-madness-you-dont-have-a-monolith-problem-you-have-a-design-problem-c2fcf80bb054?source=rss-47a1c64319b7------2"><img src="https://cdn-images-1.medium.com/max/1536/1*UDRJFu9FFcOphGgOebfqRw.png" width="1536"></a></p><p class="medium-feed-snippet">If every scalability discussion ends with &#x201C;let&#x2019;s split into microservices,&#x201D; there is a good chance you are optimising the wrong thing&#x2026;</p><p class="medium-feed-link"><a href="https://parthmakawana.medium.com/stop-the-microservices-madness-you-dont-have-a-monolith-problem-you-have-a-design-problem-c2fcf80bb054?source=rss-47a1c64319b7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://parthmakawana.medium.com/stop-the-microservices-madness-you-dont-have-a-monolith-problem-you-have-a-design-problem-c2fcf80bb054?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2fcf80bb054</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-design]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Mon, 23 Feb 2026 13:53:10 GMT</pubDate>
            <atom:updated>2026-02-23T18:34:54.504Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Striking a Balance: The Pitfalls of a “Product-Heavy” Organization]]></title>
            <link>https://medium.com/codex/striking-a-balance-the-pitfalls-of-a-product-heavy-organization-fa824c96f2bc?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa824c96f2bc</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Tue, 05 Sep 2023 11:36:12 GMT</pubDate>
            <atom:updated>2023-10-31T12:14:13.054Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZOeqcmNI5tzBgwrA" /><figcaption>Photo by <a href="https://unsplash.com/@sebastien_bonneval?utm_source=medium&amp;utm_medium=referral">Sebastien Bonneval</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>With Agile Methodology, there came several different roles that did not exist earlier, Like Scrum Master, Product Owner etc. If the organisation is following <a href="https://medium.com/codex/are-you-using-agile-or-lipstick-agile-9daa68280963">Lipstick Agile</a>, with increasing roles and people, teams gradually get divided into internal groups. Two of the most prominent groups are the “Product Team” which comprises “Business Driven Roles” like Product Manager and Product Owner etc. and The “Development Team” which comprises “Technical Driven Roles” Like Tech Lead, Developers and QAs.</p><p>These teams, with their unique skill sets and perspectives, work in tandem to bring innovative products to life. However, a common organizational pitfall is leaning too heavily towards one side, where the product team gains significant authority without possessing a deep understanding of the product itself. In this article, we’ll delve into the disadvantages of a product-heavy organization and explore why striking a balance between these two critical functions is essential for success.</p><h4>1. Misalignment of Priorities</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iEjoskAVkjWsHFk9" /><figcaption>Photo by <a href="https://unsplash.com/@2mduffel?utm_source=medium&amp;utm_medium=referral">Mark Duffel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In a product-heavy organization, the product team often sets the agenda. However, when they lack a profound understanding of the product’s technical intricacies, they may inadvertently set priorities that don’t align with the development team’s capabilities or the product’s actual needs. This misalignment can lead to conflicts, inefficiencies, and wasted resources.</p><p>Not just the Misalignment of the priorities, the ill-understood product team can frequently shuffle the priorities leaving the development team puzzled and distracted.</p><h4>2. Lack of Technical Feasibility</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_jNReXmI6AFeU2ef" /><figcaption>Photo by <a href="https://unsplash.com/@ayeltvanveen?utm_source=medium&amp;utm_medium=referral">Ayelt van Veen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A Product-Heavy organisation often shoves the requirements down to the throat of the development team without including them in the initial discussion and feasibility check.</p><p>Imagine a scenario where the product team proposes features or changes that sound fantastic in theory but are technically challenging or impossible to implement. This situation can be a recipe for frustration and project delays as the development team grapples with unrealistic expectations.</p><h4>3. Inefficient Resource Allocation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d0ufv49JyeJHbYtK" /><figcaption>Photo by <a href="https://unsplash.com/@frantic?utm_source=medium&amp;utm_medium=referral">Alex Kotliarskyi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>One of the consequences of a product-heavy approach is that resources might be inefficiently allocated. The product team’s decisions, driven by their limited product knowledge, may result in the development team spending valuable time and effort on tasks that don’t provide substantial value to the product or its users. Manier times, the development team gets disturbed by unnecessary and unprioritised investigation items which doesn’t add any business value to the overall product.</p><h4>4. Communication Challenges</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0SjpFaLOywk6NQhl" /><figcaption>Photo by <a href="https://unsplash.com/@lunarts?utm_source=medium&amp;utm_medium=referral">Volodymyr Hryshchenko</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Effective communication is the lifeblood of any successful project. However, When a product is product-heavy, It happens that the product team communicates the things that they have no clue about. Especially when the product team doesn’t bother to connect with the development team on the subject matter. Most of the issues go back and forth and never get resolved.</p><h4>5. Increasing backlog but reduced throughput</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mZVu0l9HAKokuinK" /><figcaption>Photo by <a href="https://unsplash.com/@sharonmccutcheon?utm_source=medium&amp;utm_medium=referral">Alexander Grey</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A primary goal of the product team is to generate a backlog of features for the development team to work on, It may so happen that the ill-informed product team start putting things on backlog understanding which development team may go crazy.</p><p>Increased importance on lining up the backlog items, creating n+x sprints, showcasing roadmaps without any technical feasibility or use case etc. can stack up backlog to a certain level where the development team may fail to cope.</p><h4>6. Slow Decision-Making</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pzFDEeiYQ54aX-9R" /><figcaption>Photo by <a href="https://unsplash.com/@danielmingookkim?utm_source=medium&amp;utm_medium=referral">Daniel Mingook Kim</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Since the product team does not have in-depth knowledge of things on hand, It so happens that those things on hand become the victim of procrastination. And most of the time this happens when some critical decision is required. since the product team lacks a deep understanding of the market and product, It relies on external inputs to make the decision which oftentimes is time-consuming and most of the time, misleading.</p><h4>7. Reduced Employee Morale</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*88bEFGPxjiz2Mp5u" /><figcaption>Photo by <a href="https://unsplash.com/@dre0316?utm_source=medium&amp;utm_medium=referral">Andre Hunter</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When developers feel their expertise and insights are undervalued, morale can take a nosedive. Disheartened team members are less likely to give their best, which can lead to high turnover rates and create a negative work environment.</p><p>In addition, all the other points mentioned here, like communication issues, Misplaced priorities etc. make the development team wonder why they are in such a puzzling situation which gradually frustrates both the product and development team.</p><h4>8. Risk of Overpromising</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8pbkL7mUSEtxWyC8" /><figcaption>Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=medium&amp;utm_medium=referral">Brett Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Working directly with customers and the operation support team, the product team generally deals with the most critical part of business functions. However, Under pressure to thrive in business or rather in fear of getting out of business, the product team sometimes over-commits many features that may be impossible for the development team to achieve.</p><p>A product team without a firm grasp of development constraints might unintentionally overpromise on delivery timelines or product capabilities. This can lead to disappointment among stakeholders and damage the organization’s credibility.</p><h4>9. Quality, Technical and Innovation Debt</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EMy6h6NHETVuufRi" /><figcaption>Photo by <a href="https://unsplash.com/@ameenfahmy?utm_source=medium&amp;utm_medium=referral">ameenfahmy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The product-heavy organisations focus more on rapid feature development. Frequent releases and fail-fast approach. However, In pursuit of rapid feature development, they might inadvertently compromise code quality. Without the necessary technical oversight, technical debt can accumulate, making future development more challenging and costly.</p><p>Innovation often emerges from the crossroads of technical expertise and creative thinking. A product-heavy approach that sidelines technical knowledge can stifle innovation. The development team, immersed in the nuts and bolts of the product, may be better positioned to identify new technologies or solutions that could enhance it. Without their input, valuable ideas may go unnoticed.</p><h4>10. False sense of hunky-dory</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*81Nsf5_iCfDM5sBP" /><figcaption>Photo by <a href="https://unsplash.com/@victor_g?utm_source=medium&amp;utm_medium=referral">Victor</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>With all the frustration, and complexities, the development team slowly burns down, but being the product-heavy organisation, rather than addressing the key issues of the development team, most of the time, the product team comforts stakeholders with a completely false sense of hunky-dory whose bubble may eventually get burst, leaving only ashes.</p><h4>Conclusion</h4><p>In the complex dance of product development, balance is critical. A product-heavy organization can face a myriad of disadvantages, from misaligned priorities to reduced innovation and employee morale. Organizations must foster collaboration, communication, and mutual respect between their product and development teams to navigate these pitfalls successfully. Additionally, investing in training and knowledge sharing can bridge the gap, ensuring that both sides work harmoniously to deliver exceptional products. By striking the right balance, organizations can set themselves up for success in a competitive marketplace where innovation and efficiency are paramount.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa824c96f2bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/striking-a-balance-the-pitfalls-of-a-product-heavy-organization-fa824c96f2bc">Striking a Balance: The Pitfalls of a “Product-Heavy” Organization</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hey, Gen Z workers, slow down…]]></title>
            <link>https://medium.com/codex/hey-gen-z-workers-slow-down-82d3b15a8846?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/82d3b15a8846</guid>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[millenials]]></category>
            <category><![CDATA[gen-z]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Fri, 05 Aug 2022 11:52:20 GMT</pubDate>
            <atom:updated>2022-08-08T14:14:51.182Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tcjjvUaUUn5wFird" /><figcaption>Photo by <a href="https://unsplash.com/@lucarinigiac?utm_source=medium&amp;utm_medium=referral">Giacomo Lucarini</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s been some time since Zoomers or say GenZ’s have started making it into the mainstream corporate. And being a late Millenial who has worked under boomers and early Millenials, and now mentoring the Zoomers, I can clearly point out a few behaviours of Gen Z workers which differs from Millenials. It includes good as well as bad traits.</p><h4>Some bad traits of Zoomers:</h4><ol><li>They tend to be over-energised and excited at starting something, and gradually lose interest over time.</li><li>Does everything in Hustle and Bustle without understanding the intention behind it or the bigger picture.</li><li>Considers themselves “Know It All” person.</li><li>Talks more and listens less, and adapts none.</li><li>Can be very blunt sometimes.</li><li>Learns everything, but doesn’t dive deep into anything. — Jack of all trades, Master of none.</li><li>Demands for “Want it all” from employers, are sometimes even unreasonable and unrealistic.</li></ol><h4>Some good traits of Zoomers:</h4><ol><li>If they keep their excitement intact, can achieve some incredible results.</li><li>Learns things quicker than Millenials.</li><li>Though they demand for “Want it all”, they are willing to “Give it all” from their side.</li><li>Their bluntness can sometimes be considered their reactiveness.</li></ol><p>Well, those were some observations by a Millenial of Zoomers, But does that mean these are true? Truth can be defined from statistics only. So let&#39;s get into some statistics.</p><h4>Statistics?</h4><p>I recommend you go through <a href="https://www2.deloitte.com/global/en/pages/about-deloitte/articles/genzmillennialsurvey.html">this</a> Deloitte report. But to summarize, below are the things which zoomers and millennials prefer from their potential employers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*218ZaL-Lrs-3C29V3N6BxQ.png" /></figure><p>It can be easily observed that Millenials look for Good Work/Life balance and a sense of meaning from work more than GenZs.</p><p>Psychologically, with no intention to find a sense of meaning either from a job, a hobby or life in general, people tend to get dissatisfied easily. And that’s also reflected in the report.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A6WMxRYqJvyw9YD1UAPnZQ.png" /></figure><p>It’s evident that GenZs tend to get stressed and burned out more than Millenials. there are several reasons for the same. Many of these are from the bad traits mentioned above like starting over-excited and in hustle and bustle but then losing interest over time.</p><p>And that stress results in something similar to Great Resignation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z90lUP5A_7A50g36Y7y2jg.png" /></figure><p>That doesn&#39;t imply that one should stick to the job he/she is unhappy about, but If you’re unhappy and stressed even after finding your “Happy Place”, There needs some soul searching.</p><p>The reason that great resignation may not end soon is that those participating in the great resignation, mainly GenZ and Late Millenials, They tend to be “Want it all” employees. And no organisation is generous enough to “Provide it all” to them. so they keep hopping here and there and keep increasing their stress.</p><h4>So that’s why I recommend Zoomers to slow down, breathe, observe, realise and adapt.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82d3b15a8846" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/hey-gen-z-workers-slow-down-82d3b15a8846">Hey, Gen Z workers, slow down…</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When an IT professional, becomes a “Resource”…..]]></title>
            <link>https://parthmakawana.medium.com/when-an-it-professional-becomes-a-resource-97954c9f74b3?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/97954c9f74b3</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Mon, 01 Aug 2022 08:52:45 GMT</pubDate>
            <atom:updated>2022-08-05T18:42:37.373Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qbEc8r_eLZVXb813" /><figcaption>Photo by <a href="https://unsplash.com/@weirick?utm_source=medium&amp;utm_medium=referral">Jake Weirick</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Humanity has witnessed and survived 4 different industrial revolutions—mechanisation, Mass Production, Automation and now Robotization.</p><p>The employees have evolved over time, however, the employees have been seen the same way for many years. During the first 2 revolutions, the employees were called the “Laborer”. The term basically relates to physical hardship done through working in the industry.</p><p>Then gradually through the 3rd and 4th revolutions, the physical hardship shifted to mental hardship, and the term “Laborer” started feeling like an insult to employees.</p><p>Especially IT companies have started to treat their employees who usually do mental hardship, with respect by calling them some dignified terms like Family, Community, Tribe, Pack etc.</p><p>However, organisations&#39; mindsets still remain in the industrial age and didn’t shift entirely to the information age. Though they’ve given the employees dignified terms like the one mentioned, many organisations still treat their employees like labourers. But just with a new term called “Resource”.</p><h4>What’s wrong with “Resource”?</h4><p>Well, Since the term “Resource” has become a replacement for the term “Laborer”, the mindset of employees and employers has gone back to the industrial age, where the employers considered employees as just a tool to get their work done and to be part of headcount.</p><p>When an employee becomes a “Resource”, there are several things that are set as a culture of an organisation by default:</p><ol><li>The employee merely stays as a headcount in the herd.</li><li>Employers prefer the quantity of work done by a “Resource” to quality.</li><li>Employers don’t focus on the personal and professional growth of a “Resource”</li><li>The employees neither feel part of something big or essential nor retain individual identity.</li><li>Employers see employees’ performance through the reports rather than being on the ground to see the reality.</li><li>The organisation starts becoming top-heavy and management-oriented.</li><li>Employees’ voices and concerns either go unheard or ignored.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_JC-FAC5gsrXphPH1yS4Q.gif" /></figure><h4><strong>What’s the solution?</strong></h4><p>Now that we know what’s wrong with considering an employee as a “Resource”, What could be the solution?</p><p>For starters, I barely mind calling employees by any suitable term, even “Resource” works fine if employees are treated with dignity and respect.</p><p>Certain things will make employees forget that they are a “Resource”:</p><ol><li>Freedom for employees to choose their career path and guide them on that path to achieve success. After all, an employee&#39;s success is indeed an organisation&#39;s success.</li><li>Frequently discuss the issues and concerns they have. And not just for formality like every other organisation does but create an action item for the same.</li><li>Let them be part of a bigger picture, decision making at the team level so that they can feel like being part of something big rather than working with the same old day-to-day tasks. The more minds get into something, the better it gets.</li><li>Find a way to measure the performance of employees on an individual level rather than via reports only. sometimes, Reports do not show the full picture. Get to know their strengths and weaknesses.</li><li>Prefer the quality of work done by individuals to quantity. because clients can be happy with fewer features with few issues than having more features with more issues.</li></ol><p>That’s all for now. Short and sweet!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97954c9f74b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What happened to “Javascript Killer” WebAssembly? Is it already dead?]]></title>
            <link>https://medium.com/codex/what-happened-to-javascript-killer-webassembly-is-it-already-dead-456cbadf101d?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/456cbadf101d</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[webassembly]]></category>
            <category><![CDATA[programming-languages]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Tue, 17 May 2022 09:04:11 GMT</pubDate>
            <atom:updated>2022-05-18T01:07:09.733Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Firnk_otGUnu2S-jj7XaRQ.jpeg" /></figure><p>Looking at the current technology market situation, the hype around Web3.0, Metaverse, Blockchain, AI, ML etc., reminds us of how rapidly the technology market changes. It is so rapidly evolving that technologies that we thought would be the future of the industry today, would disappear entirely from the industry a day after tomorrow.</p><p>We have so many examples of tech that were hyped for doom, many of them are either extinct or on the verge of extinction. Just a few of them are surviving. and merely a handful of them could thrive.</p><p>We’ll look back at one such hyped tech “Web Assembly” by answering What, Why and When:</p><p><strong>What is WebAssembly?</strong></p><p><strong>Why do we call it Hyped for doom?</strong></p><p><strong>When will it be dead?</strong></p><h3>What?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zg5wsYLJFxaGrHq3" /><figcaption>Photo by <a href="https://unsplash.com/@purzlbaum?utm_source=medium&amp;utm_medium=referral">Claudio Schwarz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>First, let us understand what is WebAssembly or WASM for short? Why did everyone think it would become a “Javascript Killer”?</p><p>Now, What is WebAssembly? If we go by the definition from its official <a href="https://webassembly.org/">website</a>, It states:</p><blockquote>WebAssembly (abbreviated <em>Wasm</em>) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications.</blockquote><p>Basically, It is a low-level, assembly-like language which gets stored in compact binary format so that it can give a near-native performance.</p><p>As mentioned in the definition, WASM was designed as a compilation target for other languages, allowing server-side code (such as C or C++ code) to be compiled into it and executed inside the browser.</p><p>It can let you code in any low-level programming language thus removing the barrier of understanding a particular programming language. It has native browser support so it is accepted across the browsers.</p><p>Imagine a non-web developer writing a piece of code in a non-web-compatible language using WASM and still being able to create amazing web apps that can run on browsers with near-native speed. That is the power of WASM and that was what’s promised.</p><blockquote>Now, It was never intended to crush out javascript in the first place, but to work alongside it and overcome its issues and boost its advantages.</blockquote><p>However, as I mentioned it was hyped to a general audience as a replacement for javascript, which is totally incorrect. People across the world started comparing it with javascript as if WASM was a rival to JS but in reality, WASM is a companion of JS and that’s where the tag “Javascript Killer” came into being.</p><p>The reason why people started comparing WASM with JS is that WASM promised to solve several issues that JS has like Security issues, Cross-platform support, Improved speed, Improved Debugging, and Garbage collection to name a few.</p><p>But did it deliver on that promise? Let’s find out in my next section.</p><h3>Why?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8-mPhui8H9NeHdXr" /><figcaption>Photo by <a href="https://unsplash.com/@77hn?utm_source=medium&amp;utm_medium=referral">The 77 Human Needs System</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Now, Why did we call WASM, hyped for doom? Is it because it did not deliver on its promises? Well, partially, YES!!!</p><p>The promises it delivered are Faster and easy coding, cross-platform development, and biggest of all, Improved performance.</p><p>It does deliver faster and easy coding as it allows developers to write the code in their native programming language so little or no training and exercise are required.</p><p>The biggest marketed feature of WASM was its improved performance over JS. And It does deliver on that promise. The obvious reason for it is that it translates into a binary instruction which is of course lite weight than JS text files. There have been many articles around the internet which did benchmark tests across different browsers and devices.</p><blockquote>And usually, WASM was 30–60% faster than JS depending upon the browser and devices.</blockquote><p>So what went wrong, you might ask?</p><p>Though it exceeded the benchmark tests, Manier times, users and developers have found that real-world performance does not match that of benchmarks. It does exceed JS performance but not as much as the benchmarks suggested. Which basically disappointed many people.</p><blockquote>But one of the most prominent failures for WASM was its promise of improved security over JS.</blockquote><p>We all know JS has several security issues on its own, and WASM promised to resolve them, however, in real-world applications, it failed to deliver on that promise. If you look at statistics <a href="https://www.zdnet.com/article/half-of-the-websites-using-webassembly-use-it-for-malicious-purposes/">here</a>, It states that Half of the websites using WebAssembly use it for malicious purposes.</p><p>So the very tool that was designed to improve security is being used for malicious purposes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*M-CP9VPdyZqU2kYMl6C_1w.gif" /></figure><p>That’s why is said it partially did not deliver on its promise.</p><p>But that’s not all.</p><blockquote>We, the developers and people of the tech community understand that new technology can not be perfect at first. It takes many iterations to be in shape and start delivering. So we really want WASM to gradually improve and start to deliver over iterations.</blockquote><p>But the problem WASM faced apart from its security issues and some performance mismatch between the benchmark and real-time is the marketing and getting the attention of developers and people of the tech community.</p><p>Though it was released with a bang in 2017 and later many products like Blazor made headlines with WASM, Many people do not know what WASM is capable of doing or have never got their hand on it to experience how it is different from other front-end/client-side frameworks. It’s been too long to get its well-deserved attention and widespread adaptation in real-world applications.</p><p>So, combining poor after-launch marketing along with security issues, It became the hyped for doom tech.</p><p>So the question we now raise is how long will it be able to continue this way? Will it survive any further or if not when it will be dead eventually? Let’s find that out in the next segment.</p><h3>When?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_5gmDGeWktN7oCWH" /><figcaption>Photo by <a href="https://unsplash.com/@aronvisuals?utm_source=medium&amp;utm_medium=referral">Aron Visuals</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s been 5 years since WASM was released and its potential is still fully not explored and adapted for the obvious reasons we mentioned above.</p><p>So will it be able to continue this way and survive, or will it be dead? and when it will be dead?</p><p>Well, I truly wish it to succeed as it&#39;s an exciting piece of tech with lots of potentials. So I really do not wish it to go into dust this soon. But unless it resolves the issues I mentioned above, It won&#39;t be long before WASM may get forgotten.</p><p>It has the potential to co-operate with the current technology trends like Gaming, metaverse and crypto/blockchain applications as it can do the huge computation in real-time with high performance. So If adopted well, it can become the prominent force driving client-side development provided it starts delivering on its promises.</p><p>Until then, Happy Learning!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=456cbadf101d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/what-happened-to-javascript-killer-webassembly-is-it-already-dead-456cbadf101d">What happened to “Javascript Killer” WebAssembly? Is it already dead?</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are you following Agile or Lipstick Agile?]]></title>
            <link>https://medium.com/codex/are-you-using-agile-or-lipstick-agile-9daa68280963?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9daa68280963</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Tue, 10 May 2022 05:43:21 GMT</pubDate>
            <atom:updated>2022-05-11T05:54:52.310Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/925/1*hJR6TcA5sLQZaTE7A1CjFQ.jpeg" /></figure><p>Agile Methodology was founded in the early 2000, but it picked up pace in the early 2010s.</p><p>Since then, more and more organisations try to be agile in their core values and practices (People call it “Living Agile”), but others following them just boast about being agile and call it a day, without solving core issues and following its principles. (Call it “Lipstick Agile”)</p><p>In this article, We’ll revolve around Lipstick Agile and answer the following questions:</p><p><strong>Why do we call it “Lipstick Agile”?</strong></p><p><strong>What are its traits?</strong></p><p><strong>When should you be alarmed? and</strong></p><p><strong>How can you overcome it?</strong></p><p>Let’s get started then!!!</p><h3>Why?</h3><p>First, Let’s go through the term “Lipstick Agile”.</p><p>I apologise for borrowing the term from <a href="https://medium.com/@stefanw?source=post_page-----2cce052b9bda--------------------------------">Stefan Wolpers</a>, But the term is surprisingly simple and complex at the same time.</p><p>A basic explanation of why it’s called “Lipstick Agile” is the simple illustration of the first image in this story where a pig is forced to apply the lipsticks and makeup to make it look good. It’s obvious that even though we apply as many lipsticks, a pig at its core is still a pig and it will do as good as a pig even if we expected it to be better after applying lipstick.</p><blockquote>Likewise, If you try to enforce the Agile manifesto under individual’s throats without addressing the organisation’s and individual’s static and rigid mindset, you are falling in the trap of Lipstick Agile.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8wCy3KtJRs6dyxq0Vc0A9Q.png" /></figure><p>Though it’s a very simple explanation of the term, the complexity of this term lies in finding out if you are using Lipstick Agile or not?</p><p>So I’ll try to address and declutter that complexity in the next segment.</p><h3>What?</h3><p>Now, What are the traits of Lipstick Agile? How can you identify if you are falling into Lipstick agile or not?</p><p>For that, as an individual/leader, you would need to ask yourself these questions by being true to yourself. Don’t give answers by your theoretical knowledge but by answering it from what you practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9ky02TYDU4IDbLqU" /><figcaption>Photo by <a href="https://unsplash.com/@two_tees?utm_source=medium&amp;utm_medium=referral">Matt Walsh</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Ready?</p><p>Here they are:</p><ol><li>Is your team’s or individual’s mindset rigid? Do they or you welcome changes as they come than resist them?</li><li>Is your appetite for numbers like revenue, contracts and customer retention strong? or can you be flexible for negative numbers?</li><li>Do you stick to the processes and tools set by your organisation/team? or do you empower or motivate individuals to explore various processes and tools?</li><li>Is working software important to you over the history of tickets and documentation?</li></ol><p>If the answers given by your heart are on a scale of No to neutral, then you are definitely using Lipstick Agile. Even if you said yes to most of it, I would burst that bubble in just a moment. But before that, you might be wondering, these questions seem familiar. And you’re right!!! These are taken straight from the <a href="https://agilemanifesto.org/">Agile Manifesto</a>.</p><p>So even if you said yes to the above questions, let’s break those further down.</p><ol><li>Do you stick to the agile ceremonies even if they are not fruitful? Do you keep doing the standup meetings even if it’s just status updates? Do you even work on good, bad or improvement points from retrospectives?</li><li>Do you believe that increasing revenue or new contracts or customer retention ratio are the primary metrics to measure success? Do you put numbers like those, preference over customer satisfaction?</li><li>Is Burndown chart, Velocity, Throughput, Time logs, Bug counts, Jira reports and sticking to processes set by the organisation/team more important to you than the business value of features and an individual? Is completing all the committed items in a sprint in hustle and bustle to show productivity more important to you than the quality of delivery from that sprint?</li><li>Do you prefer everything should be documented, be it in Docs, Jira Ticket, Sharepoint, OneNote or Commits? Do you rigidly maintain the history of work done by individuals than worry about the impact of work done?</li></ol><p>Now I assume, your answers might have changed because that’s what most of the “Self Trained Agile Organisations” do.</p><blockquote>Now, don’t get me wrong, I do not say that numbers like revenue, contracts, retention ratio etc and metrics like burndown, velocity, reports etc doesn&#39;t matter. It most certainly does. But it does only when team &amp; individuals have matuared enough in Agile Transformation.</blockquote><p><strong>Following them rigorously and making decisions based on that while your team or individuals still don&#39;t have an Agile mindset or are not trained for it, is of no use. In fact, It may adversely affect your team/organisation.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*pmS_rpOaxNpi1ng0QuVg7g.gif" /></figure><p>Lipstick Agile works fine for most of the teams &amp; organisations who take pride in being Agile even if it’s false agile. It only starts to get painful when things start to go sideways. That’s when you should be alarmed. We’ll discuss those alarms in the next section.</p><h3>When?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tPK_DL35GuzsQ9p1" /><figcaption>Photo by <a href="https://unsplash.com/@eilisgarvey?utm_source=medium&amp;utm_medium=referral">Eilis Garvey</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When you should wake up from false pride in using Agile while you are actually using Lipstick Agile? What are the signs of that wake-up call?</p><blockquote>Well, for starters, the first and major indication would be your customers. If they are not happy with what you deliver or they don&#39;t find business value of the features you have delivered, then you should be alarmed.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*oRUtxu8Ey1ekR_bX3nV39A.gif" /></figure><p>The second would be the satisfaction of individuals. If the individuals feel that the work they are doing is not making any sense, or they feel the meetings or several agile ceremonies are wasting their time without giving any fruitful results, or they feel that the processes and tools they are using are rather an overkill than facilities, then you should be alarmed.</p><p>Third would be your feeling about the deliveries and performance of your team. If you think that burndown, throughput, bug count, bug severities etc.(Yes, I admit here, metrics are relevant) and most importantly, the business values of deliveries are going sideways, or the teams or individuals are not in sync with themselves or with stakeholders and they are still working in silos, then you should be alarmed.</p><p>Now that we know what are the indications of a wake-up call, how can one overcome that? That’s what we’ll discuss in the next section.</p><h3>How?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VhCNMBgPr2XqhVVl" /><figcaption>Photo by <a href="https://unsplash.com/@jannerboy62?utm_source=medium&amp;utm_medium=referral">Nick Fewings</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Now, Let’s circle back to the first question I asked in the breakdown questions in the “What?” section. Because the best solution to overcome the trap of Lipstick Agile lies there.</p><p>The question I asked was: Do you even work on good, bad or improvement points from retrospectives?</p><p>The retrospective is a very important ceremony which allows the team to focus on what went well, what didn’t go well and what we need to improve.</p><blockquote>Most of the organisations/teams that are using Lipstick Agile either get away from this important ceremony totally or perform it just for the sake of … well, performing it.</blockquote><p>Is it because they fear that individuals would say something like Dilbert?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*SvrgzmW0oFW3zGPItHHFNQ.gif" /></figure><p>I certainly hope not. 😁</p><p>The prime reason the retrospective is being done for name’s sake is that individuals and stakeholders lose their interest in performing it over time, as the points like what went well, what didn’t go well and what needs to be improved etc. stay in retrospect board only. It doesn’t translate into action items for future sprints.</p><blockquote>To overcome the trap of Lipstick Agile, one should empower and trust their teams, individuals, stakeholders and end-users to provide actual feedback rather than imposing fear or letting them have disinterest in that ceremony by not making it fruitful.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*b9MpT9HsVtpnP3gOe767gA.gif" /></figure><p>Another way to overcome it is to envision and tackle real-world business values. Measure the work done by the team on a business value scale. Empower the individuals to raise red flags when they feel the work they are doing isn’t adding any value.</p><p>Ask individuals to remember to raise red flags by asking them to remember: <br><strong>“If it doesn’t make any sense to you, it shouldn’t be there”</strong></p><p>Once you fix those 2, the third alarm goes off automatically.</p><p>Hope you found it useful and practical.</p><p>Happy Learning!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9daa68280963" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/are-you-using-agile-or-lipstick-agile-9daa68280963">Are you following Agile or Lipstick Agile?</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The end of Mediocre Software Developer is near?]]></title>
            <link>https://medium.com/codex/the-end-of-mediocre-software-developer-is-near-eda94c3f04b2?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/eda94c3f04b2</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[github-copilot]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Mon, 02 May 2022 05:25:07 GMT</pubDate>
            <atom:updated>2022-05-10T07:21:10.481Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J57QkAD6S9eNO1hE" /><figcaption>Photo by <a href="https://unsplash.com/@wcfthdu?utm_source=medium&amp;utm_medium=referral">Wicliff Thadeu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As we all know, Software development is a challenging and continuously evolving field. Not just today, It has been this way always. But in recent times, it has been accelerated at such a pace that many developers find it difficult to keep up.</p><p>So the question we are asking is: Will the fast-paced and rapidly evolving nature kill the jobs of mediocre programmers?</p><p>Again as per my previous articles, I’ll go by answering What, Why, When and How.</p><h3>What?</h3><p>What do I mean by Mediocre developers and the end of them?</p><p>Let’s first go with a Mediocre developer. I believe there are several traits of a Mediocre developer. Like:</p><ol><li>Little or no interest in programming</li><li>Procrastinate to cope with the latest trends</li><li>Does not deep dive into the solutions he/she is working on</li></ol><p>Now, What do I mean by end of mediocre developers? I do not mean that they would disappear from the industry. but realistically, they would keep doing mediocre jobs and maintain the legacy systems.</p><h3>Why?</h3><p>First, we need to understand why this question arose?</p><p>We’ve all been saying and seeing the fact that AI and robotics would eventually take over many jobs. But we all thought that Software Development is a field that is the brain behind AI, so developers would never be obsolete. However, in recent years, the increasing use of no-code and CMS based websites pushes us to think otherwise.</p><p>We think that no-code and CMS based websites can’t create complex and logical web apps. and that’s correct too. But then came GPT-3 and people created some amazing apps over it. And in October 2021, GitHub launched Copilot which allows a user (even non-technical users) to code by just providing comments or requirements in plain English language.</p><p>I know copilot is more like a fun playground right now, but it’s impressive to see how it can even provide solutions to moderate to some highly complex leetcode problems.</p><blockquote>We still think it’s in an early stage, and it can never be as perfect and understanding as a human being, but it’s a start.</blockquote><p>And then came GitHub Copilot Labs. and it blew my mind.</p><p>It explains code, answers some specific questions, and even translates the code from one programming language to another.</p><p>It can also let users understand the existing code so a developer would not always be required even if there need some changes in existing code.</p><p>Both extensions combined make us think, are the tech giants trying to get rid of expensive and slow human intelligence with cheap and fast artificial intelligence?</p><p>Apart from that, the rise of Web3.0 and decentralized applications would also push the mediocre developers out of mainstream development. It’s still too early to say whether web3.0 will become a driving force of this decade or not, but it would certainly make some impact.</p><h3><strong>When?</strong></h3><p>So when is this going to happen? When will the Mediocre developers become obsolete?</p><p>There’s no definite timeline one can think of. But with advancements in AI, It seems pretty closer than we think. My best guess would be that within the next 5 years, all the new developments would gradually shift to methods like no-code and may also use a non-technical person with GitHub co-pilot as a pair programmer.</p><blockquote>It doesn&#39;t mean developers will be out of jobs. The projects which require heavy business logic or heavy configurations or personalisation or heavy database structure that a human brain can do better and faster than an AI which provide false results in that case, would always require a developer.</blockquote><h3><strong>How?</strong></h3><p>How a developer can save him/herself? Well, There’s only one way. He/she will have to stop procrastinating and start learning new technologies.</p><blockquote>It would be either AI or Web3.0 that would cause the end of Mediocre developers.</blockquote><blockquote>So It should be the primary goal to get on either of the trains to save him/herself from getting thrown out of the station before the trains left.</blockquote><p>Happy Learning!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eda94c3f04b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/the-end-of-mediocre-software-developer-is-near-eda94c3f04b2">The end of Mediocre Software Developer is near?</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tangled with front-end state management? Use the store!!!]]></title>
            <link>https://medium.com/codex/tangled-with-front-end-state-management-use-the-store-86632c20f2ef?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/86632c20f2ef</guid>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[vue]]></category>
            <category><![CDATA[state-management]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Wed, 29 Dec 2021 13:53:44 GMT</pubDate>
            <atom:updated>2022-05-10T09:06:57.503Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VMZS9voaQkB48gKV" /><figcaption>Photo by <a href="https://unsplash.com/@timmossholder?utm_source=medium&amp;utm_medium=referral">Tim Mossholder</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let’s be honest, State management on front-end applications is a tedious job.<br>Even from the days of Vanilla JavaScript to the date with many advanced JS Frameworks and libraries.</p><p>State management can be done in all three tiers of the application, be it backend, database or front-end. However, we will specifically talk about state management in the front-end side of it in this article.</p><p>Let’s get started in my much-appreciated style of WWWH aka What, Why, When and How.</p><h3>What?</h3><p>First up, we need to understand what is the state?</p><p>The state is just a snapshot or representation of the system from the client-side at a given point in time. It can be manipulated and represented in a seamless manner especially in single-page applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mD6hH2jyPWoyKeE-r-ptxw.png" /><figcaption>State Management Pattern in a nutshell</figcaption></figure><p>The state is basically a store of data take it Application related data, User Data, Navigation information, Communication-related data etc. And with any kind of data, we deal with, It can be either manipulated or consumed.</p><p>As for State Management, We can manipulate the state by various actions. It can be user actions, API response, navigation changes etc. On the other hand, we can consume that store to display the latest state of the application by querying the store. As simple as that.</p><p>As one can figure out from the above diagram, It’s a circular pattern that is continuous. But basically, if we start with the store, the store has the initial state of the application which is used to render the view, from which, the user performs any actions which in turn triggers a mutation to state and it continues.</p><p>There are multiple libraries that provide state management for different javascript frameworks like:</p><p>&gt; NgRx for Angular<br>&gt; Redux for React<br>&gt; Vuex for Vue</p><h3>Why?</h3><p>Now that we understood what is state and state management, let’s see why we need it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6JzeC4ihd7oCnOaj" /><figcaption>Photo by <a href="https://unsplash.com/@neotronimz?utm_source=medium&amp;utm_medium=referral">Nirmal Rajendharkumar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Remember the time when we used to store a bunch of things into localstorage that can be manipulated and consumed throughout the application? then you would certainly remember the pain of getting all those key values organised.</p><p>State management takes care of the main pain point of organising the state for your application without you constantly worrying about it.</p><p>State management helps us to set, manipulate, organise and synchronise the current state of application throughout all the components in your application.</p><p>It also helps us to make API interaction and data flow through the APIs smoother and consistent. It can help us cache(not in the literal sense) the responses so that we can retrieve them as and when required quickly.</p><p>It also helps us to ease the communication between multiple components as the centralised store helps all the components to interact with it to change or access the data centrally.</p><h3>When?</h3><p>So, When we can think of using the store? What are the use cases in which using the store will benefit us?</p><p>There are mainly 2 scenarios in which one can think of using the store:</p><ol><li>The application contains so many components that need to interact with each other frequently or</li><li>The application consumes redundant data frequently.</li></ol><p>However, If you are developing a simple application with component silos, you are better off not using it as it would rather be complex and slow to implement the State management.</p><p>How do we decide when to use State management? I would like to borrow the below paragraph from ngrx website:</p><p>A good guideline that might help answer the question, “Do I need NgRx Store?” is the SHARI principle:</p><ul><li><strong>Shared</strong>: state that is accessed by many components and services</li><li><strong>Hydrated</strong>: state that is persisted and rehydrated from external storage.</li><li><strong>Available</strong>: state that needs to be available when re-entering routes.</li><li><strong>Retrieved</strong>: state that must be retrieved with a side-effect.</li><li><strong>Impacted</strong>: state that is impacted by actions from other sources.</li></ul><h3>How?</h3><p>We can use state management by simply using libraries that help us implement state management. and it varies for javascript frameworks.</p><p>However, The basic concept of implementing a store is the same for all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*KIoNyRO6s_52W68Y-0usJw.png" /><figcaption>Workflow for Vuex</figcaption></figure><p>There are 4 actors which need to be remembered:</p><ul><li><strong>State</strong>: It’s the source of truth/data that stores the state of the application</li><li><strong>View</strong>: Which consumes the state to present it to the user</li><li><strong>Actions</strong>: Which are the cause of change in state</li><li><strong>Mutations</strong>: Which gets triggered on the specific action and eventually change the state.</li></ul><p>Rather than adding the snippet for all the JS frameworks, I would like to redirect you to the documentations of well known and well established libraries from various JS frameworks.</p><ul><li>Angular: <a href="https://ngrx.io/guide/store">NgRx</a></li><li>React: <a href="https://redux.js.org/introduction/getting-started">Redux</a></li><li>Vue: <a href="https://vuex.vuejs.org/guide/#the-simplest-store">Vuex</a></li></ul><p>Happy Learning!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86632c20f2ef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/tangled-with-front-end-state-management-use-the-store-86632c20f2ef">Tangled with front-end state management? Use the store!!!</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mediator Pattern: A Capable Underdog]]></title>
            <link>https://medium.com/codex/mediator-pattern-a-capable-underdog-7eb82944a935?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7eb82944a935</guid>
            <category><![CDATA[mediator-pattern]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[cqrs]]></category>
            <category><![CDATA[design-patterns]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Fri, 03 Dec 2021 11:56:26 GMT</pubDate>
            <atom:updated>2022-05-10T07:47:29.617Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mediator Pattern: A Capable Underdog?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*NEzTLQNy6vDTuW7B6b48ew.jpeg" /></figure><p>Aghh, One more design pattern blog on my feed? I bet you are thinking the same. But let me assure you, you would be gaining at least some idea of why I called it Capable and Underdog at the same time.</p><p>I would be answering basically 4 questions here which everyone would ask when learning about a new pattern: <strong>What, Why, When and How</strong>?</p><p>So let’s get started:</p><h3>What?</h3><p>First and foremost, the question that arises hearing about a new pattern is why?<br>Why do you need some new patterns in your project when you already have more than 20 well-known design patterns floating around and in a stable state for most of the project.</p><p>Well, to understand that first we need to understand what is mediator pattern?</p><p>If we go by the definition from Wikipedia, it says:</p><blockquote>“the mediator pattern defines an object that encapsulates how a set of objects interact.”</blockquote><p>Over the head huh? Don’t worry.</p><p>As the name implies, the Mediator plays an intermediatory role to mediate. But mediate between whom? You guessed it right. Between classes. In other words, it provides a unified and single entity to communicate between classes. Let’s make it simple for now, it mediates between the core API Actions and the respective business logic they communicate to. So, it’s a behavioural pattern.</p><p>You would immediately ask, why do we need a mediator when we can already communicate between classes very easily by using plenty of other design patterns, to answer that, let’s move on to the next topic.</p><h3>Why?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*47yVS6oabVDepiv4" /><figcaption>Photo by <a href="https://unsplash.com/@bdp028?utm_source=medium&amp;utm_medium=referral">Beckett P</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagine the Airport to be your application and you need to manage the air traffic.</p><p>Imagine if there was no Air Traffic Controller on the ground and planes needed to manage the altitudes and speeds by themselves, by interacting with dozens of other aeroplanes nearby?</p><p>It would create a mess, wouldn’t it?</p><p>Most of the traditional design patterns work on dependencies. Let’s say there are 3 classes that depend on 3 different classes to execute their business logic. What we do traditionally is resolve dependencies of the classes it consumes. Which makes the interaction many to many in a way. Which creates a spaghetti of dependencies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/351/1*uRzcER9AJHpNTheKDPSyKw.jpeg" /><figcaption>The Traditional way</figcaption></figure><p>Now imagine you need to decouple or change the interaction of some of the classes?</p><p>That’s where the mediator comes into the picture.</p><blockquote>What it does is, basically take care of interactions.</blockquote><p>Which solves several issues:</p><ol><li>Direct/Tight communication between classes.</li><li>Handles complex dependency management.</li><li>Allows us to easily modify any interactions between the classes.</li></ol><p>The scenario from above will now look like this in mediator pattern:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/391/1*8AfVfxkn0W0_NBBPtzlw4A.jpeg" /><figcaption>The Mediator way</figcaption></figure><p>It&#39;s easily observable that it not just looks clean but also provides a unified interface to manage the interactions.</p><p>Ok, so now that we know what it is and why it was introduced, let&#39;s check some use cases on when to use it and when not to use it.</p><h3>When?</h3><p>Simply put, we can use a mediator pattern when you need to get out of dependency entanglement. When you have so many classes which are dependent on one another, managing dependencies create a headache.</p><p>We can use it when we need to easily change the behaviour of how classes interact between themselves, when we need to have an ATC kind of single entity to manage the interactions and when we need to encapsulate the objects being communicated such that only a single entity knows the dependencies between classes.</p><p>Of course, it’s not perfect. It comes with a price.</p><p>As with all other single entities, it’s prone to fail. A complex mediator with too many dependencies on it may become a single point of failure. So better not complicate it.</p><p>Now let&#39;s jump on to How we can use it?</p><h3>How?</h3><p>Don&#39;t worry, I won&#39;t be pasting the whole solution here. You can check out multiple examples of such projects on GitHub like this one <a href="https://github.com/evgomes/cqrs-mediatr-asp-net-core">here</a>.</p><p>But to put it in basic context, you can install and configure MediatR Nuget Package, Create models and handlers pertaining to actions/workflows, and then use it in actions by sending the request to the mediator.</p><h3>Mediator with CQRS</h3><p>If you have visited the GitHub repo from above, you would have seen the term CQRS-Mediator Pattern. CQRS and Mediator are often used interchangeably which is somewhat incorrect.</p><p>Both have different use cases and problems to solve, but combining both is where magic is. The Nuget MediatR facilitates the use of both patterns, which is one of the reasons why these terms are used interchangeably. Learn more on CQRS <a href="https://docs.microsoft.com/en-us/azure/architecture/patterns/cqrs">here</a>.</p><h3>Capable Underdog?</h3><p>Till now, we know why it&#39;s capable, but why it&#39;s still an underdog?</p><p>Unfortunately, there is no certain answer to the question, but in my opinion and observation, the reason would be that many existing projects use widely acceptable design patterns like singleton and factory patterns. But It’s evident that the use of the Mediator Pattern is accepted and growing especially in new solutions industry-wide.</p><p>Happy Learning!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eb82944a935" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/mediator-pattern-a-capable-underdog-7eb82944a935">Mediator Pattern: A Capable Underdog</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things you will realize about the corporate IT world, Eventually]]></title>
            <link>https://parthmakawana.medium.com/things-you-will-realize-about-the-corporate-it-world-eventually-7a4ca25ae6af?source=rss-47a1c64319b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a4ca25ae6af</guid>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[corporate]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[reality]]></category>
            <dc:creator><![CDATA[Parth Makawana]]></dc:creator>
            <pubDate>Tue, 05 Jan 2021 06:22:14 GMT</pubDate>
            <atom:updated>2021-06-18T13:44:48.155Z</atom:updated>
            <cc:license>https://creativecommons.org/publicdomain/mark/1.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LSHlmDfYI0_efli5" /><figcaption>Photo by <a href="https://unsplash.com/@villxsmil?utm_source=medium&amp;utm_medium=referral">Luis Villasmil</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Internet is full of articles with similar titles, some written by well-known authors. So, why bother reading this? Well, These points are my observations being in the corporate IT world for about 5 years now. Some of them may be generic for the corporate world in general. You may agree or disagree with a few or many of them. But every individual may have their viewpoint based on the degree of the circle of their experience they are standing on. And I would love to hear your thoughts on it.</p><p>So let&#39;s get started:</p><h3>1. The Foundation of your career is very crucial</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tVLQul3Av9i2mQco" /><figcaption>Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=medium&amp;utm_medium=referral">Brett Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Colleges and universities form your academic foundation, but their importance gradually decreases when you step into the corporate world. It just becomes the first stepping stone in starting your career. Nothing more. Your academic excellence doesn’t necessarily convert to an excellent career. It depends on how excellent your career foundations are. I’ve seen many people who were not able to convert their academic excellence into an excellent career.</p><p>But what builds an excellent career foundation? You ask.</p><p>Well, It depends on the work, environment, and co-workers you get at the beginning of your career.<br>As a graduate, your obvious aim remains to build your experience, knowledge, and professional etiquette. You work as hard as a child who wants to reach up to his/her toy up in the attic. While getting knowledge is in your hands partially, these things still depend on the people you interact with every day.</p><blockquote>A graduate is like a seed. It takes some great people and minds to nurture them into fruitful plants.</blockquote><p>Having a mentor who can nurture that seed, is very crucial for an excellent foundation of a career.</p><p>But a mentor can only write something on a slate if it&#39;s empty. It&#39;s important for a graduate to wipe off all unnecessary experience, knowledge, and arrogance he/she has gained while in academics, and become a student once again. For a successful foundation, you need to surround yourself with people who not only improve your knowledge and encourage learning but motivate you to achieve excellence selflessly in the early stages. And even scold you for your misdirection and wrong behaviour.</p><p>On the other side, If you are surrounded by negative people at the start of your career, please know that you are doomed. Because, it only increases the unnecessary experience, knowledge, and arrogance you’ve gained till now. It diverts your attention from improving yourself to blaming others and increases your ignorance over time.</p><h3>2. Processes Matters</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*trKUAcbJgB8aBoXs" /><figcaption>Photo by <a href="https://unsplash.com/@edenconstantin0?utm_source=medium&amp;utm_medium=referral">Eden Constantino</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a developer, I’ve hated some of the software development processes and methodologies. I mean why do we need so many meetings, checkpoints, and processes to complete a small piece of work. Right? Well, they are there for a reason.</p><blockquote>I’ve seen the chaos where there’s no established process, misunderstanding when there’s no meetings and conflicts when there are no checkpoints.</blockquote><p>Yes, the processes should not be rigid, It should be agile enough to modification depending on situations. And Meetings should always be time-bound and to the point.</p><p>I’ve been first introduced to the Iterative model and then to Agile. I’ve personally liked the iterative model for the fact that it has the best of both worlds: Waterfall and Agile. Or for the fact that requirements are quite stable and easy for modification. But either way, Any established process is required for the team to perform consistently.</p><h3>3. Building a network is important</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eNkqlnjmSQDlVJC1" /><figcaption>Photo by <a href="https://unsplash.com/@omarg247?utm_source=medium&amp;utm_medium=referral">Omar Flores</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Well, I for one, am not the right person to write about this as I am terrible at building a network. But I’ve included this because I realize that not having a good network of people damages your chances of getting good opportunities in the future. I have always behaved self-respectfully in getting in touch with former colleagues. Some may even consider that arrogance.</p><blockquote>But I feel you should connect with people who wants to be connected with you. You should pull that string if you don’t get any response from other end. And focus on those who do. It might reduce your network, but it will be of the right people.</blockquote><h3>4. Comfort Zone kills your skills</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E87ZYTw-h5kdcN-t" /><figcaption>Photo by <a href="https://unsplash.com/@coena?utm_source=medium&amp;utm_medium=referral">Coen Staal</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In everyone’s life, there comes a time when they have achieved many of the things they’ve wanted, and now they sit back and relax. Everyone deserves to relax if the achievement is huge, but It should not convert into Comfort Zone. If you’ve achieved something excellent, relax, and regain your strength to set up new goals.<br>How do you find if you’re in your comfort zone or not? It&#39;s easy.</p><blockquote>If you’re happy (or rather not stressed out) with whatever you do, please know, you are in comfort zone.</blockquote><p>I know this is not a popular opinion and it&#39;s debatable. People always says that take pride in what you do, be happy in what you do, blah blah, but in ideal corporate world, If you’re always happy (or rather not stressed out) with even the wrong situation you are in, you are in the comfort zone.</p><p>You’re getting good pay, praises from everyone. That feels sweet. And who wouldn’t like sweet things?</p><blockquote>But remember, sweetness causes diabetes, just the way comfort zone kills your skills.</blockquote><p>And how can we get out of our comfort zone? Well that depends, is your comfort zone created by people around you? Then connect with new people. Or is it created by day to day work? Then change the work, thrive for doing better.</p><h3>5. Learn to face conflicts and failure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q9UQObRvIzYQMJBb" /><figcaption>Photo by <a href="https://unsplash.com/@tamara_photography?utm_source=medium&amp;utm_medium=referral">Tamara Gak</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This perhaps is the most common and crucial point in all, because we all face that almost daily.</p><p>Let’s start with conflicts.</p><blockquote>It’s of-course fine to have difference of opinion on any point.</blockquote><p>Having multiple minds working on a common thing may bring multiple views to the table and that’s actually beneficial. But the problem arises when these difference of opinion turns into conflicts.</p><p>And about failure, many successful people have already talked about failure, so I might not be the right person to comment on that. But certainly, there would be times when you won’t be at your best. Just keep breathing and focus your attention.</p><h3>6. Respect/Adjust with your colleagues</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pkk3fph_oxZA-Pl4" /><figcaption>Photo by <a href="https://unsplash.com/@janesky?utm_source=medium&amp;utm_medium=referral">Antonio Janeski</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Your colleagues and superiors play a crucial part in what you become in your professional career. You might be fortunate to have great colleagues that support, understand and motivate you. But many may not be that fortunate.</p><p>For those, there are few ways to deal with the situation.</p><blockquote>Respect other’s opinions that may not adversely affect you, and Adjust with and understand other’s opinion that may.</blockquote><p>There will be scenarios every day where you think, a piece of work can be done easily or better your way, but that may not be accepted. So rather than being heartbroken or hurt, try to find out why your opinion is discarded, compare it with what’s been accepted and improve upon it.</p><blockquote>That doesn’t mean you should not voice out your opinions. You should always put your opinion on the table. If it’s accepted, be happy, if it’s not, adjust and understand why it’s not accepted.</blockquote><h3>7. Never mix up work, family, and friends</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MMWDFInnRNNwvX75" /><figcaption>Photo by <a href="https://unsplash.com/@krakenimages?utm_source=medium&amp;utm_medium=referral">krakenimages</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This one rule will be more than enough for peaceful work and life. That doesn’t mean you don’t share your good and bad things from work to family and friends and vice-versa, but define a line between what to share and what not.</p><blockquote>That also doesn’t mean you don’t make friends at work, but identify the nature of that friendship.</blockquote><p>If you cross that thin line of separating work, family, and friends, it will create a mess you wouldn’t be able to settle easily.</p><h3>8. Be careful whom you consider as friends at work</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9gCSPmBgsD0xpGBg" /><figcaption>Photo by <a href="https://unsplash.com/@grstocks?utm_source=medium&amp;utm_medium=referral">GR Stocks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Speaking of friends at work, it&#39;s very important, who you consider friends at work. Because let&#39;s be honest, in the corporate world, not everyone is your well-wisher and not everybody is your enemy.</p><p>How can you find such friends? You ask. Well, it&#39;s difficult.</p><blockquote>Because you will get to know who your real friends at work are after you stop working with them.</blockquote><p>That sounds crazy, but it&#39;s true to nature. True friends at work will always be happy to connect with you, improve one another, share knowledge and have fun even after you are no longer important to them.</p><blockquote>They admire and connect with your nature, not your position and power.</blockquote><p>But during your ongoing tenure, just consider them as your colleague. As you will eventually find out if they are friends or not.</p><h3>9. Respect is a two-way street</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*imGwgF6VADxRvX8Z" /><figcaption>Photo by <a href="https://unsplash.com/@felippetiago?utm_source=medium&amp;utm_medium=referral">Tiago Felipe Ferreira</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The statement is self-explanatory. If you don’t give respect to others, you won’t get it from that person and others. There are several aspects to it, however,</p><blockquote>Most of the people co-relate respect with position and power. That way, one just becomes an opportunist.</blockquote><p>Getting respect is the right of every human being, whether they are powerful or not and knowledgeable or not. People tend to ignore especially those who either do not hold any power or have less knowledge than others. We know the power and position aspect easily, but let me tell you about the knowledge aspect. Those who are less knowledgeable than others, make mistakes while working, requires help by keeping their dignity intact. If you hurt their dignity by unnecessarily scolding them, they might approach you in the same way.</p><blockquote>I’ve seen the magic of being a selfless helping hand to those in need, and the beauty of getting their respect back when they approach you.</blockquote><h3>10. Learning is the real earning</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a8izZDjEGaG1JBZ2" /><figcaption>Photo by <a href="https://unsplash.com/@element5digital?utm_source=medium&amp;utm_medium=referral">Element5 Digital</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>Learn, Earn, Adjust, Respect and Relax. Peace out. ✌</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a4ca25ae6af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>