<?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 Akshay Gohil on Medium]]></title>
        <description><![CDATA[Stories by Akshay Gohil on Medium]]></description>
        <link>https://medium.com/@akshaygohil?source=rss-39f38e7124------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*52R5QBl63LtVZL1e_lBa1A.jpeg</url>
            <title>Stories by Akshay Gohil on Medium</title>
            <link>https://medium.com/@akshaygohil?source=rss-39f38e7124------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:39:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@akshaygohil/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[Addition by subtraction]]></title>
            <link>https://medium.com/@akshaygohil/addition-by-subtraction-b4c30fca8c14?source=rss-39f38e7124------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4c30fca8c14</guid>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Akshay Gohil]]></dc:creator>
            <pubDate>Wed, 22 Jun 2022 15:27:16 GMT</pubDate>
            <atom:updated>2022-06-22T15:27:16.349Z</atom:updated>
            <content:encoded><![CDATA[<p>Do more by doing less…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mEHUROmF2WuUTe6bcMI5eg.jpeg" /><figcaption>(Photo by <a href="https://unsplash.com/@isaacmsmith">Isaac Smith</a> on <a href="https://unsplash.com/photos/6EnTPvPPL6I">Unsplash</a>)</figcaption></figure><p>You might have observed that sometimes when someone is asked to improve the productivity of one person or a group of people, they start adding more people, or adding more goals. Many times, this results in a drop in productivity rather than improving it. You might have met people who take pride in saying, “<em>I’m able to multitask</em>”. Honestly, it’s not the truth.</p><p>Multi-tasking is a myth. The human brain cannot perform two tasks that require high-level brain function simultaneously. (This also reminds me of a great talk by <a href="https://vimeo.com/49718712">Rob Pike — Concurrency is not parallelism</a>). We might be able to do something concurrently, but we do a very poor job at doing things in parallel.</p><p>Subtract obstacles, mastering your environment improves the overall productivity. Companies redesign workspaces to reduce any friction in communication. Organisations have started spending their energies on becoming “<strong>lean</strong>” for this exact reason.</p><p>More often, by adding more things, we introduce additional complexity and, as a result, instead of improving productivity, this results in a worse situation. You can find such examples in your organisation or in your life, where a small team with a clear set of instructions are outperforming a larger team with many goals defined for them.</p><blockquote>“As you subtract, you add.”</blockquote><p>To find such results, you need to ask yourself:</p><ul><li>How can you simplify the journey, which results in fewer clicks for the user?</li><li>Do you need to make your team smaller to have better focussed output?</li><li>What can be subtracted from existing processes to improve speed?</li><li>How can you remove clutter from the environment to achieve better productivity?</li></ul><p>Thank you for reading. If you like it show some love by hitting that clap icon.</p><p>You can connect with me on Twitter: <a href="https://twitter.com/aks_gohil">@aks_gohil</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4c30fca8c14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Progressive overloading what?!]]></title>
            <link>https://medium.com/@akshaygohil/progressive-overloading-what-3013b208c3b2?source=rss-39f38e7124------2</link>
            <guid isPermaLink="false">https://medium.com/p/3013b208c3b2</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Akshay Gohil]]></dc:creator>
            <pubDate>Mon, 29 Jul 2019 07:23:12 GMT</pubDate>
            <atom:updated>2019-07-29T07:23:12.129Z</atom:updated>
            <content:encoded><![CDATA[<h4>The single most important thing that you need to succeed in your life.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PW1h_JLREiJFb7zh" /><figcaption>Photo by <a href="https://unsplash.com/@huchenme?utm_source=medium&amp;utm_medium=referral">Hu Chen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you haven’t heard this term before, you have been missing out a lot. Trust me.</p><p>It is the one of the key factors for any kind of success. This term “Progressive Overload” is widely used in Exercising but I think it shouldn’t be limited to exercises.</p><h3>So what the heck is this Progressive Overloading?</h3><p>In order for you to grow, success to be achieved, muscle to grow, or improve in any other field, you need to be forced to adapt to a new level, then what you’ve been previously at.</p><p>Have you played any video game? It is pretty similar to playing a video game.</p><p>When you start playing a new game the first level will be easy but as you cross that level you are faced with more and more difficulties. As you cross these levels one by one you are being “progressively overloaded” to achieve the ABILITY to move ahead in the game.</p><blockquote>“You learn something valuable from all of the significant events and people, but you never touch your true potential until you challenge yourself to go beyond imposed limitations.” — Roy T. Bennette</blockquote><p>Let’s say you are a fresher just out of college, you get your first job, the first few months will be easy everyone’s guiding you but as you move forward you will be given more responsibilities. In this case these additional responsibilities act as the necessary challenge or to say progressive overload that will help you improve in your career.</p><p>The key thing to note here is that you need to <em>keep challenging yourself</em>.</p><p>If you can do ‘Task A’ in 1 hour, ask yourself if you can do it in 50 minutes? It doesn’t matter if you couldn’t do it let’s say you did it in 55 minutes. That’s improvement!</p><p>You are better than you were before.</p><h3><strong>Why do you need it?</strong></h3><p>It doesn’t matter who you are you need this. Everyone wants to be better version of themselves. Progressive Overloading is here to help you achieve that. You’ll see many people who are more advanced than you are. But your race is with yourself not with anyone else.</p><p>You can certainly look up to people for inspiration but <em>never</em> compare yourself with others.</p><p>Thank you for reading. If you like it show some love by hitting that clap icon.</p><p>You can connect with me on Twitter: <a href="https://twitter.com/aks_gohil">@aks_gohil</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3013b208c3b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Caching]]></title>
            <link>https://medium.com/@akshaygohil/introduction-to-caching-33ca834eaacc?source=rss-39f38e7124------2</link>
            <guid isPermaLink="false">https://medium.com/p/33ca834eaacc</guid>
            <category><![CDATA[redis]]></category>
            <category><![CDATA[memcached]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Akshay Gohil]]></dc:creator>
            <pubDate>Fri, 17 May 2019 06:05:43 GMT</pubDate>
            <atom:updated>2019-05-17T06:05:43.932Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“What is considered slow depends on your requirements. But when something becomes slow it’s a candidate for <strong>caching</strong>.”</blockquote><h4>What is cache?</h4><p><em>“Cache</em>” is a hardware or software component that stores data so that future requests for that data can be served faster; the data stored in a cache might be the result of an earlier computation or a copy of data stored elsewhere.</p><p>There are two scenarios while accessing data from cache:</p><ol><li><strong><em>Cache Hit</em></strong>: This occurs when the requested data can be found in a cache. (Shown in green in Diagram 1)</li><li><strong><em>Cache Miss</em></strong>: When the requested data cannot be found in a cache. (Shown in red in Diagram 1)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*eNaoeQKSoyXtbKi74OAGiQ.jpeg" /><figcaption>Diagram 1: Caching Hit &amp; Miss</figcaption></figure><ul><li>A small amount of faster, more expensive memory is used to improve the performance of recently accessed or frequently accessed data that is stored temporarily in a rapidly accessible storage media that’s local to the cache client.</li><li>Cache shortens data access times, reduces latency and improves input/output.</li><li>Because almost all application workloads depend on I/O operations, caching improves application performance.</li></ul><h4>Cache Algorithms</h4><ul><li><strong><em>Least Frequently Used (LFU)</em></strong> keeps track of how often an entry is accessed. The item that has the lowest count gets removed first.</li><li><strong><em>Least Recently Used (LRU)</em></strong> puts recently accessed items near the top of the cache. When the cache reaches its limit, the least recently accessed items are removed.</li><li><strong><em>Most Recently Used (MRU)</em></strong> removes the most recently accessed items first. This approach is best when older items are more likely to be used.</li></ul><h4>Cache Policies</h4><p><strong><em>Write-around</em></strong>:</p><ol><li>Write-around cache writes operations to storage, skipping the cache altogether.</li><li>This prevents the cache from being flooded when there are large amounts of write I/O.</li><li>The disadvantage to this approach is that data isn’t cached unless it’s read from storage.</li><li>That means the read operation will be relatively slow because the data hasn’t been cached.</li></ol><p><strong><em>Write-through</em></strong>:</p><ol><li>Write-through cache writes data to cache and storage.</li><li>The advantage here is that because newly written data is always cached, it can be read quickly.</li><li>A drawback is that write operations aren’t considered complete until the data is written to both the cache and primary storage.</li><li>This can cause write-through caching to introduce latency into write operations.</li></ol><p><strong><em>Write-back</em></strong>:</p><ol><li>Write-back cache is similar to write-through caching in that all the write operations are directed to the cache.</li><li>However, with write-back cache, the write operation is considered complete after the data is cached.</li><li>Later on, the data is copied from the cache to storage.</li><li>With this approach, both read and write operations have low latency.</li><li>The downside is that, depending on what caching mechanism is used, the data remains vulnerable to loss until it’s committed to storage.</li></ol><p>The choice of cache policy will be based on your use-case and preference. Each cache policy comes with its pros and cons as listed above, however it will be good to use write-through as this policy favours that data be written in both cache and storage, hence the updated data is available in cache for read.</p><h4>Cache Options Available</h4><ol><li><a href="https://redis.io/">Redis</a></li><li><a href="https://memcached.org/">Memcached</a></li></ol><p>There are other options also available such as <a href="https://varnish-cache.org/">Varnish</a>, <a href="http://www.alachisoft.com/ncache/">Ncache</a> but these are not as widely used as the former two.</p><p>We can check the google trends for all four <a href="https://g.co/trends/1FVMs">here</a>.</p><p>Let’s take a quick look at these two in the following comparison:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dFsZpD9x9x0j6UDGd1kMrA.png" /><figcaption>(Diagram 2. Memcached &amp; Redis Comparison)</figcaption></figure><h4>Okay! When to use cache?</h4><p>Caching is great to improve performance of application but caching should be done <em>to decrease costs needed to increase performance and scalability</em> and NOT <em>to solve performance and scalability problems</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*noKTD7n4GIUQZXqC3ATPDA.gif" /><figcaption>(Source: <a href="https://media.giphy.com/media/MCZ39lz83o5lC/giphy.gif">https://media.giphy.com/media/MCZ39lz83o5lC/giphy.gif</a>)</figcaption></figure><p>Every superpower comes with a responsibility, a lot of times developers try to hide performance and scalability problems with caching.</p><p>API response is slow? let’s cache the response. Database queries are slow? Cache the results in middle-tier or a specialised micro-service.</p><p>The major flaw in this is that, sooner or later performance and scalability becomes a problem again.</p><p>Caching also comes with an overhead of maintaining correct data in cache, we need to make sure that the data in cache is updated whenever it is updated at the source. It is also important to figure out how and when the cached data will be invalidated.</p><p>Caching is great and will definitely improve performance of your application but, only if it is used well. Note that you will also have to add logic to handle scenarios when what you are looking for is not in cache, as by nature cache is volatile.</p><h4>Conclusion</h4><ul><li>Caching may not be always needed but if you need your application to scalable (which you want in most of the cases) you should use caching.</li><li>Caching also helps in extracting your application state out of the application server (viz. You can maintain user login session in caching layer, so that you can increase number of application servers and have the session available on all of them.)</li></ul><p>Thank you for reading, this is my first post. If you like it show some love.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33ca834eaacc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>