<?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 Rahul Lohakare on Medium]]></title>
        <description><![CDATA[Stories by Rahul Lohakare on Medium]]></description>
        <link>https://medium.com/@rahullohakare20?source=rss-28c4c5c99913------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qUW5nVfLdBHScqbQA4ggkA.jpeg</url>
            <title>Stories by Rahul Lohakare on Medium</title>
            <link>https://medium.com/@rahullohakare20?source=rss-28c4c5c99913------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:47:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rahullohakare20/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[Functional programming: Declarative vs Imperative programming]]></title>
            <link>https://rahullohakare20.medium.com/functional-programming-declarative-vs-imperative-programming-5332976d55fc?source=rss-28c4c5c99913------2</link>
            <guid isPermaLink="false">https://medium.com/p/5332976d55fc</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[imperative]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[declarative-programming]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Rahul Lohakare]]></dc:creator>
            <pubDate>Sun, 22 May 2022 12:48:27 GMT</pubDate>
            <atom:updated>2022-05-22T12:48:27.670Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*of56R7oc8TH92WijmgXiMQ.png" /><figcaption>Declarative vs Imperative programming</figcaption></figure><p><strong>How to do it? vs What to do?</strong></p><p><strong>In Imperative programming,</strong> we have to tell all the steps of the program one by one to the computer.</p><p>The person reading the code will have to read the code line by line and understand the steps performed for a particular action.</p><p>In short, we have to mention all the steps to the computer, Like the computer is asking us the question “<strong>How to do it</strong>?” and we as a programmers provide all the steps as an answer to the computer.</p><p><strong>In declarative programming,</strong> We don’t have to mention the steps every time. We as a programmer only have to tell the computer what task it has to work on and it will use all abstract logic written earlier to perform the task.</p><p>So in short, Assume that the computer is asking you <strong>“What to do ?” </strong>instead of How to do? and we as programmers will provide the task to do and not the steps to do that task</p><p><strong>Write Declarative code!</strong></p><p>If we want to have our codebase built with declarative code, we must follow a few things to make it declarative.</p><p>1. Try to break your function into small functions, such that each function should have single responsibility only.</p><p>2. While writing a function keep in mind that you must write a function that should be common and generic so that it will be reused in multiple places in the codebase.</p><p>3. Keep the function names declarative, Function name itself should mention what action it will perform.</p><p><strong>Analogy</strong></p><p>Imagine, you have two robots in your house and the names of the robots are Mr. Imperative vs Mr. Declarative.</p><p>Now you want them to make a coffee for you.</p><p>You called Mr. Imperative and said, “make a cup of coffee for me”.</p><p>Mr. Imperative: “How to do it?”</p><p>You: “get some coffee powder”</p><p>You: “get some water”</p><p>You: “add some sugar”</p><p>You: “Add some cream or milk”</p><p>You: “heat it for some time”</p><p>You: “Serve it to me”</p><p>Huff…. lot of work, right?</p><p>Imagine, the next day you want a coffee again, and these steps you have to mention again.</p><p>Now this time let’s call <strong>Mr. Declarative</strong></p><p>You: “Hello Mr. declarative”</p><p>Mr. Declarative: “Hello Sir, what should I do for you today?”</p><p>You: “Get me a cup of coffee”</p><p>After some time.</p><p>Mr. Declarative: “Here is your coffee sir”</p><p>Pretty cool right? No worries about having to tell him all the steps every time.</p><p>There are some best examples of declarative things in programming that you might be using daily</p><p>HTML tags: Have you ever had to think how &lt;p&gt;, &lt;div&gt;, &lt;span&gt;, &lt;ul&gt; works internally or have to write code for it?</p><p>You are freely using it for years just by trusting its functionality and you already know how to and when to use these tags.</p><p>That is an abstraction, which means hiding the implementation details and knowing the usage only.</p><p><strong>Is it possible to avoid imperative code completely?</strong></p><p>Let’s understand this, you have written declarative functions all over but now pick any single function in it. You must have written step-by-step instructions (code) inside that declarative function.</p><p>That means you have used imperative code to create a declarative function. Just the difference here is that you have written declarative function in such a way that it will be reusable in multiple places in the codebase.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5332976d55fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Functional programming : Avoid Mutations]]></title>
            <link>https://rahullohakare20.medium.com/functional-programming-avoid-mutations-5bc06bfb5414?source=rss-28c4c5c99913------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bc06bfb5414</guid>
            <category><![CDATA[immutability]]></category>
            <category><![CDATA[mutation]]></category>
            <category><![CDATA[js]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[functional-programming]]></category>
            <dc:creator><![CDATA[Rahul Lohakare]]></dc:creator>
            <pubDate>Sat, 19 Feb 2022 08:22:04 GMT</pubDate>
            <atom:updated>2022-02-19T08:22:04.156Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Functional programming : Avoid Mutations</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oCmHdNhjesYGtMAW" /><figcaption>Photo by <a href="https://unsplash.com/@diana_pole?utm_source=medium&amp;utm_medium=referral">Diana Polekhina</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>The Mutation. </strong>Are you the one who heard this word only in the X-men movie? Well, If yes don’t worry, I was once too.</p><p>In my coding career, I have experienced so many coding scenarios and problems that can be solved by “Avoiding mutations”.</p><h3><strong>What is mutation ?</strong></h3><blockquote><em>A change in the form or structure of something </em>–Oxford Advanced American Dictionary</blockquote><h3><strong>A real life example (Analogy)</strong></h3><p>World’s current biggest problem is COVID-19 pandemic. We all know that science and technology has grown so much that we can easily get rid of any dangerous virus. Then why scientists and researchers are failing to find medicine over COVID-19 ?</p><p>Reason is Mutation.</p><p>You know every virus has a specific structure, Our immune system that fights with it and remembers the structure of the virus. Next time if the same virus enters into our body, the response time for killing the virus will be very less.</p><p>In case of covid, it changes its own structure over time to be able to survive.</p><p>Now, the vaccines or medicines which were effective on the last form of covid will not be very much effective on this mutated form.</p><p>I wish COVID-19 could have been Immutable.</p><h3><strong>Mutable and Immutable</strong></h3><p><em>Mutable</em> is a type of variable that can be changed and which can’t be changed directly is known as Immutable.</p><p>In JavaScrip<a href="https://developer.mozilla.org/en-US/docs/Glossary/JavaScript">t</a>, only <strong>objects and arrays</strong> are mutable, rest of the data types are immutable. Like <strong>Strings and Numbers</strong> are <strong>Immutable</strong>.</p><p>Let’s see an example.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/78a91d2a1d6d9e8249dd606edde68036/href">https://medium.com/media/78a91d2a1d6d9e8249dd606edde68036/href</a></iframe><p>Here, the <strong>salaryStructure </strong>has property ‘basicSalary’ which has been changed accidently due to mutation in <strong>processUserOneSalary </strong>function and due to that <strong>processUserTwoSalary </strong>function received changed value.</p><p>Let’s see how memory allocation works in case of mutation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7_II4CSOBUM6f37j429Hg.jpeg" /><figcaption>Memory allocation in case of Mutation</figcaption></figure><p>All 3 variables are pointing to the same memory location and hence, if property of any one variable gets changed then all others will receive updated value.</p><p>Before fixing our example. Let’s see how to deep copy an object or array.</p><pre><strong>JSON.parse(JSON.stringify(object));</strong></pre><p>Now let’s fix the mutation problem.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e58e32c948ab073b0f11c180f09926ad/href">https://medium.com/media/e58e32c948ab073b0f11c180f09926ad/href</a></iframe><p>Here, we have used <strong>clone </strong>function which deeply copies object and then we’ve performed property value change on cloned object. This is immutability.</p><p>Let’s see memory allocation in case of Immutability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kvc1TjmzPLwvCMPMA3xYPQ.jpeg" /><figcaption>Deep copy of a object, Immutability</figcaption></figure><p>Modern JavaScript also lean towards immutability. Examples of it are functions like map, reduce and filter.</p><p>Immutability is debatable topic among developers. Few developers have opinion that Immutability comes with high memory wastage. On the other hand Immutability prevent bugs and obviously saves productive time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bc06bfb5414" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Functional programming : Avoid Shared state]]></title>
            <link>https://rahullohakare20.medium.com/functional-programming-avoid-shared-state-65c2730a3497?source=rss-28c4c5c99913------2</link>
            <guid isPermaLink="false">https://medium.com/p/65c2730a3497</guid>
            <category><![CDATA[manage-state-in-react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[immutability]]></category>
            <category><![CDATA[shared-state]]></category>
            <dc:creator><![CDATA[Rahul Lohakare]]></dc:creator>
            <pubDate>Sat, 19 Feb 2022 07:46:30 GMT</pubDate>
            <atom:updated>2022-02-19T07:46:30.128Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Functional programming : Avoid Shared state</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/0*eXeau6k7czZodb69.jpg" /><figcaption>Sharing is not always bad though…</figcaption></figure><h3><strong>What is a shared state?</strong></h3><p>Shared state is a variable, object, property of an object or memory space that can be accessed from more than one function.</p><h3><strong>What’s the problem with shared state ?</strong></h3><p>Accidentally changing the value of a variable which is shared in the entire code base may lead to potential and complex bugs. Such bugs are hard to debug and solve.</p><p>See the below example</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/73687bb2c3e57bb2367f2f81ef198816/href">https://medium.com/media/73687bb2c3e57bb2367f2f81ef198816/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZsNPYFnh2wgb-ZoxK-Wd6A.png" /><figcaption>Accidental shared state update</figcaption></figure><h3><strong>Yes It’s easy but it’s costly</strong></h3><p>I know it is easy to write a shared state and read/write it from anywhere in the app.</p><p>For very small things it is ok but, imagine having 1000 files and functions having a shared state and no idea which file or function is changing the state, intentionally or accidentally. In this case If the code base increases bugs due to shared state increases.</p><h3><strong>Mutable shared state and Immutable shared state</strong></h3><p>For an shared Immutable state it is harmless as nobody will be able to directly change it. Example of it is React state management.</p><p>For a mutable shared state, we have to keep track of the history or changes done on it. Also a locking mechanism will also be needed. Which is expensive.</p><p>Even if the sequence of calling functions got changed, output will change.</p><h3>How to fix problem of mutable shared state ?</h3><p>Avoid shared state and while writing code, write logic such that there will be no shared state. Still needed a shared state ?</p><p>Use any one of the below methods</p><p>A) Copy while using it.</p><p>B) Copy at the source.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/32e1f6d63e59b7eb4353d9ae63ce46a3/href">https://medium.com/media/32e1f6d63e59b7eb4353d9ae63ce46a3/href</a></iframe><h3><strong>Prevent accidental changes and not intentional</strong></h3><p>The primary focus of “Avoiding shared state” is to prevent accidental updates of mutable variables. But, you might be thinking, what if we actually need to change the value of a mutable variable? Like if we have a configuration variable or property in a window object that has an effect on the entire app.</p><p>Sure, We can change it intentionally. But the recommended way for it is having a function (setter). Benefits of having a setter function is you can log or track the direct changes to mutable state variables.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4248eac4825236cb60787b85bd79b69/href">https://medium.com/media/a4248eac4825236cb60787b85bd79b69/href</a></iframe><h3><strong>State in react</strong></h3><p>Many of you are might be confused like me. That we normally use state in react. That is something shared too, then why react allowed shared state.</p><p>The reason is react never allows shared state. The state which we use in react is an Immutable state by its own way. You cannot directly change state in react. To change any state you have to call setState function or use callback function in case of hook. That is where react added Immutability. Those functions internally never change the value of state directly.</p><p>Congratulations ! you’ve just learnt a new concept of functional programming.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65c2730a3497" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Functional programming : Avoid Side Effects]]></title>
            <link>https://rahullohakare20.medium.com/functional-programming-avoid-side-effects-b76800c4c7a4?source=rss-28c4c5c99913------2</link>
            <guid isPermaLink="false">https://medium.com/p/b76800c4c7a4</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[avoid-side-effects]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[functional-programming]]></category>
            <dc:creator><![CDATA[Rahul Lohakare]]></dc:creator>
            <pubDate>Sun, 09 Jan 2022 09:09:05 GMT</pubDate>
            <atom:updated>2022-01-09T15:27:29.446Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7IDAGFLTRdOmoD8NA10ApA.png" /></figure><h3><strong>Functional programming : Avoid Side Effects</strong></h3><p>One of the most important guidelines for Functional Programming is “<strong>avoid the side effects</strong>”.</p><h3><strong>What are ‘Side effects’?</strong></h3><blockquote><em>“An unexpected result of a situation or course of action that happens as well as the result you were aiming for”</em></blockquote><p>— Oxford Advanced American Dictionary</p><h3><strong>A real life example (Analogy)</strong></h3><p>Suppose a person named John has a beautiful house and good neighbors.</p><p>One day John found that there is no water supply to his house while neighbors have proper water supply.</p><p>He calls a plumber to fix the water supply issue for his house. The plumber visits his house and fixes the issue. Very next day John’s neighbors complain that they have had no water supply since yesterday. It turns out that, plumber fixed the problem for John but at the same time he messed up with the neighbor’s water supply.</p><p>This is a clear case of side effects. Right ?</p><blockquote><strong>Side effect </strong>is when a function uses and modifies the value which is outside of it.</blockquote><h3><strong>Things that are considered as side effects in programming world</strong></h3><ul><li>Changing a value globally (variable, property or data structure)</li><li>Changing the original value of a function’s argument.</li><li>Throwing an exception.</li><li>Printing to the Screen or Logging.</li><li>Triggering an external process.</li><li>Invoking other functions that have side-effects.</li></ul><p>Let’s see one example.</p><pre><strong>let count = 0;</strong></pre><pre><strong>function increment() {</strong><br><strong> count++;<br> return count;<br>}</strong></pre><pre><strong>function getInitialValue() {<br> return count;<br>}</strong></pre><pre><strong>increment();</strong><br><strong>getInitialValue();</strong> // Here expected count value should be 0 but, instead it is 1.</pre><p>Here, as you can see count is a global variable and increment is changing its value even if it is not inside increment, resulting in a manipulated value of count is accessed by getInitialValue. That’s a side effect.</p><h3><strong>How to avoid side effects ?</strong></h3><ul><li>Write your function in such a way that it should accept values only from arguments passed to it and there should not be any direct access to variables outside of it.</li><li>Return the result value.</li></ul><p>Above two are part of Pure function.</p><p><strong>Let’s see how it works</strong></p><pre><strong>let count = 0;</strong></pre><pre><strong>function increment(num) {<br> return num + 1;<br>}</strong></pre><pre><strong>function getInitialValue() {<br> return count;<br>}</strong></pre><pre><strong>const incrementedCount = increment(count);</strong>  // 1<br><strong>getInitialValue(); </strong>// 0 as there is no side effect now.</pre><h3><strong>What’s the benefit ?</strong></h3><p>By writing side effects free code we can save complex, potential bugs and can save a lot of debugging time. And ofcourse who doesn’t want to save productive time.</p><p><strong><em>If you find this post helpful, please click the clap 👏 button as much as you want to motivate me to share more knowledge with you!</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b76800c4c7a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Javascript : Dot (.) notation vs Bracket [] notation]]></title>
            <link>https://rahullohakare20.medium.com/javascript-dot-notation-vs-bracket-notation-37bcf780c5e3?source=rss-28c4c5c99913------2</link>
            <guid isPermaLink="false">https://medium.com/p/37bcf780c5e3</guid>
            <category><![CDATA[objects-in-javascript]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[es6]]></category>
            <dc:creator><![CDATA[Rahul Lohakare]]></dc:creator>
            <pubDate>Sat, 03 Apr 2021 07:32:30 GMT</pubDate>
            <atom:updated>2021-04-03T07:49:45.413Z</atom:updated>
            <content:encoded><![CDATA[<h3>Javascript : Dot (.) notation vs Bracket [ ] notation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vEoUxySU852TvOfg7ATMyg.png" /><figcaption>Dot Vs Bracket</figcaption></figure><p>For most of the developers, Dot (.) or Bracket [] does not matter. <br>They randomly use any one of these and once they ran into a strange problem they start to believe that <em>“Javascript is such a mess”</em>.</p><p>Believe me, Javascript is not the mess but yes it&#39;s a different and unique programming language.</p><h4><strong>Why we need Dot (.) or Bracket [ ] in Javascript?</strong></h4><p>Javascript has few non-primitive data types including array and object.<br>When we want to access an element of an array or object, We use Dot (.) or Bracket [ ] notation.</p><pre><strong>const language = {<br>    name: &#39;Javascript&#39; <br>}</strong></pre><pre>// Dot (.) notation<br><strong>console.log(language.name);</strong> // Javascript</pre><pre>// Bracket [] notation<br><strong>console.log(language[&#39;name&#39;]);</strong> // Javascript</pre><h4><strong>Limitations of dot (.) notation.</strong></h4><p>I still remember my javascript learning days when I was simply using dot notation every time to access a property of an object.<br>Then I encountered few issues with dot notation. Let me tell you all those problems one by one.</p><p><strong>Problem 1.</strong> <strong>Numeric key of an object</strong><br>Here we have an object with a numeric key.</p><pre><strong>const language = {<br> 1: ‘Number one’<br>}</strong></pre><pre>// Lets try to access it with dot (.) notation<br><strong>console.log(language.1);</strong> //JavaScript error: Uncaught SyntaxError: Unexpected number</pre><pre>// Lets try to access it with dot (.) notation and quotes (‘)<br><strong>console.log(language.’1&#39;);</strong> // JavaScript error: Uncaught SyntaxError: Unexpected string</pre><p>Here, bracket comes into the picture<br>Let&#39;s try it with the bracket notation.</p><blockquote>“Numeric value means bracket”</blockquote><pre><strong>const language = {<br>    1: &#39;Number one&#39; <br>}</strong></pre><pre>// Lets try to access it with bracket [] notation<br><strong>console.log(language[1]); </strong>// Number one</pre><pre>// Also with quotes (&#39;&#39;)<br><strong>console.log(language[&#39;1&#39;]);</strong> // Number one</pre><p><strong>Problem 2. Use of variable value as a key.</strong></p><p>In some cases, we want to access object keys dynamically with a variable.</p><pre><strong>const type = &#39;web development&#39;;</strong></pre><pre><strong>const language = {<br>    &#39;web development&#39; : &#39;Javascript&#39;  <br>}</strong></pre><pre>// Lets try to access it with dot notation and variable name<br><strong>console.log(language.type);</strong> // undefined</pre><p><strong><em>Why undefined here?</em></strong></p><p>The dot never evaluates any expression. So, if we use the variable name it will try to evaluate it as a string. <br>If we use a variable with the name ‘type’ then it checks for a record with the key name ‘type’.<br>As it is not there in an object it is undefined</p><pre><strong>language.type =&gt; searching for key name &#39;type&#39; =&gt; not found =&gt; undefined </strong></pre><p>Here also bracket [ ] solves the problem.</p><pre><strong>const type = &#39;web development&#39;;</strong></pre><pre><strong>const language = {<br>    &#39;web development&#39; : &#39;Javascript&#39;  <br>}</strong></pre><pre>// Lets try to access it with bracket notation and variable name<br><strong>console.log(language[type]); </strong>// Javascript</pre><p><strong>How did it work?</strong></p><p>bracket evaluates the variable passed to it and then searches for the key in the object.</p><pre><strong>language[type] =&gt; language[‘web development’] =&gt; ‘Javascript’</strong></pre><h4><strong>When to use what?</strong></h4><p><strong>Thumb rule:</strong> According to the Airbnb style guide. One should always use Dot(.) notation to access object properties.<br>But keep the above scenarios in mind. Whenever you see variable and numeric keys use bracket [ ] notation.</p><h4><strong>What about arrays?</strong></h4><p>In Javascript, we don’t have associative arrays ( Array having alphanumeric keys ). So by default, we have numeric keys for an array.<br>Just like objects here also our thumb rule works.</p><blockquote>“Numeric value means bracket”.</blockquote><pre><strong>const language = [&#39;ruby&#39;, &#39;js&#39;, &#39;java&#39;, &#39;c#&#39;];</strong></pre><pre><strong>console.log(language.1);</strong> // JavaScript error: Uncaught SyntaxError</pre><pre><strong>console.log(language[1]);</strong> // js<br><strong>console.log(language[&#39;1&#39;]);</strong> // js</pre><h4><strong>Conclusion:</strong></h4><p>You can always use dot (.) notation but once you see variables and numeric keys, go for bracket notation to retrieve value from the object.</p><p><strong><em>If you find this post helpful, please click the clap 👏 button as much as you want to motivate me to share more knowledge with you!</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37bcf780c5e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>