<?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 Peter Tasker on Medium]]></title>
        <description><![CDATA[Stories by Peter Tasker on Medium]]></description>
        <link>https://medium.com/@petetasker?source=rss-e3bdfe7f3308------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4uTvLtID9ViJpji0DXd6sg.jpeg</url>
            <title>Stories by Peter Tasker on Medium</title>
            <link>https://medium.com/@petetasker?source=rss-e3bdfe7f3308------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:38:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@petetasker/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[Nginx, Let’s Encrypt and taking my own server down ]]></title>
            <link>https://medium.com/@petetasker/nginx-lets-encrypt-and-taking-my-own-server-down-ec24368be418?source=rss-e3bdfe7f3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec24368be418</guid>
            <dc:creator><![CDATA[Peter Tasker]]></dc:creator>
            <pubDate>Tue, 10 Apr 2018 00:49:15 GMT</pubDate>
            <atom:updated>2018-04-10T00:49:17.523Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kNXBynZRMspDoPmV.jpg" /></figure><p><a href="https://unsplash.com/@simonfitall?utm_medium=referral&amp;utm_campaign=photographer-credit&amp;utm_content=creditBadge">unsplash-logoSimon Fitall</a></p><p>If you pay attention to <a href="https://fourdots.com/blog/why-you-need-ssl-to-rank-better-in-2016-and-how-to-set-it-2169">Google and it’s indexing rules</a>, you’ve probably heard that you need an SSL certificate on your site. I’ve known this for a while and my personal site at petetasker.com wasn’t a high priority situation.</p><p>Welp, I was bored one night and decided it was about time to get one of those fancy-pants free <a href="https://letsencrypt.org/">Let’s Encrypt</a> cert’s installed on my old Linode server.</p><p>There are tons of resources on the internet that outline how to get an SSL certificate installed on your site, so I’m not going to go over that portion. What I will go over is how blindly following them can take down your server…</p><p>You see, most tutorials want you to use <a href="https://certbot.eff.org/">Certbot</a> to install your certificate and configure Nginx.</p><p>certbot --nginx -d petetasker.com</p><p>Seems harmless enough, no? That little --nginx flag, if you didn&#39;t read the fine print, will modify your virtual host config. Yeah. There&#39;s an option when setting up the certificate to redirect all HTTP traffic to HTTPS, and obviously I said &#39;sure&#39;.</p><p>And queue the redirect loop. Site monitor email deluge, Twitter ‘the site is DOWN’ DM’s…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*spqKNVwpJVAbqVkv.png" /></figure><p>Everything is going swimmingly!</p><p>I managed to solve this issue by removing the following block in the /etc/nginx/sites-available/petetasker.com virtual host declaration:</p><pre>if ($host = petetasker.com) {<br>       return 301 https://$host$request_uri;<br>    } # managed by Certbot</pre><p>And adding a simpler redirect block, just to be <em>reallllly</em> clear, at the top of the file:</p><pre>server{<br>        listen 80;<br>        server_name petetasker.com;<br>        return 301 https://$server_name$request_uri;<br>}</pre><p>So what’s the lesson here kids? The lesson is that if you’re using a tool that will ‘automagically’ do something for you, and it sounds too good to be true, it probably is.</p><p>If you’re wondering what the final virtual host block looks like:</p><pre>server{<br>        listen 80;<br>        server_name petetasker.com;<br>        return 301 https://$server_name$request_uri;<br>}<br>server {<br><br>        listen 80 default_server;<br>        #listen [::]:80 default_server ipv6only=on;<br>        server_name  petetasker.com www.petetasker.com;<br><br>        server_name  petetasker.com www.petetasker.com;<br>        root /usr/share/nginx/sites/petetasker.com;<br>        index index.php index.html;<br><br>        location / {<br>                try_files $uri $uri/ /index.php?$args;<br>        }<br><br>        location ~ \.php$ {<br>                try_files $uri =404;<br>                fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;<br>                fastcgi_index index.php;<br>                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;<br>                include fastcgi_params;<br>        }<br><br>    listen [::]:443 ssl ipv6only=on; # managed by Certbot<br>    listen 443 ssl; # managed by Certbot<br>    ssl_certificate /etc/letsencrypt/live/petetasker.com-0001/fullchain.pem; # managed by Certbot<br>    ssl_certificate_key /etc/letsencrypt/live/petetasker.com-0001/privkey.pem; # managed by Certbot<br>    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot<br>    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot<br><br>}</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec24368be418" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using async await with jQuery’s $.ajax]]></title>
            <link>https://medium.com/@petetasker/using-async-await-with-jquerys-ajax-dd9823fe31bf?source=rss-e3bdfe7f3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd9823fe31bf</guid>
            <dc:creator><![CDATA[Peter Tasker]]></dc:creator>
            <pubDate>Thu, 14 Dec 2017 17:26:01 GMT</pubDate>
            <atom:updated>2017-12-14T17:26:03.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_UDOcYmtXLWKEm6l.jpg" /></figure><p>Photo by <a href="https://unsplash.com/photos/2vmT5_FeMck?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Denys Nevozhai</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>If you’re like me, you’re probably stuck using jQuery more often than not. It’s everywhere, and to be honest it’s a solid, mature library. It’s also often already loaded on the page, especially if you’re working with WordPress.</p><p>Outside of DOM manipulations (which you can now do <em>mostly</em> with native JS), jQuery’s $.ajax() method is really handy and works well.</p><p>But did you know that this function provides Promise interface out of the box? I recently remembered this and I thought to myself:</p><blockquote>Hmm I wonder if I can use async/await with jQuery’s $.ajax().</blockquote><p>Turns out, you can!</p><h4>The setup</h4><p>Async/await is really new still, it’s only in the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function">ES2017 spec</a>, so you’ll need to use a <a href="https://scotch.io/tutorials/javascript-transpilers-what-they-are-why-we-need-them">transpiler</a> like <a href="https://babeljs.io/">Babel</a> to get it working in older browsers. Most of us are using Babel anyway with our bundlers (<a href="https://babeljs.io/docs/setup/#installation">Webpack</a>, Browserify), so this isn’t a huge deal.</p><p>Assuming you already have Babel installed and configured, the first thing you’ll need to do is get Babel to use the ‘env’ preset. In your .babelrc file, add these lines:</p><pre>{<br>...<br>&quot;presets&quot;: [&quot;babel-preset-env&quot;],<br>...<br>}</pre><p>You’ll also have to install this Babel preset and polyfill from npm: npm i -D babel-preset-env babel-polyfill.</p><p>Once that’s done you’ll also need to install this <a href="https://babeljs.io/docs/plugins/transform-async-to-generator/">magic plugin</a> for Babel: npm i -D babel-plugin-transform-async-to-generator. This is the key package that lets you use async/await in your code. I should mention that this simply gets Babel to compile the async/await syntax to ES2015 generators, so if you&#39;re not targeting most modern browsers keep that in mind.</p><p>The next, and <em>FINAL</em> thing you need to do is use the babel-polyfill module in your code. You can use a Webpack loader if you like, or just include the package in your source files:</p><pre>import &#39;babel-polyfill&#39;;</pre><p>Phew!</p><p>Ok, now we’re ready to go. Start up Webpack and let’s start using async/await!</p><h4>Don’t call me, maybe</h4><p>Back in the day you had to use $.ajax() like this:</p><pre>//Function wrapper that confuses alot of devs because async code works differently<br>function doAjax() {<br>    $.ajax({<br>        url: ajaxurl,<br>        type: &#39;POST&#39;,<br>        data: {<br>            stuff: &quot;here&quot;<br>        },<br>        success: function (data) {<br>            //wacky nested anonymous callbacks go here<br>            var something_but_not_really = data;<br>        },<br>        error: function (jqXHR, textStatus, errorThrown) {<br>            // Empty most of the time...<br>        }<br>    });<br><br>    return something_but_not_really<br>}</pre><p>I know when I was a junior dev I had no idea why something_but_not_really was undefined. I had to learn about callbacks a billion times 😬.</p><p>But now…</p><pre>async function doAjax(args) {<br><br><br>    const result = await $.ajax({<br>        url: ajaxurl,<br>        type: &#39;POST&#39;,<br>        data: args<br>    });<br><br>    return result;<br>}</pre><p>And result <em>actually</em> returns the AJAX result. Cool right?</p><p>The big benefit of async/await is that it makes asynchronous code <em>appear</em> synchronous. As in, do this thing, wait for it to finish and then give me the result.</p><h4>Errors</h4><p>Notice anything missing in our new function? Yep, error handling is non-existent. Fortunately, since async/await is essentially synchronous, you can use try...catch()!!!</p><pre>async function doAjax(args) {<br>    let result;<br><br>    try {<br>        result = await $.ajax({<br>            url: ajaxurl,<br>            type: &#39;POST&#39;,<br>            data: args<br>        });<br><br>        return result;<br>    } catch (error) {<br>        console.error(error);<br>    }<br>}</pre><p>And there you have it. Some error catching built in. Now, there’s other ways to handle errors with async/await, but they’re a <a href="http://blog.grossman.io/how-to-write-async-await-without-try-catch-blocks-in-javascript/">little more complex</a>.</p><p>The other thing to keep in mind now, since we’re returning the result of an awaited function, result will equal a <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise">Promise instance</a>. You have 2 options with what you can do with the result.</p><p>The first option is to make sure that you use await when calling doAjax() later on.</p><pre>// Elsewhere in code, inside an async function<br>const stuff = await doAjax();</pre><p>The other option is to use the Promise interface and roll that way:</p><pre>doAjax().then( (data) =&gt; doStuff(data) )</pre><p>Promises aren’t all that bad, and can look cleaner or be easier to work with, depending. I’ve found that using ES2015 classes it’s sometimes easier to use the Promise interface, so YMMV.</p><p>But that’s it — go get your $.ajax() using async/await today!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd9823fe31bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript’s cryptic ‘this’ — what, when and why]]></title>
            <link>https://medium.com/@petetasker/javascripts-cryptic-this-what-when-and-why-e0aa14aff57d?source=rss-e3bdfe7f3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0aa14aff57d</guid>
            <dc:creator><![CDATA[Peter Tasker]]></dc:creator>
            <pubDate>Thu, 30 Nov 2017 20:30:18 GMT</pubDate>
            <atom:updated>2017-11-30T21:29:15.281Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zHmsBjnwYl452CIZ.jpg" /></figure><p>*Photo by Tarun Ram on Unsplash</p><p>Before MDN started to organize their JavaScript documentation, finding answers to your JavaScript questions often landed you on Stack Overflow.</p><p>Welp, these days MDN has mostly done away with that practice, that is, except if you’re looking for answers around the usage of this.</p><p>The <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/this">documentation is great</a>, it really is, but it’s not exactly full of helpful, real-world examples. So I thought I’d put together a few tips and tricks about the ever so magical this keyword.</p><h4>Old-skool JS</h4><blockquote>“Back in my day we had to alert out our objects!”</blockquote><p>Ok, so yeah, if you run console.log(this) in your dev console you&#39;ll <em>generally</em> see that by default, this = Window{}. Super helpful 😏.</p><p>It gets more interesting when you check inside a function:</p><pre>function mahFunc(){<br>    console.log(this);<br>}<br><br>mahFunc();<br>// Window{}</pre><p>You should still see the Window object. Ok so, nothing new here.</p><p>But what if you add &#39;use strict&#39;?</p><pre>function mahFunc(){<br>    &#39;use strict&#39;<br>    console.log(this);<br>}<br>// undefined</pre><p>Ok, but if what if you call mahFunc() on the Window global (since it&#39;s a global function)?</p><pre>function mahFunc(){<br>    &#39;use strict&#39;<br>    console.log(this);<br>}<br><br>window.mahFunc();<br>// Window</pre><p>Huh? Strict mode is a funny beast, but generally makes errors more obvious and cleans up your JavaScript. Something not mentioned in the MDN docs is that bundlers/loaders/concatenators like Webpack/Browserify, may have strict mode enabled by default. So keep an eye out if you ever see your this variable returning something funny.</p><h4>Call me plz</h4><p>Ok so this in a global context is weird, but who doesn&#39;t use objects and ES2015+ classes these days? If you&#39;d like to use a <em>different</em> value for this, (as-in not undefined or Window) inside your function, you can pass a context with .call() and .apply(). I always remember these with &#39;yadda-yadda.prototype.call()&#39;.</p><pre>function mahFunc(){<br>    console.log(this);<br>}<br><br>const config = {<br><br>    stepOne(){<br>        //do step one<br>    },<br><br>    stepTwo(){<br>        //do step 2<br>    }<br>}<br><br>mahFunc.call(config);<br><br>//{stepOne: ƒ, stepTwo: ƒ}</pre><p>This way you’re able to specify a context for a function. It’s super handy and what a lot of frameworks and bundlers use internally — check out your Webpack bundles!</p><p>I won’t go over all the possible cases/uses of this, there&#39;s quite a few and the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/this">MDN doc</a> is quite good.</p><p>It’s important to remember this 🙄.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0aa14aff57d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open Source and Visual Studio Code]]></title>
            <link>https://medium.com/@petetasker/open-source-and-visual-studio-code-cf8a1f1da667?source=rss-e3bdfe7f3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf8a1f1da667</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[visual-studio-code]]></category>
            <dc:creator><![CDATA[Peter Tasker]]></dc:creator>
            <pubDate>Tue, 21 Nov 2017 19:51:03 GMT</pubDate>
            <atom:updated>2017-11-21T20:29:29.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*5abJbp0C_yYTI20gZ0vXUQ.png" /><figcaption>Open Source PHP Extensions</figcaption></figure><h3>Open Source, PHP and Visual Studio Code</h3><p>Lately, [VS Code](<a href="https://code.visualstudio.com/">https://code.visualstudio.com/</a>) has been getting a lot of hype in the dev community. It’s been around since for a few years and TBH is a really sweet editor. Lots of great extensions and community support. It’s also quite fast (for an Electron app 😬) and the peeps and Microsoft seem to be keeping it up to date and iterating quickly.</p><p>However, anything you _really need_ to work with PHP is missing by default. I believe this is by design to encourage a vibrant extensions community. Luckily, like most languages, there’s a vibrant open source PHP extension community. There’s a few great extensions for PHP: [PHP IntelliSense](<a href="https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-intellisense">https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-intellisense</a>), [PHP Debug](<a href="https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-debug">https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-debug</a>) (both by the [same developer](<a href="https://github.com/felixfbecker">https://github.com/felixfbecker</a>)) as well as [PHP Intelliphense](<a href="https://marketplace.visualstudio.com/items?itemName=bmewburn.vscode-intelephense-client">https://marketplace.visualstudio.com/items?itemName=bmewburn.vscode-intelephense-client</a>) (#wat?). There’s even a really great intro by [Jeffrey Way on Laracasts](<a href="https://laracasts.com/series/visual-studio-code-for-php-developers">https://laracasts.com/series/visual-studio-code-for-php-developers</a>) outlining everything you need to do to get VS Code set up for PHP dev.</p><p>Some of the PHP packages work fine and have over a million installs (!!!). Sometimes, however, they _don’t_ work. Like, at all. Just today, the PHP Debug extension completely broke. Luckily the developer was paying attention and rolled out a fix within hours. Pretty awesome support for an open-source product!</p><p>However, if you paid for the editor, say something like PHPStorm, you could go and raise an issue on their support channel. You could complain about the product not working, rightly so, as you’ve paid for the right! As a ‘customer’ you have a certain amount of clout with a vendor like Jetbrains. This is _NOT_ the case with open source, and I feel that we developers forget this.</p><p>This is where I take issue. I’m all for open source software. I’ve built my career on it. The issue is that the developer for this plugin had to fix the issue himself. There’s an expectation there that he _HAS_ to fix the issue, and do it RIGHT NOW. And if it’s not done immediately people freak out, complain on Twitter, write a blog post about, have a cow 🐮, man.</p><p>Open source is just that, open. If you find an issue with a plugin, editor, extension or WHATEVER, see if you can fix it! That’s the whole point. Let’s not throw our hands up and complain, let’s get our hands dirty and fix the damn thing.</p><p>That’s what open source is all about. Let’s remember that.</p><p>/rant</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf8a1f1da667" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PHPStorm, MAMP and Xdebug — How to keep (some of) your hair]]></title>
            <link>https://medium.com/@petetasker/phpstorm-mamp-and-xdebug-how-to-keep-some-of-your-hair-faae7c25f118?source=rss-e3bdfe7f3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/faae7c25f118</guid>
            <dc:creator><![CDATA[Peter Tasker]]></dc:creator>
            <pubDate>Mon, 16 Oct 2017 17:57:14 GMT</pubDate>
            <atom:updated>2017-10-16T17:57:16.519Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>I’m mostly logging this here for my own benefit, but if the Google gods brought your here, sweet!</blockquote><p>Just came across another fun quirk with running Xdebug, MAMP and PHPStorm together. 😅😅😅😅</p><p>I’ve talked about this combination causing me <a href="http://petetasker.com/mamp-xdebug-phpstorm-and-symlink-madness/">issues in the past</a>, but this is a whole new situation that killed a couple hours for me.</p><p>So, it appears that for PHPStorm to pick up Xdebug correctly, the xdebug.remote_host variable needs to be set correctly. It normally is, if you copy-pasta some of the tutorials on the internet.</p><p>Unfortunately, for some reason, this Monday morning, setting this value to localhost no longer worked. Why? Welp, localhost is pointing to an invalid folder location, according to MAMP. Apparently this was enough for PHPStorm to freak out and just not run Xdebug. Period.</p><p>Fun!</p><p>So how’d I figure out this was the reason for Xdebug throwing up?</p><p>The PHPStorm docs of course! Wayyyyy at the bottom of <a href="https://confluence.jetbrains.com/display/PhpStorm/Validating+Your+Debugging+Configuration#ValidatingYourDebuggingConfiguration-Remotehostisconfiguredas&#39;localhost&#39;despiteserverhostisprobablynotlocal">this page</a> it’s plainly stated:</p><h4>Remote host is configured as ‘localhost’ despite server host is probably not local</h4><blockquote>The URL to validation script contains something different from localhost, but the xdebug.remote_host value is not set and so is using the default value of localhost, or is set to localhost or 127.0.0.1.</blockquote><p><a href="https://www.youtube.com/watch?v=pU96c_3RXXU">#themoyouknow</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*w-3DSmv8IrWDBIkm.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faae7c25f118" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript build tooling and the CLI]]></title>
            <link>https://medium.com/@petetasker/javascript-build-tooling-and-the-cli-cf6dc01270a3?source=rss-e3bdfe7f3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf6dc01270a3</guid>
            <dc:creator><![CDATA[Peter Tasker]]></dc:creator>
            <pubDate>Mon, 19 Jun 2017 19:10:34 GMT</pubDate>
            <atom:updated>2017-06-19T19:10:36.683Z</atom:updated>
            <cc:license>https://creativecommons.org/publicdomain/mark/1.0/</cc:license>
            <content:encoded><![CDATA[<p>Something that’s come up recently in the front-end world is the topic of a learning curve and JavaScript tooling such and <a href="https://webpack.js.org/">Webpack</a> and <a href="https://babeljs.io/">Babel</a>. While I agree that new tooling can sometimes be a pain to learn, since when did being a web developer/programmer/rockstar <em>not</em> require learning new things? I mean, learning the CLI is one thing, but it’s not suuuuper difficult and is definitely a skill that will serve you well in your career. On top of that, front-end build tooling has been around for a while, first with Grunt and then Gulp. Does Webpack make things that much more difficult?</p><p>The argument I’m making is partially around React and how Webpack (or similar) is required. To me, this doesn’t seem like a problem, as many languages <em>require</em> compilation during a build step. I see the build step and associated tooling a good thing, as it allows for more streamlined and complex programming concepts to be brought into front-end development.</p><p>If you’re worried about learning something like the Webpack build process, <a href="https://github.com/facebookincubator/create-react-app">Create React App</a> has got all the setup jank covered. In Vue, there’s <a href="https://github.com/vuejs/vue-cli">vue-cli</a> which similarly gets you set up. In both cases all it takes to get up and running is npm install then npm start. That&#39;s not too bad!</p><p>I guess what I’m saying, if all this ‘new’ stuff bothers you as a developer, it might be time to 1.) upgrade your skills, or 2.) do something else. Things aren’t slowing down any time soon in the front-end landscape, better get on the wagon or jump off!</p><p><em>Originally published at </em><a href="http://petetasker.com/javascript-build-tooling-and-the-cli/"><em>Database Critical</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf6dc01270a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>