<?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 Goutham Pilla on Medium]]></title>
        <description><![CDATA[Stories by Goutham Pilla on Medium]]></description>
        <link>https://medium.com/@gouthampilla?source=rss-acc0bb64188d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rF9DRgZYS8hXtWR9.</url>
            <title>Stories by Goutham Pilla on Medium</title>
            <link>https://medium.com/@gouthampilla?source=rss-acc0bb64188d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:15:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gouthampilla/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[2 Claude Code Features I Use Every Day]]></title>
            <link>https://gouthampilla.medium.com/2-claude-code-features-i-use-every-day-cdee7e052279?source=rss-acc0bb64188d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdee7e052279</guid>
            <category><![CDATA[claude-code]]></category>
            <dc:creator><![CDATA[Goutham Pilla]]></dc:creator>
            <pubDate>Sun, 01 Nov 2026 18:10:36 GMT</pubDate>
            <atom:updated>2026-11-01T18:10:36.093Z</atom:updated>
            <content:encoded><![CDATA[<p>I use Claude Code (CC) in the desktop app. I use it to plan, review and write code. I spend most of my time reviewing plans and asking questions.<strong></strong></p><p><strong>I have two problems again and again:</strong></p><ol><li>I have many small questions while reviewing, but I don’t want them in the main conversation.</li><li>When a conversation becomes valuable, I want to start more than one branch from it.</li></ol><p>To solve these problems, I use side chat and fork.</p><h3>Side Chat (/btw in the terminal)</h3><p>When I review a CC response, I often have a quick question that I don’t want to add to the main conversation.</p><p>Before AI agents, I did a quick Google search, read the answer and went back to my main task. Side chat does the same job inside CC.</p><p>In the terminal, use /btw to ask a <a href="https://code.claude.com/docs/en/interactive-mode#side-questions-with-%2Fbtw">side question</a>. The question doesn’t go into the conversation. For example: /btw what was the name of that config file again?</p><p>In the desktop app, I select the text and click “Start a side chat”. CC opens a side pane.</p><figure><img alt="Screenshot 2026-11-01 at 22.33.42.png" src="https://cdn-images-1.medium.com/max/1024/dfe67545b86b80fbd1f5586dab604cc75e7e5f8b620805c7418b475e6592ee0b" /><figcaption>Select the text and click on “Start a side chat”</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/adb0661470eb3be5a31496886d7df5e66bb1b0a1c6e87f1d67c6a4f14bd27a24" /><figcaption>Side pane for the side chat</figcaption></figure><p>Now I can ask all my questions in the side chat and keep the main conversation clean. I can also open more than one side chat.</p><h3>Fork (/branch in the terminal)</h3><p>Sometimes I want a new conversation that starts with the current context. For example, after a long session, CC understands the codebase and the feature. Now I want one conversation to write the code and another to write the tests. Both start from the same context.</p><p>In the desktop app, I type /fork &lt;my new query&gt; in the input box.</p><blockquote>Note: Fork works differently in the terminal./fork starts a subagent that inherits the whole conversation so far, instead of starting fresh./branch creates a new conversation with a copy of the parent’s context. This is what fork does in the desktop app.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/5b4be9d4c78a3f36cc8991684c2b1cc10f52c1ce841fd65b35d448a8ce6eafe1" /><figcaption>Forking a conversation in the desktop app</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/d96cd72021d6811f1367c7768fba593b2c83e1f7c74cec2671c8aabb04fe6c9e" /><figcaption>Forked conversation nested under its parent</figcaption></figure><h3>In short</h3><ul><li>Use side chat for a quick question.</li><li>Use fork when you want to start new work from the same context.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdee7e052279" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setup background tasks in Django using Celery]]></title>
            <link>https://gouthampilla.medium.com/setup-background-tasks-in-django-using-celery-b7dcd686ac37?source=rss-acc0bb64188d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7dcd686ac37</guid>
            <category><![CDATA[django]]></category>
            <category><![CDATA[celery]]></category>
            <category><![CDATA[django-background-tasks]]></category>
            <dc:creator><![CDATA[Goutham Pilla]]></dc:creator>
            <pubDate>Mon, 24 Jan 2022 10:04:13 GMT</pubDate>
            <atom:updated>2022-01-24T10:09:33.670Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*Ob1iQqflD0nqGQvcOOc5CA.png" /><figcaption>Reference: <a href="https://docs.celeryproject.org/en/stable/_static/celery_512.png">https://docs.celeryproject.org/</a></figcaption></figure><p>In this article, we will</p><ol><li>set up <a href="https://docs.celeryproject.org/en/stable/">celery</a>, integrate it with <a href="https://www.djangoproject.com/">Django</a> to send an instant email as a background task.</li><li>send scheduled emails using <a href="https://pypi.org/project/django-celery-beat/">django-celery-beat</a>.</li></ol><h3>Background tasks</h3><p>Let’s take an example of an e-commerce application. You have ordered your items and now you must receive an order confirmation email. One way is to send an email within the same web process or offload the email sending to a different process, say a background worker. Tasks that do not have to run immediately within the web process and can be offloaded to a different background worker are called <strong>background tasks</strong>.</p><p>Other examples include</p><ul><li>Converting a profile pic to a thumbnail to display as a profile pic.</li><li>Computing and sending reports at a scheduled time.</li><li>….</li></ul><p><strong>What are the advantages you get offloading tasks to a background process/worker?</strong></p><p>In case of an email:</p><ul><li>Users do not have to wait till the email is sent, the user experience improves.</li><li>If the email sending fails, you can have retry logic in place to resend the email.</li></ul><h3>Celery</h3><p>Celery is a task queue, a task is put in the queue, and celery workers process the task. Celery requires a messaging layer, called a broker, to communicate among workers. We will use Redis in this example. To schedule tasks using celery, we will use the celery-beat extension and database as the scheduler.</p><p>Let’s jump into the implementation now!</p><p>We will use the <a href="https://github.com/goutham2027/bookstore">bookstore app</a> as an example.</p><p><strong>Not so important note:</strong> There is nothing in the app other than examples for celery.</p><h4>Install the following dependencies</h4><p>Path to file: requirements.txt</p><pre>celery==5.2.3<br>django-celery-beat==2.2.1<br>Django==3.2.11<br>ipdb==0.13.9<br>redis==4.1.1</pre><h4><strong>Configure Django celery beat and celery</strong></h4><ol><li>Add django_celery_beat to INSTALLED_APPS in bookstore/settings.py.</li><li><a href="https://pypi.org/project/django-celery-beat/">django-celery-beat</a> has certain models which help us to schedule tasks. To apply migrations run — python manage.py migrate</li><li>As said earlier in the article, we will use Redis as the message broker. Start your redis server and add the CELERY_BROKER_URLto your Django settings. For bookstore app it is:bookstore/settings.py</li></ol><pre>CELERY_BROKER_URL = &#39;redis://localhost:6379&#39;</pre><h4>Email Backend</h4><p>We will use the <a href="https://docs.djangoproject.com/en/4.0/topics/email/#console-backend">console</a> as the EmailBackend. To send a real email configure the backend to SMTP and supply appropriate credentials. Refer to Django documentation on <a href="https://docs.djangoproject.com/en/4.0/topics/email/#email-backends">Email backends</a>.</p><p>Add the EMAIL_BACKEND config to bookstore/settings.py</p><pre>EMAIL_BACKEND = &#39;django.core.mail.backends.console.EmailBackend&#39;</pre><h4>Create celery app</h4><p>Path to file: bookstore/celery.py</p><pre>import os</pre><pre>from celery import Celery</pre><pre># Set the default Django settings module for the &#39;celery&#39; program.<br>os.environ.setdefault(&#39;DJANGO_SETTINGS_MODULE&#39;, &#39;bookstore.settings&#39;)</pre><pre>app = Celery(&#39;bookstore&#39;)</pre><pre># Using a string here means the worker doesn&#39;t have to serialize<br># the configuration object to child processes.<br># - namespace=&#39;CELERY&#39; means all celery-related configuration keys<br>#   should have a `CELERY_` prefix.<br>app.config_from_object(&#39;django.conf:settings&#39;, namespace=&#39;CELERY&#39;)</pre><pre># Load task modules from all registered Django apps.<br>app.autodiscover_tasks()</pre><p><strong>Create a celery task</strong></p><p>Path to file: web/tasks.py</p><pre>from django.core.mail import send_mail</pre><pre>from bookstore.celery import app</pre><pre>@app.task<br>def send_email(to, subject, body):<br>    send_mail(<br>        subject,<br>        body,</pre><pre>        # dummy from address, this doesn&#39;t matter<br>        # because we are using console as the Email backend</pre><pre>        &#39;from-default@gmail.com&#39;,<br>        [to]<br>    )</pre><p>To send instant email and schedule emails I’ve created a basic UI in Django. Start Django server, and celery</p><pre>python manage.py runserver</pre><pre>celery -A bookstore  worker -B  --scheduler django_celery_beat.schedulers:DatabaseScheduler --loglevel=INFO</pre><p>Option B is to start celery along with celery beat service and --scheduler is to specify which scheduler to use to schedule emails. In this case, we are using the database as the scheduler.</p><p>Visit <a href="http://localhost:8000/">http://localhost:8000</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JMDBrHz4C15mbZW9nvdsvA.png" /><figcaption>Home Page</figcaption></figure><h4>Send instant email</h4><p>Once the user submits the form, we will instruct celery to execute the task. Link to code: <a href="https://github.com/goutham2027/bookstore/blob/main/bookstore/web/views.py#L25">https://github.com/goutham2027/bookstore/blob/main/bookstore/web/views.py#L25</a></p><pre>send_email.delay(email, subject, body)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HoGytZL_Baj9RTuSje29rA.png" /><figcaption>Instant Email</figcaption></figure><p>Because we configured the console as the email backend, the actual email contents are printed onto the celery console — attached screenshot</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tX36ubuCziK6snGdjFU0mw.png" /><figcaption>Instant email — console output</figcaption></figure><h4>Scheduling an email</h4><p>To schedule an email, we will rely on Django celery beat’s <a href="https://django-celery-beat.readthedocs.io/en/latest/#example-creating-crontab-based-periodic-task">PeriodicTask</a> model.</p><p>PeriodicTask requires a crontab schedule or an interval, a unique name for the periodic task, actual task, and arguments if any. We will use the crontab schedule.</p><pre><strong>&gt;&gt;&gt; from</strong> <strong>django_celery_beat.models</strong> <strong>import</strong> CrontabSchedule, PeriodicTask<br><strong>&gt;&gt;&gt; </strong>schedule, _ = CrontabSchedule.objects.get_or_create(<br><strong>... </strong>    minute=&#39;30&#39;,<br><strong>... </strong>    hour=&#39;*&#39;,<br><strong>... </strong>    day_of_week=&#39;*&#39;,<br><strong>... </strong>    day_of_month=&#39;*&#39;,<br><strong>... </strong>    month_of_year=&#39;*&#39;,<br><strong>... </strong>)</pre><pre>&gt;&gt;&gt; PeriodicTask.objects.create(<br>...     crontab=schedule,<br>...     name=&#39;Importing contacts&#39;,<br>...     task=&#39;proj.tasks.import_contacts&#39;,<br>... )</pre><p>Link to code: <a href="https://github.com/goutham2027/bookstore/blob/main/bookstore/web/views.py#L46">https://github.com/goutham2027/bookstore/blob/main/bookstore/web/views.py#L46</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xyXJw8-byFEoGfIkRe-GwA.png" /><figcaption>Schedule Email</figcaption></figure><p>Once a new periodic task is created, you will see the following log printed to the celery console. This means the task has been scheduled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_KQGbyKT6L3X6PiaFC8MKw.png" /><figcaption>Periodic task created</figcaption></figure><p>Once the task is executed at the schedule, you will see the following log printed to the celery console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4scfbXg627UutZhdv2fBzQ.png" /><figcaption>Scheduled email log</figcaption></figure><h3>Gotchas</h3><ul><li>By default Celery schedules your tasks in UTC. Be wary if you are from a different timezone while testing. In the example, I am converting my local time to UTC before creating the periodic task. <a href="https://github.com/goutham2027/bookstore/blob/main/bookstore/web/views.py#L44">You can check here</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7dcd686ac37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up a maintenance page in k8s]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://gouthampilla.medium.com/setting-up-a-maintenance-page-in-k8s-f4f40d249da7?source=rss-acc0bb64188d------2"><img src="https://cdn-images-1.medium.com/max/1920/1*17LjqQsr7ePLbXe902FAcQ.png" width="1920"></a></p><p class="medium-feed-snippet">Site under maintenance</p><p class="medium-feed-link"><a href="https://gouthampilla.medium.com/setting-up-a-maintenance-page-in-k8s-f4f40d249da7?source=rss-acc0bb64188d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://gouthampilla.medium.com/setting-up-a-maintenance-page-in-k8s-f4f40d249da7?source=rss-acc0bb64188d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4f40d249da7</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[site-maintenance]]></category>
            <dc:creator><![CDATA[Goutham Pilla]]></dc:creator>
            <pubDate>Sat, 22 May 2021 16:45:34 GMT</pubDate>
            <atom:updated>2026-01-20T09:46:50.877Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[DNS01 and HTTP01 Solvers in a Single ClusterIssuer — Cert Manager]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Cert Manager verifies domain ownership using either DNS01 or HTTP01 solvers. For wildcard certs, we should use DNS01 solver. But what if&#x2026;</p><p class="medium-feed-link"><a href="https://gouthampilla.medium.com/dns01-and-http01-solvers-in-a-single-clusterissuer-cert-manager-ef419c0a268?source=rss-acc0bb64188d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://gouthampilla.medium.com/dns01-and-http01-solvers-in-a-single-clusterissuer-cert-manager-ef419c0a268?source=rss-acc0bb64188d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef419c0a268</guid>
            <category><![CDATA[cert-manager]]></category>
            <category><![CDATA[lets-encrypt]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[ingress]]></category>
            <dc:creator><![CDATA[Goutham Pilla]]></dc:creator>
            <pubDate>Wed, 20 Jan 2021 16:40:04 GMT</pubDate>
            <atom:updated>2021-03-15T18:21:56.677Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Generating Let’s Encrypt wildcard certs using cert-manager on GKE]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://gouthampilla.medium.com/generating-lets-encrypt-wildcard-certs-using-cert-manager-on-gke-25bf454e5904?source=rss-acc0bb64188d------2"><img src="https://cdn-images-1.medium.com/max/1400/1*u36XWFqThd1HbaMvqe2mbg.png" width="1400"></a></p><p class="medium-feed-snippet">In this article, we will create a Let&#x2019;s Encrypt wildcard certificate for a domain in GKE using cert-manager. For certificate issuing, we&#x2026;</p><p class="medium-feed-link"><a href="https://gouthampilla.medium.com/generating-lets-encrypt-wildcard-certs-using-cert-manager-on-gke-25bf454e5904?source=rss-acc0bb64188d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://gouthampilla.medium.com/generating-lets-encrypt-wildcard-certs-using-cert-manager-on-gke-25bf454e5904?source=rss-acc0bb64188d------2</link>
            <guid isPermaLink="false">https://medium.com/p/25bf454e5904</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cert-manager]]></category>
            <category><![CDATA[lets-encrypt]]></category>
            <category><![CDATA[gcp]]></category>
            <dc:creator><![CDATA[Goutham Pilla]]></dc:creator>
            <pubDate>Mon, 18 Jan 2021 17:06:48 GMT</pubDate>
            <atom:updated>2021-01-20T15:27:50.436Z</atom:updated>
        </item>
    </channel>
</rss>