<?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 Naor Zruk on Medium]]></title>
        <description><![CDATA[Stories by Naor Zruk on Medium]]></description>
        <link>https://medium.com/@naorzruk?source=rss-acbc85ea7e25------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*aFQntFhyw0B0dQKmlaWe1w.jpeg</url>
            <title>Stories by Naor Zruk on Medium</title>
            <link>https://medium.com/@naorzruk?source=rss-acbc85ea7e25------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:22:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@naorzruk/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[Typescript — The great ‘Unknown’]]></title>
            <link>https://medium.com/@naorzruk/typescript-the-great-unknown-8ad919103952?source=rss-acbc85ea7e25------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ad919103952</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Naor Zruk]]></dc:creator>
            <pubDate>Sat, 09 May 2020 09:06:29 GMT</pubDate>
            <atom:updated>2020-05-09T09:18:41.418Z</atom:updated>
            <content:encoded><![CDATA[<h3>Typescript — into the Unknown</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/0*EevGT9gUlFRbWO2W" /></figure><p>In this article, you’ll go on a journey with me to explore the great ‘unknown’, This journey starts with ‘unknown’ evil twin, any .</p><h3><strong>Any</strong></h3><p>Typescript brought peace and mind to javascript developers, it freed us from unsynced Jsdocs, endless read through semi documented functions and intelligent guesswork about what the hell is this result variable contains anyway.<br>It freed our minds and our poor dynamic, none static soul.</p><p>And then <strong><em>Any </em></strong>came.</p><p>Well, you see, any, is one of the weirdest things in typescript, it introduces a mechanism that dumb down the entire purpose of typescript, what do I mean by that, let’s look at the following code for example.</p><pre>const num: any = 10<br>const str: any = &#39;2&#39;<br>const obj: any = {a: 2}<br>const bol: any = false</pre><p>Given these variables, let’s try to do stuff with them, and ask the compiler what does it think</p><pre>obj + str \\ That&#39;s fine</pre><pre>str - bol + num \\ That&#39;s also fine</pre><pre>Math.pow(obj,bol) \\ Look&#39;s good to me, carry on please</pre><p>Well, You get the point.<br>With any, you can do anything, nothing really holds you down and we go straight back to using Typescript as if it was Javascript.<br>So we lose the main thing we choose Typescript for in first place, strict type-checks errors.</p><p>Now, I bet you’re wondering<br>“Then how are we going to deal with i/o or functions with any return type then”<br>That’s where unknown come’s into play</p><h3><strong><em>The Great Unknown</em></strong></h3><p>unknown in javascript, acts as the good twin of any , it tells the compiler the following variable can be of any type, but that doesn’t mean you can do anything with it, you first need to validate it’s type and only then you can move on.</p><p>Let’s look at a simple example</p><pre>function foo():unknown</pre><pre>const result = foo()</pre><pre>result + 2 // error<br>result + &#39;hello&#39; // error<br>if(typeof result === &#39;number&#39;){<br>  result + 2 // Works!<br>}</pre><p>With unknown , we get what we paid for, static typing but also the ability to communicate safely and receive results from the outside world.</p><h3><strong>Enforcing ‘Unknown’ usage</strong></h3><p>To enforce the unknown usage throughout the code simply set the following Eslint rule as part of your project</p><p><a href="https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/no-explicit-any.md">typescript-eslint/typescript-eslint</a></p><h3><strong>Final Words</strong></h3><p>I hope you enjoyed this article, if you did, Clap 👏 and Share!<br>For more articles, follow me on Medium or on <a href="https://twitter.com/ZrNaor">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ad919103952" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Javascript Proxies, Russian Roulette and some Practical examples]]></title>
            <link>https://medium.com/@naorzruk/javascript-proxies-russian-roulette-and-some-practical-examples-35f7a1e0612c?source=rss-acbc85ea7e25------2</link>
            <guid isPermaLink="false">https://medium.com/p/35f7a1e0612c</guid>
            <category><![CDATA[cool-coding-stuff]]></category>
            <category><![CDATA[cool-stuff]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[proxy]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Naor Zruk]]></dc:creator>
            <pubDate>Wed, 06 Mar 2019 14:30:43 GMT</pubDate>
            <atom:updated>2019-03-07T05:00:16.444Z</atom:updated>
            <content:encoded><![CDATA[<p>Javascript Proxies, Russian Roulette and some Practical examples</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*PeFS0b5QRUlQlWdWacXESA.jpeg" /></figure><p>For those of you who don’t know, es2015 came with a new feature named ‘proxy’<br>What proxy basically does is create an object that implements some traps ( middleware if you’d like), when accessing the object internal methods, like get, set and so on.</p><p><strong>Proxy Terminology</strong></p><p><strong>Trap</strong> — is the built in object method we’re going to change. <br>when user will access the Trapped method, our function will handle it, instead of the standard implementation. <br>one example could be putting a trap on the object <em>get </em>method<em>, </em>implementing a new behaviour, now each time someone access the object properties with dot or brackets operators, our handler will meet it.</p><p><strong>target</strong> — the object that the proxy acts upon</p><p><strong>Handler —</strong> An object containing traps</p><h3><strong>Examples</strong></h3><p>Suppose we want to store readers and their reading count in an object,<br>where the reader name is the key, and reading count is the value</p><p>instead of implementing this logic over and</p><pre>var readersCount = {}<br>somePageOnReadListener((readerName) =&gt; {<br>   if(!readersCount[readerName]){<br>      readersCount[readerName] = 1<br>   }<br>   else {<br>     readersCount[readerName]++<br>   }<br> }<br>})</pre><pre>otherPageOnReadListener((readerName) =&gt; {<br>   if(!readersCount[readerName]){<br>      readersCount[readerName] = 1<br>   }<br>   else {<br>     readersCount[readerName]++<br>   }<br> }<br>})</pre><p>we could use proxies</p><pre>// Here, set is the trap, and readersCount will be the target<br>var readersCount = new Proxy({}, {<br>    set: (target,prop,val) =&gt; {<br>      if (typeof val !== &#39;number){<br>         return<br>      }<br>      if (!target[prop]){<br>         target[prop] = 1<br>      } else {<br>         target[prop] = val <br>     }<br>   }<br>})</pre><pre>somePageOnReadListener((readerName) =&gt; {<br>   readersCount[readerName]++<br>})</pre><pre>otherPageOnReadListener((readerName) =&gt; {<br>   readersCount[readerName]++<br>})</pre><p>Proxies may be a good solution for this, since the logic in the proxy only handles redundant language specific “problems”.</p><p>this line of code</p><pre>readersCount[readerName]++</pre><p>merely does what we all expect it to do, only handling some language specific edge cases</p><p><strong>Another Example</strong></p><p>suppose we want to keep an object under track, and each time one of it’s properties change(only on the shallow object level), print it out</p><pre>new Proxy({}, {<br>    set: (target,prop,val) =&gt; {<br>        if(tar[prop] !== val){<br>         console.log(`prev value ${target[prop]}: new value ${val}`)<br>        }<br>        tar[prop] = val<br>    }<br>})</pre><p><strong>Russian Roulette</strong></p><p>Proxies can be fun too, <a href="https://github.com/naorzr/rus_roulette">here’s my implementation</a> for a russian roulette game with your code using proxies.<br>basically, you wrap a certain object with the roulette function and in return you get a new object that allows you to access the object props, only if you’re lucky that is.</p><p>For more proxy goodies you can check out this<a href="https://github.com/mikaelbr/awesome-es2015-proxy"> git repo</a> that contain a list of some cool and unique stuff implemented using proxies.</p><p><strong>Beware of Proxies Magic</strong></p><p>Since proxies return a new object, containing a new behaviour for well known language features, like getting, setting and so on, it can make the code HIGHLY unreadable.<br>I’d say that when using a proxy one should consider one of two possibilities.<br>1) declaring it in a way that won’t go unnoticed<br>2) use it to handle stuff like accessing <em>undefined</em> properties, simple string to number conversions, debugging and so on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35f7a1e0612c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Portals In React-Native]]></title>
            <link>https://medium.com/@naorzruk/portals-in-react-native-22797ba8aa1b?source=rss-acbc85ea7e25------2</link>
            <guid isPermaLink="false">https://medium.com/p/22797ba8aa1b</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[portal]]></category>
            <category><![CDATA[cool-stuff]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react-native-development]]></category>
            <dc:creator><![CDATA[Naor Zruk]]></dc:creator>
            <pubDate>Tue, 19 Feb 2019 09:22:10 GMT</pubDate>
            <atom:updated>2019-09-01T05:08:58.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*QNT3UeK47uIWzvqn9073Hw.jpeg" /></figure><p>With React context api we can implement a simple portal mechanism that would allow you to teleport a react-native element from one place to another regardless of the hierarchy.</p><p>To do so, we create a PortalProvider that will handle a table of gates, where as the gate-name would be the key, and the element to be rendered would be the value.<br>The teleportation part is pretty straight forward as well, each element inside the portal would have access to a <em>teleportation</em> <em>function</em> that could teleport an element to any given portal by name.</p><p>I’ve written everything down in typescript, for the sake of clarity.</p><p><strong>PortalContext.tsx</strong></p><pre><strong>import </strong>* <strong>as </strong>React <strong>from </strong>&#39;react&#39;<br><strong>export default </strong>PortalContext = React.createContext({<br>  gates: {},<br>  teleport: (gateName: <strong>string</strong>, element: JSX.Element) =&gt; {<br>    <strong>return<br>  </strong>}<br>})</pre><p><strong>PortalProvider.tsx</strong></p><pre><strong>import </strong>* <strong>as </strong>React <strong>from </strong>&#39;react&#39;<br><strong>import </strong>{ PortalContext } <strong>from </strong>&#39;./PortalContext&#39;<br><br><strong>interface </strong>IProps {<br>  children: JSX.Element<br>}<br><br><strong>class </strong>PortalProvider <strong>extends </strong>React.Component&lt;IProps&gt; {<br>  <strong>public </strong>state = {<br>    gates: {}<br>  }<br><br>  <strong>public </strong>render() {<br>    <strong>const </strong>{ children } = <strong>this</strong>.props<br>    <strong>return </strong>(<br>      &lt;PortalContext.Provider value={{ gates: <strong>this</strong>.state.gates, teleport: <strong>this</strong>.teleport }}&gt;<br>        {children}<br>      &lt;/PortalContext.Provider&gt;<br>    )<br>  }<br><br>  <strong>private </strong>teleport = (gateName: <strong>string</strong>, element: JSX.Element) =&gt;<br>    <strong>this</strong>.setState({ gates: { ...<strong>this</strong>.state.gates, [gateName]: element } })<br>}<br><br><strong>export default </strong>PortalProvider</pre><p>The PortalGates would display only the corresponding element from the table to their prop name.</p><p><strong>PortalGate.tsx</strong></p><pre><strong>import </strong>* <strong>as </strong>React <strong>from </strong>&#39;react&#39;<br><strong>import </strong>{ PortalContext } <strong>from </strong>&#39;./PortalContext&#39;<br><br><strong>function </strong>PortalGate(props: {<br>  gateName: <strong>string<br>  </strong>children?: (teleport: (gateName: <strong>string</strong>, element: JSX.Element) =&gt; <strong>void</strong>) =&gt; JSX.Element<br>}) {<br>  <strong>const </strong>{ gateName, children } = props<br>  <strong>return </strong>(<br>    &lt;PortalContext.Consumer&gt;<br>      {value =&gt; {<br>        <strong>return </strong>(<br>          &lt;React.Fragment&gt;<br>            {value.gates[gateName]}<br>            {children &amp;&amp; children(value.teleport)}<br>          &lt;/React.Fragment&gt;<br>        )<br>      }}<br>    &lt;/PortalContext.Consumer&gt;<br>  )<br>}<br><br><strong>export default </strong>PortalGate</pre><p>now, using it, is as simple as it gets</p><p>Wrap your app.js component with the PortalProvider</p><pre><strong>import * as React from &#39;react&#39;<br>import </strong>PortalProvider from &#39;./PortalProvider&#39;</pre><pre><strong>export default class </strong>App <strong>extends </strong>React.Component{<br><br>  <strong>public </strong>render() {<br>    <strong>return </strong>(<br>      &lt;PortalProvider&gt;<br>        &lt;App/&gt;<br>      &lt;/PortalProvider&gt;<br>    )<br>  }<br>}</pre><p>now you can generate a portal gate from anywhere in the app, and send components from anyplace to the other regardless of the hierarchy.</p><p><strong><em>Example:</em></strong><br>for example, say we want to teleport a <strong>biscuit</strong> element from the <strong>Bag</strong> to the <strong>Jar</strong>, The code would look something like this:</p><p><strong>Bag.tsx</strong></p><pre><strong>import * as React from &#39;react&#39;<br>import </strong>PortalGate from &#39;./PortalGate&#39;</pre><pre><strong>const</strong> Biscuit = &lt;View style={{ backgroundColor: &#39;red&#39;, width: 800,          height: 800 }} /&gt;</pre><pre><strong>export default </strong>() =&gt; (<br>  &lt;View&gt;<br>    &lt;PortalGate gateName={&#39;bag&#39;}&gt;<br>      {teleportFN =&gt; (<br>       &lt;TouchableOpacity<br>         style={{ width: 200, height: 200 }}<br>         onPress={() =&gt; teleportFN(‘jar’,Biscuit)}<br>     &gt;<br>    &lt;Text style={{ width: 200, height: 200 }}&gt;<br>        LET THE MAGIC BEGIN<br>    &lt;/Text&gt;<br>  &lt;/TouchableOpacity&gt;<br>)}<br>     &lt;/PortalGate&gt;</pre><pre>  &lt;/View&gt;<br>)</pre><p><strong>Jar.tsx</strong></p><pre><strong>import * as React from &#39;react&#39;<br>import </strong>PortalGate from &#39;./PortalGate&#39;</pre><pre><strong>export default </strong>() =&gt; (<br>  &lt;View&gt;<br>    &lt;PortalGate gateName={&#39;jar&#39;}/&gt;<br>  &lt;/View&gt;<br>)</pre><p><strong>Final Thoughts</strong></p><p>Well that was it, Hope you enjoyed :) and if you did! Clap and Share ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22797ba8aa1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[‘This’ keyword in javascript — Concise Summary]]></title>
            <link>https://medium.com/@naorzruk/this-keyword-in-javascript-concise-summary-d940f6690a1d?source=rss-acbc85ea7e25------2</link>
            <guid isPermaLink="false">https://medium.com/p/d940f6690a1d</guid>
            <category><![CDATA[this]]></category>
            <category><![CDATA[concise]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[short]]></category>
            <dc:creator><![CDATA[Naor Zruk]]></dc:creator>
            <pubDate>Mon, 11 Feb 2019 18:21:58 GMT</pubDate>
            <atom:updated>2019-02-13T12:38:14.301Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding ‘This’ keyword in javascript — Summary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*qVdGsrSLm7tp48EYjN4PWA.jpeg" /></figure><p>This is my brave attempt at summarizing and explaining the ‘this’ keyword in javascript for you busy people in under 3 minutes, let’s begin.</p><ol><li><strong>Implicit Binding</strong> — When using <strong><em>this</em></strong> in a function without explicit binding, <strong><em>this</em></strong> will refer to the object which the function was called from, i.e the context object(except a special case i’ll refer to later), for example:</li></ol><pre>function foo(){<br>  console.log(this)<br>}<br>var obj = {foo}<br>foo() // global object (or undefined in strict mode)<br>obj.foo() // obj {foo}</pre><p>2. <strong>Explicit binding </strong>— with explicit binding it’s a no brainer, <strong><em>this</em></strong> will refer to the object it was bound to. <br>you can bind ‘<strong><em>this</em></strong>’ with Object.call(), Object.apply() or bind().</p><pre>function foo(){<br>  console.log(this)<br>}<br>var obj = {a: 2}<br>Object.call(foo,obj) // {a: 2}</pre><p>just note that using <strong><em>bind </em></strong>will return a hard bounded function, which can be a little confusing if you weren’t aware of the fact that the <strong><em>this </em></strong>inside was already bounded.</p><p>3.<strong>Arrow Functions</strong> — This is the most confusing one.</p><p>With regular functions you get an implicit ‘<strong><em>this</em></strong>’ binding, which is bound to the context the function was called.<br>With es6 arrow functions, <strong><em>‘this’</em></strong><em> is not bound to the context the function was called </em>but rather, <strong><em>‘this’ </em></strong><em>will be equal to the lexical scope ‘</em><strong><em>this</em></strong><em>’ it was defined in</em>.</p><p>consider this</p><pre>// foo1 is the lexical scope, and implicitly, foo1 &#39;this&#39; is the <br>// global object.<br>function foo1(){<br>   var a = () =&gt; console.log(this)<br>   a()<br>}</pre><pre>function foo2(){<br>   console.log(this)<br>}</pre><pre>var obj1 = {bunnies: 2, foo1, foo2}</pre><pre>obj1.foo1() // global object or undefined<br>obj1.foo2() // obj1</pre><p>and here is another example:</p><pre><strong>var </strong>obj = {<br>  c: <strong>function </strong>FOO() {<br>    <strong>var </strong>arrFunc = () =&gt; console.log(<strong>this</strong>)<br>    arrFunc()<br>  }<br>}</pre><pre>obj.c() // obj</pre><pre>// simple &#39;this&#39; diagram<br>// arrFunc(lexical scope) ---&gt; function FOO(context) ----&gt; obj</pre><p>what happened here is that the function ‘FOO’ implicitly had <strong>‘this’</strong> bounded to the obj variable.<br>the inner arrow function gets the ‘<strong>this’</strong> bounded to the lexical scope ‘<strong>this’</strong>, which is the function’s ‘FOO’ <strong>‘this’, </strong>which is obj.</p><p>4. <strong>Function as Constructor </strong>— When using the ‘<strong>new</strong>’ keyword, ‘<strong>this</strong>’ will refer to the new instance of the object created</p><p>for example:</p><pre>function Foo(){<br>  this.a = 30<br>  this.rawr = () =&gt; console.log(this.a)</pre><pre>}<br>var obj = new Foo<br>obj.rawr() // prints 30</pre><p>And here’s a summary table</p><pre>+-------------------------+--------------------------------+<br>|          Case           |         This Refers To         |<br>+-------------------------+--------------------------------+<br>| Implicit Binding        | Context Object                 |<br>| Explicit Binding        | Bounded Object                 |<br>| Arrow Function          | Lexical Scope &#39;This&#39;           |<br>| Function As Constructor | Newly Created Object Instance  |<br>+-------------------------+--------------------------------+</pre><p>Found this post helpful? Clap and Share ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d940f6690a1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ejecting To ExpoKit — Expectations Vs Reality]]></title>
            <link>https://medium.com/@naorzruk/ejecting-to-expokit-expectations-vs-reality-bd8854d1dfb5?source=rss-acbc85ea7e25------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd8854d1dfb5</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[eject]]></category>
            <category><![CDATA[expo]]></category>
            <category><![CDATA[expokit]]></category>
            <dc:creator><![CDATA[Naor Zruk]]></dc:creator>
            <pubDate>Mon, 04 Feb 2019 07:48:10 GMT</pubDate>
            <atom:updated>2019-02-06T18:54:40.928Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*9zwOOpRwNwb6l88KEwkfzg.jpeg" /></figure><h3>Ejecting To ExpoKit — Expectations Vs Reality</h3><p>Expo is wonderful, it saves you all the headache of building, maintaining libraries updated and searching for good working ones.</p><p>But it has its limits, Expo can’t possibly bundle every possible react native dependancy out there, and with no ability to link them up yourself, you’re only free to add react native dependancy which are pure JS.</p><p>To solve this, there are several options.</p><p>There is an option of Ejecting to pure React Native project, which is a pain, it means replacing everything expo based you used in your project with React Native dependancies, most of the times, it’s not a simple drag and drop replacement.</p><p>There is an option of just staying in Expo, and hacking your way around.</p><p>And then, there’s the third option, ExpoKit, The promise land.</p><p>ExpoKit idea is to allow you the capability to link external react native libraries, while keeping all the expo components you’ve used throughout the project, sounds amazing isn’t it?</p><p>Well, the hard truth is, this middle ground is not so great.</p><p><strong>The Pros</strong></p><ul><li>ExpoKit allows you to link your own react native libraries</li><li>You don’t have to replace Expo components you’ve used throughout the project</li></ul><p><strong>The Cons</strong></p><ul><li>ExpoKit is monolithic, you still get the whole package of dependancies, which increase quite dramatically the build size(if you aren’t using them)</li><li>ExpoKit uses a specific react-native version(more precisely a forked version of theirs), sometimes, deciding not to upgrade to the latest RN version, which can cause issues with other libraries.</li><li>Some libraries just collide with ExpoKit, e.g rn-fetch-blob(and every library that uses it) giving out error <strong>“Incompatible types: required: okhttp3.OkHttpClient found: expolib_v1.okhttp3.OkHttpClient”,</strong> which can be solved by manually replacing stuff in your node_modules dir, but that isn’t a great idea.</li><li>Changing app root view background(on ios) can only be done by changing the app background color in expoKit pods.</li></ul><p>But not all hope is lost, <a href="https://medium.com/u/d5a707474bd2">Brent Vatne</a> in his <a href="https://blog.expo.io/expokit-2019-1e5cb02106f8">blog</a> mentions that expectedly in feb/2019, they intend on giving a better option of just ejecting to pure React Native project and replacing all expo dep.</p><p>The plan is to have expo api exposed as dependancies that can be installed separately. (Yea, it got my 50 claps with out even asking)</p><h3><strong>Final Words</strong></h3><p>Thanks to the Expo team for their amazing work and ability to listen to community needs.</p><p>Got Something To Add? Leave a comment below :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd8854d1dfb5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>