<?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 Eelan Tung on Medium]]></title>
        <description><![CDATA[Stories by Eelan Tung on Medium]]></description>
        <link>https://medium.com/@eelan.tung?source=rss-f4b970806444------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*veZNxQeREKkVw9Or.</url>
            <title>Stories by Eelan Tung on Medium</title>
            <link>https://medium.com/@eelan.tung?source=rss-f4b970806444------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:29:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eelan.tung/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[Deploying a static React Site to Google Cloud Platform]]></title>
            <link>https://medium.com/@eelan.tung/deploying-a-static-react-site-to-google-cloud-platform-ee89b480e9f2?source=rss-f4b970806444------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee89b480e9f2</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[create-react-app]]></category>
            <dc:creator><![CDATA[Eelan Tung]]></dc:creator>
            <pubDate>Sun, 11 Nov 2018 22:24:05 GMT</pubDate>
            <atom:updated>2018-11-11T22:24:05.460Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What we need:</strong></p><ul><li><a href="https://github.com/facebook/create-react-app">create-react-ap</a>p</li><li><a href="https://cloud.google.com/">Google Cloud Platform</a></li></ul><p>I’m deploying site that needs no backend server and uses React to render the Front End.</p><p>I will also be assuming that you have a React app created and ready to deploy. So let’s get on with it!</p><ol><li>Using your terminal, change into the React app’s directory and run npm run build. This will create a new folder in your directory called <strong>build</strong>. The build folder will have all the necessary files for deployment.</li><li>Go to Google Cloud Platform and navigate to the Storage option. Here, we need to create a bucket.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SBP2v98cIXtX8q64C3boRQ.png" /></figure><p>3. Fill out the name that you want for the bucket. I have named mine testing-app. Using this bucket, we can easily upload the build folder into the Google Cloud Platform.</p><p>4. Once the bucket is created, select upload files. Browse to your project directory and upload the entire build folder.</p><p>5. One thing that is necessary for deployment if an app.yaml file. This file tells the App Engine how to make the URLs to static files. As an example, mine looks like:</p><pre>runtime: python27<br>api_version: 1<br>threadsafe: true<br>handlers:<br>- url: /<br>  static_files: build/index.html<br>  upload: build/index.html<br>- url: /<br>  static_dir: build</pre><p>After this is created, upload the app.yaml file to the bucket as well.</p><p>Your bucket should currently have one build folder and one app.yaml folder:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*vvKt5yF5skNjh1CJ0EwEnQ.png" /></figure><p>Stay inside the bucket and open up the Google Cloud Shell found on the top right-hand side of the browser:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*yzGAdWtbmv4fUs5v5yjkiA.png" /></figure><p>Once the terminal opens, we need to type these following commands:</p><pre>$ mkdir test-website<br>$ gsutil rsync -r gs://testing-app ./test-website</pre><p><em>Note: The first command after the -r is the name of the bucket you just created and the second is for the destination folder.</em></p><p>Once this is finished you can cd test-website into the directory and type ls to make sure the app.yaml and build files are there.</p><p>6. You can now deploy the app by running gcloud app deploy in the shell. This will also generate a url so you can visit the app.</p><p>The url generated usually has the following format: <a href="https://[app-name].appspot.com.">https://[app-name].appspot.com.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee89b480e9f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intro to React Hooks]]></title>
            <link>https://medium.com/@eelan.tung/intro-to-react-hooks-2bf767fbf776?source=rss-f4b970806444------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bf767fbf776</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-hook]]></category>
            <dc:creator><![CDATA[Eelan Tung]]></dc:creator>
            <pubDate>Mon, 05 Nov 2018 19:53:37 GMT</pubDate>
            <atom:updated>2018-11-05T19:53:37.598Z</atom:updated>
            <content:encoded><![CDATA[<p>React Hooks were introduced the other day by the React team. Instead of using React class components to hold state, functional components can now hold state by adding hooks.</p><p>Now, instead of refactoring the whole functional component into a class, we can simply use hooks to add state into it.</p><p>Example:</p><pre>function useCounter(initialValue) {<br>   const [value, setCount] = useState(initialValue)</pre><pre>   return {<br>      value,<br>      increase: () =&gt; setCount(value + 1),<br>   }<br>}</pre><pre>export default function CounterA() {<br>  const counter = useCounter(0)<br><br>  return (<br>    &lt;div&gt;<br>      &lt;p&gt;You clicked {counter.value} times&lt;/p&gt;<br>      &lt;button onClick={counter.increase}&gt;Click me&lt;/button&gt;<br>    &lt;/div&gt;<br>  )<br>}</pre><p>The useState is used to take the initial state as an argument and returns an array of two items. The first is the current value and the other is a function that we can use to change the value.</p><p>Another feature, aside from adding state to functional components, is the use of side-effects. These side-effects were introduced in lifecycle methods, such as componentDidMount. These methods originally can only be used in class components.</p><p>With the introduction of hooks, a hook can how have its own side-effect. For example, React added a useEffect hook that can replace those lifecycle methods. For instance, you can add the useEffect hook to be fired when the component is rendered.</p><h3><strong>Conclusion</strong></h3><p>As of now, React Hooks are still in the experimental phase so we can’t add that to any app that is production. We are all in the same boat in learning how to use these new features, but it is always nice to read React’s <a href="https://reactjs.org/docs/hooks-intro.html">introduction</a> and <a href="https://reactjs.org/docs/hooks-faq.html">FAQ</a> for hooks to get familiar with hooks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bf767fbf776" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ReactJS vs React Native]]></title>
            <link>https://medium.com/@eelan.tung/reactjs-vs-react-native-c1ea8c83b7d2?source=rss-f4b970806444------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1ea8c83b7d2</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Eelan Tung]]></dc:creator>
            <pubDate>Tue, 17 Jul 2018 19:59:19 GMT</pubDate>
            <atom:updated>2018-07-17T19:59:19.920Z</atom:updated>
            <content:encoded><![CDATA[<p>ReactJS was released in 2013 as a JavaScript library that makes webpages more dynamic and responsive to user input. React Native was created two years later by the same group of engineers at Facebook. It is a hybrid mobile-app development framework for iOS and Android. The framework is based on the same principles of ReactJS.</p><p>At the most basic level, ReactJS is used for web development and React Native is used for mobile app development. Because of the different domains, there will be differences in how they are set up and how they render any specific function. But let’s take a look at the major differences between the two.</p><h4>DOM and Styling</h4><p>While React renders HTML to the DOM, React Native doesn’t use HTML. It provides alternative components that work in a similar way. For example, a View component is similar to a div tag and a Text component is similar to a p tag. These components map the actual real native iOS or Android UI components that get rendered on the app.</p><p>Because React Native doesn’t render HTML, this also means you won’t be able to use any libraries used with ReactJS that styles any kind of HTML. Instead, to style components, React Native uses Flexbox instead of CSS.</p><h4>Gestures and Animation</h4><p>The animation and gestures can be incorporated into React with the help of CSS. Because React Native does not support CSS, it uses Animated API and Pan Responder API to create all the animation and gestures.</p><h4>Database</h4><p>React can use any database as long as you create an API for the database to integrate. React Native uses Realm, which is a database specifically built to cater to server-side development. Realm runs directly inside the mobile app and does not require any additional installation.</p><h4>Other Differences</h4><p>ReactJS and React Native also takes different approaches to navigation. React Native uses a library called Navigator. This is React Native’s alternative to react-router.</p><p>Another difference is debugging. React Native is a bit tougher because you have to use simulators to fix bugs while ReactJS has more debugging tools to work with.</p><h4>Conclusion</h4><p>Bottom line, while there are differences between the two, its hard to really compare one over the other because they are in different domains. React is ideal for dynamic, responsive UI for web interfaces, while React Native is meant for creating a more native experience for mobile phones.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1ea8c83b7d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Artificial Intelligence, Machine Learning and Deep Learning?]]></title>
            <link>https://medium.com/@eelan.tung/what-is-artificial-intelligence-machine-learning-and-deep-learning-f9b8d79ad9f0?source=rss-f4b970806444------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9b8d79ad9f0</guid>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Eelan Tung]]></dc:creator>
            <pubDate>Thu, 14 Jun 2018 03:36:46 GMT</pubDate>
            <atom:updated>2018-06-14T03:36:46.883Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*DiQfu1PQEGrnsNXb_LKtTA.png" /><figcaption>source: <a href="http://moneyinc.com/pienso-plans-change-game-machine-learning/">link</a></figcaption></figure><p>While researching for my presentation of self-driving cars, I had to look into deep learning. Like many, I wasn’t sure what the exact differences were between artificial intelligence, machine learning, and deep learning.</p><p>In reality, <strong>artificial intelligence</strong> is a broader concept that machines are able to carry out tasks in a way to make them ‘smarter’. Artificial intelligence is often then split into two categories — applied or general. Applied artificial intelligence is usually more common. These AIs are more narrowly focused on one task or category. An example of this is face recognition on Facebook. Generalized AI, which is more uncommon, is designed to be able to handle any task. Generalized artificial intelligence advancements has led to the development of machine learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*HqTwxU-lU-IrlxfaEch0hQ.png" /><figcaption>Source: <a href="https://www.alltechbuzz.net/impact-of-ai-and-ml/">https://www.alltechbuzz.net/impact-of-ai-and-ml/</a></figcaption></figure><p><strong>Machine learning</strong> is often considered a subset of artificial intelligence that is the most current state-of-the-art. Whereas artificial intelligence (machine learning category not include) utilizes decision trees for logic, or algorithms built on rules and instructions, machine learning takes in a large set of data, learn from that data, and makes a prediction or determination about something in the world.</p><p>In other words, rather than giving the machine a specific set of instructions, the machine is trained with large amounts of data and algorithms, giving it the ability to learn how to accomplish a task.</p><p>Machine learning is closely related computational statistics, which also focuses on prediction-making through the use of computers. As a side note, machine learning is sometimes mixed together with data mining. Because machine learning makes it possible to quickly and automatically produce models to analyze bigger and more complex data, which then produces more accurate results, an organization can then better identify profitable opportunities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FIlPJcQ09eL_LTCjgnPPMQ.jpeg" /><figcaption>Source: <a href="https://cdn.nanalyze.com/uploads/2016/01/Deep-Learning-Machine-Learning-Teaser-1.jpeg">https://cdn.nanalyze.com/uploads/2016/01/Deep-Learning-Machine-Learning-Teaser-1.jpeg</a></figcaption></figure><p>Machine learning could then be narrowed down even further to <strong>deep learning</strong>. Deep learning uses machine learning methods based on learning data representations (as opposed to task specific algorithms). Otherwise, there are some differences between the two.</p><p>One example is that machine learning models get progressively better but still require guidance. Engineers still need to make adjustments whenever a machine learning algorithm returns an error or inaccurate prediction. Deep learning models, on the other hand, have algorithms that are capable of determining on their own if the predictions are accurate or not and adjust accordingly.</p><p>Another difference between machine learning and deep learning is that deep learning scales with data. Machine learning methods may plateau at a certain level of performance when more examples and training data are added to the network. Deep learning networks continue to improve as the data size increases.</p><p>Deep learning works by using a complex layered structure of algorithms called artificial neural networks (ANN). These ANNs are inspired by the neural networks of the human brain. The complexity of these ANNs are needed to deal with classifying large datasets. The more data the deep learning algorithm gets, the deep learning model will train itself every time new data is received. It will “gain more experience” and therefore can learn from its mistakes and will have a higher rate of success.</p><h4>What does it all mean and how do they compare?</h4><p>Machine learning (ML) and deep learning (DL) each have their benefits and use cases. For example, deep learning generally scales better with more data than ML. DL techniques can be more easily adapted to different domains and applications. An example of this is in speech recognition. Once an engineer can understand the underlying theory of how to apply deep learning for speech recognition, they can then apply the same deep networks to natural language processing.</p><p>Machine learning on the other hand works better on smaller data sets. Deep learning networks require extremely large datasets. Sometimes these datasets aren’t readily available or time consuming to acquire. For smaller datasets, ML algorithms often outperform deep learning.</p><p>Deep learning also generally requires high-end GPUs to work effectively. Machine learning in comparison can still work well with a decent hardware. Algorithms for machine learning are also easier to understand. Because deep learning networks are very “black box”-ish, it is harder to fully understand what goes on inside the deep learning algorithms.</p><p><strong>Conclusion</strong></p><p>While machine learning and deep learning have come a long way, as more advancements come along in the future, machine learning and deep learning can greatly affect the world we live in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9b8d79ad9f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruby on Rails: form_for, form_tag, or form_with]]></title>
            <link>https://medium.com/@eelan.tung/rails-forms-384cd22c65cc?source=rss-f4b970806444------2</link>
            <guid isPermaLink="false">https://medium.com/p/384cd22c65cc</guid>
            <category><![CDATA[rails]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Eelan Tung]]></dc:creator>
            <pubDate>Wed, 23 May 2018 02:59:39 GMT</pubDate>
            <atom:updated>2018-05-23T02:59:39.393Z</atom:updated>
            <content:encoded><![CDATA[<p>When first being introduced to Ruby on Rails, it took some time to understand the exact differences between form_for and form_tag . Then, I also found out about Rails 5.1 new form_withmethod. What’s up with all these different forms and why do we need so many of them?</p><h4>Let’s start with form_tag</h4><p>Generally, form_tag is used for basic forms that are not attached to a specific Controller#action. For example, if you want to write out a contact form or a search form for your website:</p><pre>&lt;%= form_tag(&quot;/search&quot;, :method =&gt; &quot;get&quot;) do %&gt;<br>   &lt;%= label_tag(:q, &quot;Search:&quot;) %&gt;<br>   &lt;%= text_field_tag(:q) %&gt;<br>   &lt;%= submit_tag(&quot;Search&quot;) %&gt;<br>&lt;% end %&gt;</pre><p>With form_tag, the form must be manually passed to the route where the parameters are taken in. In other words, form_tag does not know where to go until we specify where to send the user submissions.</p><h4>Secondly: form_for</h4><p>form_for is more advanced compared to form_tag. It works with grabbing values from your model and tries to find the appropriate route the form needs to take. As mentioned earlier, in comparison, form_tag needs to be told exactly which route to take and also makes no assumptions about what you are doing.</p><p>For example, if you want to create a form to the user path using the form_tag:</p><pre>&lt;%= form_tag user_path do %&gt;<br>   &lt;label&gt;First Name:&lt;/label&gt;<br>   &lt;%= text_field_tag :&#39;user[first_name]&#39; %&gt;</pre><pre>   &lt;label&gt;Last Name:&lt;/label&gt;<br>   &lt;%= text_field_tag :&#39;user[last_name]; %&gt;<br>  <br>   &lt;%= submit_tag &quot;Create User&quot; %&gt;<br>&lt;% end %&gt;</pre><p>Using the form_for method, you can simplify this:</p><pre>&lt;%= form_for @user do |f| %&gt;<br>   &lt;%= f.label :first_name %&gt;<br>   &lt;%= f.text_field :first_name %&gt;</pre><pre>   &lt;%= f.label :last_name %&gt;<br>   &lt;%= f.text_field :last_name %&gt;</pre><pre>   &lt;%= f.submit %&gt;<br>&lt;% end %&gt;</pre><p>The code looks cleaner as well as allowing you to pass a form variable to the block and is best used with model-forms. It is also beneficial to use the form_for method for any database interaction.</p><h3>Heading to the future using form_with</h3><p>If you look at the <a href="http://edgeguides.rubyonrails.org/5_1_release_notes.html">Ruby on Rails 5.1 Release Notes</a>, there is a note that form_for and form_tag are unifying into form_with.</p><p>One of the benefits of using form_with is the option to generate form tags based on either URLs or models.</p><p>Let’s take these one at a time.</p><h4>form_with using URLs</h4><p>Lets take the example earlier directing the form to the user_path using the form_tag method and use the form_with instead.</p><p>We would pass a specific <strong>URL </strong>(user_path)<strong> </strong>to submit the form:</p><pre>&lt;%= form_with url: user_path do |f| %&gt;<br>   &lt;%= f.label :first_name %&gt;<br>   &lt;%= f.text_field :first_name %&gt;</pre><pre>   &lt;%= f.label :last_name %&gt;<br>   &lt;%= f.text_field :last_name %&gt;</pre><pre>   &lt;%= f.submit %&gt;<br>&lt;% end %&gt;</pre><p>With this method, it is similar to the form_tag method where you pass the URL endpoint.</p><h4>form_with using models</h4><p>As a reminder, we used form_for when we needed to create a form for a model object. Using form_with, we can also pass a <strong>model</strong> in:</p><pre>&lt;%= form_with model: @user do |f| %&gt;<br>   &lt;%= f.label :first_name %&gt;<br>   &lt;%= f.text_field :first_name %&gt;<br>  <br>   &lt;%= f.label :last_name %&gt;<br>   &lt;%= f.text_field :last_name %&gt;<br>  <br>   &lt;%= f.submit %&gt;<br>&lt;% end %&gt;</pre><p>With passing in the model, it works similarly to form_for. It can work for both new or existing records. It also fills out the input values if the model object is not new.</p><p><em>Side Note: In Rails 5.1, you will have to specify ids manually. But with the Rails 5.2 update, form_with will automatically generate ids.</em></p><h4>Conclusion</h4><p>There will be no more times you have to worry about which form method you need to use. Whether you need form connected to your model and database or simply needing to generate a HTML form, like a search, you can do everything with form_with.</p><p>There are other extra options to work with using form_with, so it will be nice to familiarize oneself with the new form method.</p><p><a href="http://api.rubyonrails.orb/classes/ActionView/Helpers/FormHelper.html#method-i-form_with">form_with documentation</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=384cd22c65cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being #lazy in Ruby]]></title>
            <link>https://medium.com/@eelan.tung/being-lazy-in-ruby-109ec10e81ed?source=rss-f4b970806444------2</link>
            <guid isPermaLink="false">https://medium.com/p/109ec10e81ed</guid>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Eelan Tung]]></dc:creator>
            <pubDate>Tue, 08 May 2018 01:54:07 GMT</pubDate>
            <atom:updated>2018-05-08T01:54:07.383Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/346/1*HTGOAz_wGXHhT2kbS6VocA.gif" /><figcaption>Source: <a href="https://giphy.com/gifs/lazy-I8DYoEE1Y1O2A">https://giphy.com/gifs/lazy-I8DYoEE1Y1O2A</a></figcaption></figure><p>I was looking at something interesting to write about when I found the <strong>Enumerable#lazy</strong> method purely by accident. It struck my interest in why a method was even called lazy. Is there really a method in Ruby to tell us to slack off?</p><h3><strong>So what does #lazy actually do?</strong></h3><p>Simply put, <strong>#lazy</strong> changes the way Ruby evaluates iterators.</p><p>It will be easier to explain through a simple example. If I’m iterating through a range like this:</p><pre>(1...5).map { |x|<br>              puts &quot;hi, i&#39;m #{x}&quot;<br>                x<br>            }.<br>              select{|x|<br>                puts &quot;filtering #{x} on evenness&quot;<br>                x % 2 == 0<br>            }.<br>              each{ |x|<br>                puts &quot;in each: #{x}&quot;<br>            }</pre><p>As you can probably guess, this code will print:</p><pre>here is 1<br>here is 2<br>here is 3<br>here is 4<br>here is 5<br>filtering 1 on evenness<br>filtering 2 on evenness<br>filtering 3 on evenness<br>filtering 4 on evenness<br>filtering 5 on evenness<br>in each: 2<br>in each: 4</pre><p>But, when using <strong>#lazy</strong>, the iterators will work as a stream, where one number will go through all three blocks before the next number is passed in.</p><p>If we look at the same example, but using the <strong>#lazy</strong> method:</p><pre>(1...5).lazy.map { |x|<br>              puts &quot;hi, i&#39;m #{x}&quot;<br>                x<br>        }.<br>            select{|x|<br>              puts &quot;filtering #{x} on evenness&quot;<br>              x % 2 == 0<br>        }.<br>            each{ |x|<br>            puts &quot;in each: #{x}&quot;<br>        }</pre><p>Will output:</p><pre>here is 1<br>filtering 1 on evenness<br>here is 2<br>filtering 2 on evenness<br>in each: 2<br>here is 3<br>filtering 3 on evenness<br>here is 4<br>filtering 4 on evenness<br>in each: 4<br>here is 5<br>filtering 5 on evenness</pre><p>In a small range like in this example, it will not make much of a difference performance-wise, but using <strong>#lazy</strong> on bigger collections, it can make it more efficient.</p><p>A simple example of this would be on a range from 1 to infinity:</p><pre>range = 1..Float::INFINITY<br>p range.lazy.collect {|x| x*x}.first(10)<br>=&gt; [1, 4, 9, 16, 25, 36, 49, 64, 81, 100]</pre><p>Using <strong>#lazy</strong> on this method would stop after the first 10 numbers in the range, whereas using <strong>#collect</strong> without the <strong>#lazy</strong> method would go into an endless loop.</p><p>You can imagine this is quite useful when you have to iterate through a large collection of data but only want a certain number of results.</p><blockquote>Note: While it doesn’t work for all Enumerable methods, you can still use it for quite a few, including map/collect, select, take, each, reject, grep and zip.</blockquote><p>In conclusion, there’s quite a bit that goes into the <strong>Enumerable#lazy</strong> method under the hood, but the usefulness of the method could be quite interesting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=109ec10e81ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>