<?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 Ayushya Jaiswal on Medium]]></title>
        <description><![CDATA[Stories by Ayushya Jaiswal on Medium]]></description>
        <link>https://medium.com/@ayushya?source=rss-8b1488a3e86d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ynfamnlEYeozIHX1FQElbw.png</url>
            <title>Stories by Ayushya Jaiswal on Medium</title>
            <link>https://medium.com/@ayushya?source=rss-8b1488a3e86d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:28:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ayushya/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Install MS SQL in Apple Silicon M1/M2/M3/M4 in Parallels?]]></title>
            <link>https://medium.com/@ayushya/how-to-install-ms-sql-in-apple-silicon-m1-m2-in-parallels-da22341c1748?source=rss-8b1488a3e86d------2</link>
            <guid isPermaLink="false">https://medium.com/p/da22341c1748</guid>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[m1]]></category>
            <category><![CDATA[m2]]></category>
            <dc:creator><![CDATA[Ayushya Jaiswal]]></dc:creator>
            <pubDate>Thu, 17 Aug 2023 15:42:56 GMT</pubDate>
            <atom:updated>2024-11-11T07:15:49.230Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve recently transitioned to an Apple Silicon M1/M2/M3/M4 device and require Windows OS for your applications, you might have encountered an obstacle when attempting to install SQL. <br>The conventional GUI Installer for SQL consistently fails, leaving you stranded at this juncture. But worry no more!</p><p>I’ve discovered a seamless solution that facilitates the installation of SQL Express and SSMS on a Mac running Windows 11 through Parallels. <br>Here’s how you can achieve it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sGJlVCawBYx6OONy2cyZDg.png" /></figure><p><strong>Installation Steps</strong></p><ol><li>Download the Installer Powershell scripts from <a href="https://github.com/ayushya/Install-MSSQLEXPRESS-in-Apple-Silicon-M1-M2/archive/refs/heads/main.zip">here</a>.</li><li>Extract the contents of this zip in C:/ in the Parallels VM.</li><li>Launch Powershell ISE with administrator privileges.</li><li>If you’ve never configured an execution policy, you can execute the following command <br>Set-ExecutionPolicy RemoteSigned (Optional)</li><li>Choose the specific flavor of SQL Server you wish to install (2019/2022 — Express/Developer). Open the corresponding .ps file, for instance if you&#39;re installing SQL Server 2019 Express, open install2019Express.ps1, and then execute it.<br>This process will automatically download and install the latest SQL Server along with SSMS.</li><li>By default, access to SSMS is granted via Windows Authentication only.<br>If you require SQL Server authentication, you can refer to this <a href="https://sudeeptaganguly.wordpress.com/2010/04/20/how-to-enable-sa-account-in-sql-server/">guide</a> for step-by-step instructions.</li></ol><blockquote>The provided scripts have a default Collation of SQL_Latin1_General_CP1_CS_AS. <br>Should you desire to modify this setting, you can do so by editing the variable $sqlInstallArgs within the respective .ps file before proceeding to execute it in step 5.</blockquote><p>Thank you for taking the time to read this guide. I sincerely hope that it has proven helpful to you. If you have any further questions, feel free to reach out. Happy installing!”</p><blockquote>If you have already tried installing SQL via <strong>other solutions</strong> that didn’t work for you, and you encounter an error while running this script, you should run the script on a fresh new Windows Instance and then migrate your other data to this new Instance on Parallels.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da22341c1748" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrading javascript package’s deep dependencies using yarn.]]></title>
            <link>https://medium.com/@ayushya/upgrading-javascript-packages-deep-dependencies-using-yarn-8b5983d5fb6b?source=rss-8b1488a3e86d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b5983d5fb6b</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[yarn]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Ayushya Jaiswal]]></dc:creator>
            <pubDate>Sat, 11 Apr 2020 22:05:54 GMT</pubDate>
            <atom:updated>2020-04-11T22:19:24.266Z</atom:updated>
            <content:encoded><![CDATA[<p>To upgrade a package in your package.json file, say your package isjsdom. You execute the following command:</p><p><strong>yarn upgrade jsdom</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*VP2U6e_mcU3ZO_hPXEJdxA.png" /><figcaption>Dependency tree for jsdom</figcaption></figure><p>But what if you want to upgrade any <strong>indirect or deep dependencies</strong> of your package, say you want to upgrade the <strong>acorn-globals</strong> package.</p><blockquote>Running <strong>yarn upgrade acorn-globals</strong> will have <strong>no effect</strong> on either package.json or your yarn.lock file.</blockquote><p><strong>Why?</strong></p><p>yarn upgrade only upgrades the packages listed under package.json and not the indirect or deep dependencies.</p><h3><strong>So how do we upgrade then?</strong></h3><p><strong>CASE 1</strong><br>A package which has only one version in yarn.lock</p><ol><li>Open yarn.lock and find the section which has the package’s version, resolved, integrity, etc.</li><li>Delete the section for the package, in our example acorn-globals</li><li>Run yarn</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hEKhcu4Y1PtP7RNgTr_uGw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fD2oLqLrU0-JhQwz4B1Scg.png" /><figcaption>After deleting the section for the package to be upgraded(left), and After running yarn (right)</figcaption></figure><p>Our package has now <strong>upgraded</strong> to the latest version.</p><p><em>[ </em><strong><em>Note: </em></strong><em>This will only upgrade to the latest minor/patch version. ]</em></p><p><strong>Case 2<br></strong>A package which has multiple versions in yarn.lock.</p><p>Say you wanted to upgrade acorn package instead. As you can see it has multiple versions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T691oVMeide69QfL9DThTw.png" /><figcaption>acorn has two versions here.</figcaption></figure><ol><li>Open yarn.lock and find the section which has the package’s version, resolved, integrity, etc.</li><li>Delete the all the sections for the package, in our example acorn</li><li>Run yarn</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1LY1MI_3FIi5yYd4kVmzUw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nszoUftwf6SzB6vvIl9A4w.png" /><figcaption>After deleting all the sections for the package acorn(left), and after running yarn(right)</figcaption></figure><p>This will upgrade the package version in each section to the latest minor/patch version.</p><h3><strong>Okay, But how can I upgrade all the sections to the latest version?</strong></h3><p>This is a bit tricky/experimental, and the process involves upgrading the packages in the dependency chain one by one following the steps mentioned above.</p><p>To find the dependency chain run =&gt;yarn why acorn</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1dTSuEs9RokQxw9hsSgm-Q.png" /></figure><p>This will give you the dependency chain.</p><p>For acorn@5 we have the chain as:<br>jest#jest-cli#jest-config#jest-environment-jsdom#jsdom#acorn</p><p>Now we need to start upgrading the packages from right to the left following the steps mentioned above unless the package dependency upgrades to the lastest.</p><p><strong><em>Please test your application thoroughly as the dependencies are updated.</em></strong></p><p><strong>Note:</strong> The dependent packages are not immediately updated as soon as a new package is published. So after a point, you have to either wait for the developer to update the package or raise a pull request to move things faster.</p><h3><strong>FAQ</strong></h3><p><strong>What if I delete and rebuild the yarn.lock file, this upgrades my packages too?<br></strong>Never do this. This will lead to the catastrophic failure of your application. This upgrades all the packages to the latest versions which might have breaking changes and your application stops working.</p><p><strong>I don’t use yarn.lock, I never faced any issues, do I really need this?<br></strong>Yes you need the yarn.lock if you use yarn, each time you are running the command yarn install you are installing the latest packages of each dependency, this will also lead to application failure.<br>Your application is tested for a particular version of a package. Say the latest version of a package was buggy and your application has installed it, without yarn.lock you will always install the latest available.</p><p><strong>Can I use the same process for Github&#39;s Security Alerts?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gx1OtwTAI6VGEZYazVIGPQ.png" /></figure><p>Yes, the process for fixing these security alerts is the same as mentioned above.</p><p>This also involves upgrading the indirect dependencies. Sometimes, if you are lucky, Github&#39;s dependabot creates a Pull Request for you, doing the same thing.</p><p><strong>Is the process safe?<br></strong>Yes, say if you were installing that main package jsdom for the first time, the latest of the deep dependent package acorn would have been installed.</p><p><strong>Why Can’t I directly upgrade the top-level package in the dependency chain</strong><strong>jest#jest-cli#jest-config#jest-environment-jsdom#jsdom#acorn ?</strong><br>The answer is that <em>you can, but you shouldn’t</em> <em>ideally</em> unless you are ready to upgrade the main package. Say you were on jest@20.x.x and the latest is jest@25.x.x, jumping 5 major versions up generally brings up breaking API changes, so unless you haven’t planned to upgrade the package you should stick to upgrading the deep dependency if that was the aim.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b5983d5fb6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Move Directory from one repository to another, preserving git-history]]></title>
            <link>https://medium.com/@ayushya/move-directory-from-one-repository-to-another-preserving-git-history-d210fa049d4b?source=rss-8b1488a3e86d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d210fa049d4b</guid>
            <category><![CDATA[repositories]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Ayushya Jaiswal]]></dc:creator>
            <pubDate>Tue, 11 Jun 2019 20:21:55 GMT</pubDate>
            <atom:updated>2019-06-12T17:21:28.248Z</atom:updated>
            <content:encoded><![CDATA[<h3>Move files from one repository to another, preserving git history</h3><p>In the multi-repository project structure, its only a matter of time when you’ll want to refactor some files from one project to another. <br>Today at <a href="https://medium.com/u/c6a9bf934df7">Instamojo.com</a> we reached a point when we start to split our large repository into several small sub-projects.</p><p>When we simply try to move files from one repository to another we lose the entire history of that particular file, and we can’t trace it back anymore.</p><p>Moving the files with history to a different repository requires the following steps:</p><h3>Getting files ready to move from <strong>Repository A.</strong></h3><p><strong>Step 1: </strong>Make a copy of repository A as the following steps make major changes to this copy which you <em>should not push</em>!</p><pre>mkdir cloneA<br>cd cloneA</pre><pre>git clone --branch &lt;branch&gt; --origin origin --progress \<br>  -v &lt;git repository A url&gt;<br># eg. git clone --branch master --origin origin --progress \<br>#   -v https://github.com/username/myproject.git</pre><pre># (assuming myprojects is the repository you want to copy from)</pre><p><strong>Step 2: </strong>Go to that directory.</p><pre>cd &lt;git repository A directory&gt;<br>#  eg. cd myproject<br># Folder Path is ~/cloneA/myproject</pre><p><strong>Step 3: </strong>To avoid accidentally making any remote changes (eg. by pushing), delete the link to the original repository.</p><pre>git remote rm origin</pre><p><strong>Step 4: </strong>Go through your history and files, removing anything that is not in FOLDER_TO_KEEP. The result is the contents of FOLDER_TO_KEEP spewed out into the base of repository A.</p><pre>git filter-branch --subdirectory-filter &lt;directory&gt; -- --all<br># eg. git filter-branch --subdirectory-filter subfolder1/subfolder2/FOLDER_TO_KEEP -- --all</pre><p><strong>Step 5:</strong> Clean the unwanted data.</p><pre>git reset --hard<br>git gc --aggressive <br>git prune<br>git clean -fd</pre><p><strong>Step 6:</strong> Move all the files and directories to a NEW_FOLDER which you want to push to repository B.</p><pre>mkdir &lt;base directory&gt;<br>#eg mkdir NEW_FOLDER</pre><pre>mv * &lt;base directory&gt;</pre><pre>#eg mv * NEW_FOLDER</pre><p>Alternatively, you can drag all the files and directory to the NEW_FOLDER using GUI.</p><p><strong>Step 7:</strong> Add the changes and commit them.</p><pre>git add .<br>git commit</pre><h3>Merge the files into the new repository B.</h3><p><strong>Step 1:</strong> Make a copy of repository B if you don’t have one already.</p><pre>mkdir cloneB<br>cd cloneB</pre><pre>git clone &lt;git repository B url&gt;<br># eg. git clone <br><a href="https://github.com/ayushya/logan.git">https://github.com/username/newproject.git</a></pre><p><strong>Step 2:</strong> Go to that directory.</p><pre>cd &lt;git repository B directory&gt;<br>#  eg. cd newproject<br># Folder Path is ~/cloneB/newproject</pre><p><strong>Step 3:</strong> Create a remote connection to <em>repository A</em> as a branch in <em>repository B.</em></p><pre>git remote add repo-A &lt;git repository A directory&gt;<br># (repo-A can be anything - it&#39;s just a random name)<br><br># eg. git remote add repo-A ~/cloneA/myproject</pre><p><strong>Step 4:</strong> Pull files and history from this branch (containing only the directory you want to move) into repository B.</p><pre>git pull repo-A master --allow-unrelated-histories<br># This merges master from repository A into repository B</pre><p><strong>Step 5:</strong> Remove the remote connection to repository A.</p><pre>git remote rm repo-A</pre><p><strong>Step 6:</strong> Finally, push the changes</p><pre>git push</pre><p>You can delete both the cloned repositories.</p><p>The files changes with history are now available online in repository B.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d210fa049d4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Journey towards upgrading to React-16]]></title>
            <link>https://medium.com/@ayushya/journey-towards-upgrading-to-react-16-fe7fef89121a?source=rss-8b1488a3e86d------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe7fef89121a</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react-fiber]]></category>
            <category><![CDATA[instamojo]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[reactjs]]></category>
            <dc:creator><![CDATA[Ayushya Jaiswal]]></dc:creator>
            <pubDate>Tue, 12 Dec 2017 20:14:47 GMT</pubDate>
            <atom:updated>2017-12-12T20:40:23.214Z</atom:updated>
            <content:encoded><![CDATA[<p>This began an year back when <a href="https://medium.com/u/6025bd347b9a">Andrew Clark</a> fascinated all of us by architecting <a href="https://github.com/acdlite/react-fiber-architecture">React-Fiber</a>.<br>We all waited for this major change to come alive.</p><p>On April 8th 2017, React <a href="https://github.com/facebook/react/releases/tag/v15.5.0">v15.5.0</a> was released and which deprecated:</p><pre>`React.createClass` and `React.PropTypes`</pre><p>We started migrating our codebase to get rid of the deprecation warnings and waited for other libraries to migrate to latest version too.</p><p>React had a critical bug from <a href="https://github.com/facebook/react/releases?after=v15.5.2">v15.5.0 — v15.5.3</a>, we directly migrated to stable <a href="https://github.com/facebook/react/releases/tag/v15.6.1">v15.6.1</a> when we were ready with the changes, it was a lot of work since it involved changes in almost every other React Component with PropTypes defined.</p><p>On 26th Sep 2017, <a href="https://github.com/facebook/react/releases/tag/v16.0.0">v16.0.0</a> was released, it was <a href="https://reactjs.org/blog/2017/09/26/react-v16.0.html">33%</a> smaller and performant than <a href="https://github.com/facebook/react/releases/tag/v15.6.1">v15.6.1</a>.</p><p>We were excited to do this migration, and we updated to <a href="https://github.com/facebook/react/releases/tag/v16.2.0">v16.2.0</a>. Since we had already fixed all files wherever deprecation warning was thrown earlier, we found the migration very easy. But we saw a lot of <a href="https://www.npmjs.com/">npm</a> warning while installing packages which was due to version incompatibility with React <a href="https://github.com/facebook/react/releases/tag/v16.0.0">v16.0.0</a> and above.</p><p>We also upgraded a lot of libraries and pushed React <a href="https://github.com/facebook/react/releases/tag/v16.2.0">v16.2.0</a> to production.</p><h3>The Error:</h3><p>At <a href="https://medium.com/u/c6a9bf934df7">Instamojo.com</a> we support a wide range of browsers, older browsers such as IE10 as well. Within 4 hours of release, we started receiving error-logs from clients at <a href="https://sentry.io/">Sentry</a>, we quickly reverted back to old <a href="https://github.com/facebook/react/releases/tag/v15.6.1">v15.6.1</a>. <br>Upon investigating we found “only the browsers which doesn’t support ES6” were failing. This was very strange because we used Babel to transpile our code to ES5. <br>We investigated further and found that in our webpack config babel-loader has excluded node_modules from being transpiled, and that is the correct behaviour because as a standard all the libraries publish in ES5.</p><p>We were using <a href="https://github.com/punkave/sanitize-html">sanitize-html</a>, newer version(1.16+) of it was using ES6 without transpiling to ES5. I reverted back to older version of <a href="https://github.com/punkave/sanitize-html">sanitize-html</a> and pushed React <a href="https://github.com/facebook/react/releases/tag/v16.2.0">v16.2.0</a> to production again.</p><p>We saw multiple developers <a href="https://github.com/punkave/sanitize-html/issues/189">complaining about the same issue</a>, so we raised a <a href="https://github.com/punkave/sanitize-html/pull/190">PR</a> to Babelify the library. Thanks to <a href="https://medium.com/u/fd07c1cedeb6">Tom Boutell</a> for quickly merging and publishing the <a href="https://github.com/punkave/sanitize-html#changelog">changes</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9dZFH3VWXjDH1A7QXD1vxw.png" /><figcaption>v1.16.2</figcaption></figure><p>This time it was stable and <a href="https://medium.com/u/c6a9bf934df7">Instamojo.com</a> is currently running on the latest <a href="https://github.com/facebook/react/releases/tag/v16.2.0">v16.2.0</a>.</p><p>A special thanks to <a href="https://medium.com/u/46afe9f523d">Aakash Goel</a> for helping me throughout.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe7fef89121a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating from compass to node-sass]]></title>
            <link>https://medium.com/@ayushya/migrating-from-compass-to-node-sass-4dadae9e8fb7?source=rss-8b1488a3e86d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dadae9e8fb7</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[node-sass]]></category>
            <category><![CDATA[compass]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[compass-to-node-sass]]></category>
            <dc:creator><![CDATA[Ayushya Jaiswal]]></dc:creator>
            <pubDate>Fri, 17 Nov 2017 04:59:55 GMT</pubDate>
            <atom:updated>2017-11-17T07:20:11.424Z</atom:updated>
            <content:encoded><![CDATA[<p>Compass is <a href="https://github.com/Compass/compass">long gone</a>, Jan 16 2015 to be precise.</p><p>We at <a href="https://www.instamojo.com/">Instamojo</a> were using it since 2012 and were linking the compiled CSS directly in the HTML without using <a href="https://webpack.js.org/">webpack</a>.</p><p>We wanted to reduce the size of initial css for a faster experience and load the route specific css dynamically via webpack. For this we have to switch over to node-sass.</p><h3>Removing Compass</h3><p>Primarily compass was used for prefixing the CSS3 properties. Since those are no longer needed now, i compiled a list of compass mixins that would need to be replaced:</p><ul><li>@include box-shadow(VALUE); -&gt; box-shadow: VALUE;</li><li>@include border-radius(VALUE); -&gt; border-radius: VALUE;</li><li>@include background-image(VALUE); -&gt; background-image: VALUE;</li><li>@include transform(VALUE); -&gt; transform: VALUE;</li><li>@include transition(VALUE); -&gt; transition: VALUE;</li><li>@include border-top-right-radius(VALUE); -&gt; border-top-right-radius: VALUE;</li></ul><p>So all i needed was find and replace this in my project.</p><blockquote>// Compass mixin <br>@include box-shadow(0 3px 15px 0 rgba(0,0,0,0.1));</blockquote><blockquote>// This becomes regular CSS without prefixes <br>box-shadow: 0 3px 15px 0 rgba(0,0,0,0.1);</blockquote><p>We used compass for generating image sprites too, so we moved to <a href="https://github.com/Ensighten/grunt-spritesmith">grunt-spritesmith</a> for generating sprites.</p><h3>The Performance difference after Migration</h3><p>We saw a magnificent difference after moving to node-sass.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HMwRhrZdWyWe-BX6jCpueQ.png" /><figcaption>Using Compass it took 75 seconds</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oOdTWcXj_Q4tgmFNXJOKSQ.png" /><figcaption>Using node-sass it took just 9.2 seconds</figcaption></figure><p>So its about <strong>~88% faster</strong> compilation using node-sass than compass locally.</p><p>Then after pushing to <a href="https://www.circleci.com/">CircleCI</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FeVA7F9TITXmXsGkWilgvA.png" /><figcaption>Using Compass it took 98.9 seconds</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1aYgyUG2PxcPHG6KVNClrQ.png" /><figcaption>Using node-sass it took 10.4 seconds</figcaption></figure><p>CSS compilation became <strong>~89% faster</strong> on CircleCI.</p><p>Gotta admit, it was kind of a fun little refactoring project. But it really feels great to take a step towards a more modern, JS/Node based front-end than being dependent on deprecated Ruby based Compass.</p><p>The code went live, yesterday morning 16th November ‘17.</p><p>A special thanks to <a href="https://medium.com/u/ea17deaeaa97">@kingsidharth</a> for encouraging and helping me to put my first story on Medium.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dadae9e8fb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>