<?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 Pardha Saradhi Mavilla on Medium]]></title>
        <description><![CDATA[Stories by Pardha Saradhi Mavilla on Medium]]></description>
        <link>https://medium.com/@pardhasaradhim?source=rss-513a7645bb59------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*59ThqkhCC2hAE5Vn.</url>
            <title>Stories by Pardha Saradhi Mavilla on Medium</title>
            <link>https://medium.com/@pardhasaradhim?source=rss-513a7645bb59------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:20:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pardhasaradhim/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 Fallacy of ‘X is Dead’ Tech Articles: Why They Don’t Contribute to the Conversation]]></title>
            <link>https://medium.com/@pardhasaradhim/the-fallacy-of-x-is-dead-tech-articles-why-they-don-t-contribute-to-the-conversation-b6c405f4eb6b?source=rss-513a7645bb59------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6c405f4eb6b</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Pardha Saradhi Mavilla]]></dc:creator>
            <pubDate>Tue, 21 Mar 2023 18:13:07 GMT</pubDate>
            <atom:updated>2023-03-21T18:13:07.116Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s a familiar trope in the world of tech blogging: “X is Dead!” or “Move Over, X.” These sensationalist headlines often grab attention, but they rarely contribute any meaningful value to the discourse. Instead of engaging in thoughtful analysis, these articles tend to rely on hyperbole and oversimplification, which does a disservice to readers and the tech industry alike. This article will examine the reasons why “X is Dead” tech articles are problematic and suggest ways to elevate the conversation for the benefit of everyone involved.</p><figure><img alt="Confuse when you can’t convience" src="https://cdn-images-1.medium.com/max/1024/1*MX5Xwpui0t9zyiRQYvvE3Q.jpeg" /></figure><ol><li><strong>Overgeneralization and lack of nuance <br></strong>“X is Dead” articles often rely on broad generalizations that gloss over the complexities and nuances inherent in the technology landscape. By framing the conversation as an all-or-nothing proposition, these articles dismiss the value of individual use cases, diverse applications, and the dynamic nature of technological evolution. Instead of fostering constructive debates about the merits and drawbacks of different technologies, these articles only serve to polarize the discussion.</li><li><strong>Clickbait culture <br></strong>Sensationalist headlines are designed to capture clicks and generate revenue, often at the expense of accuracy and integrity. This clickbait culture incentivizes authors and publishers to prioritize attention-grabbing statements over thoughtful analysis. While it may drive short-term engagement, this approach ultimately erodes trust and undermines the credibility of tech blogging.</li><li><strong>Ignoring ongoing Innovation and development <br></strong>“X is Dead” articles often fail to acknowledge the ongoing innovation and development taking place in the technologies they declare obsolete. Technologies rarely die overnight; instead, they evolve, adapt, and find new applications over time. By suggesting that a particular technology is dead, these articles overlook the potential for future advancements and limit the scope of the conversation.</li><li><strong>Misleading and confusing for readers <br></strong>For readers who may not be well-versed in the nuances of the tech industry, “X is Dead” articles can be misleading and confusing. They often give the impression that certain technologies are no longer relevant or useful, when in reality, they may still have a significant role to play. This can lead to misinformed decisions and an inaccurate understanding of the technological landscape.</li></ol><p>Recommendations for a better tech discourse: To foster a more constructive conversation around technology, here are some suggestions for writers and readers alike:</p><ol><li><strong>Embrace nuance and complexity <br></strong>Acknowledge the intricacies and diverse applications of different technologies, and avoid oversimplification. Encourage discussions that consider the merits and drawbacks of various technologies in context, rather than resorting to blanket statements.</li><li><strong>Prioritize accuracy over sensationalism <br></strong>As authors and publishers focus on delivering accurate, well-researched, and thoughtful content rather than relying on clickbait tactics. As readers, seek out and support publications and writers that prioritize integrity and credibility.</li><li><strong>Celebrate innovation and progress <br></strong>Rather than declaring technologies dead, celebrate the innovation, development, and progress that drives the tech industry forward. Encourage conversations that explore the potential for growth and improvement in various technologies.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6c405f4eb6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building an Utility Application for Developers]]></title>
            <link>https://medium.com/@pardhasaradhim/building-an-utility-application-for-developers-1013e74eb8ff?source=rss-513a7645bb59------2</link>
            <guid isPermaLink="false">https://medium.com/p/1013e74eb8ff</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[utilities]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Pardha Saradhi Mavilla]]></dc:creator>
            <pubDate>Sun, 18 Feb 2018 22:11:02 GMT</pubDate>
            <atom:updated>2018-02-18T22:15:43.499Z</atom:updated>
            <content:encoded><![CDATA[<p>One tool to solve them all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YYkRmSyewkSCpuUJ." /><figcaption>“Tools ” by <a href="https://unsplash.com/@joszczepanska?utm_source=medium&amp;utm_medium=referral">Jo Szczepanska</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a software developer there are many tasks I do on a regular basis.</p><ul><li>Parsing/Validating JSON (<a href="http://jsonviewer.stack.hu/">http://jsonviewer.stack.hu/</a>)</li><li>Making test API calls (<a href="https://www.getpostman.com/">https://www.getpostman.com/</a>)</li><li>Running shell scripts/commands</li><li>Epoch and timezone conversions (<a href="https://www.epochconverter.com/">https://www.epochconverter.com/</a>)</li><li>Building/Validating cron expressions (<a href="http://www.cronmaker.com/">http://www.cronmaker.com/</a>)</li><li>Making notes/Saving snippets</li></ul><p>and some trivial but important ones</p><ul><li>Finding the current branches of different projects (<a href="https://github.com/">https://github.com/</a>)</li><li>Finding your schedule (<a href="https://www.google.com/calendar">https://www.google.com/calendar</a>)</li><li>Taking screenshots and searching for them. (I find myself doing this too many times)</li></ul><p>For most of the tasks stated above, I have to open my browser (chrome, which gobbles as much ram as it can get), go to that particular site, do my work and switch back to coding.This won’t work offline.For some of these tasks, there are native clients like Calendar but I have to open that for one small work .(I’m too lazy for that).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*emb0px0iy4jax-G1." /><figcaption>“Too lazy for anything routine” by <a href="https://unsplash.com/@ejleusink?utm_source=medium&amp;utm_medium=referral">Erik-Jan Leusink</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Whenever I had to do these tasks I always wished for one single offline application which is low on resources so I can keep in running and use it for all my purposes. Either my search was bad or my use-case is very specific I did not find a prebuilt solution for this.</p><p>So I decided to build one myself. I have started with the basic functionality and hope to finish it in 2 weeks. It will have JSON parsing, ability to make curl requests, a cron maker/validator, and one-click shell command execution. All this comes with a sleek UI. I am planning to write small posts covering different steps so that I can get some feedback while I build it.</p><h3>Closing Remarks</h3><p>If there are any other features you think that should be added please mention them in the comments.</p><h4>If this post was helpful, please click the clap 👏 button below a few times to show your support!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1013e74eb8ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>