<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dev Chavda</title>
    <description>The latest articles on DEV Community by Dev Chavda (@daredevil_gotham).</description>
    <link>https://dev.to/daredevil_gotham</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3919809%2F6aab6017-aabb-464a-b54b-677c0dc0982f.jpg</url>
      <title>DEV Community: Dev Chavda</title>
      <link>https://dev.to/daredevil_gotham</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/daredevil_gotham"/>
    <language>en</language>
    <item>
      <title>FINANCE PRO: PAYTRACK</title>
      <dc:creator>Dev Chavda</dc:creator>
      <pubDate>Sat, 09 May 2026 13:30:00 +0000</pubDate>
      <link>https://dev.to/daredevil_gotham/finance-pro-paytrack-55na</link>
      <guid>https://dev.to/daredevil_gotham/finance-pro-paytrack-55na</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo9ete8hwt5af04kq4n0x.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo9ete8hwt5af04kq4n0x.png" alt=" " width="800" height="440"&gt;&lt;/a&gt;&lt;br&gt;
One unexpected challenge while building PayTrack this week:&lt;/p&gt;

&lt;p&gt;The backend suddenly stopped communicating with Supabase even though the application code was completely correct.&lt;/p&gt;

&lt;p&gt;After hours of debugging Flask configs, API requests, credentials, CORS, and network calls, the actual issue turned out to be DNS routing from the ISP itself.&lt;/p&gt;

&lt;p&gt;The backend simply could not properly reach Supabase servers.&lt;/p&gt;

&lt;p&gt;Changing DNS settings to Google/Cloudflare fixed the issue instantly.&lt;/p&gt;

&lt;p&gt;Interesting reminder that software debugging is often larger than the application code itself. Infrastructure, networking, DNS, and external services can quietly become the real source of failure.&lt;/p&gt;

</description>
      <category>backend</category>
      <category>fullstack</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
    <item>
      <title>BIG UPDATE</title>
      <dc:creator>Dev Chavda</dc:creator>
      <pubDate>Sat, 09 May 2026 06:05:45 +0000</pubDate>
      <link>https://dev.to/daredevil_gotham/big-update-2kd6</link>
      <guid>https://dev.to/daredevil_gotham/big-update-2kd6</guid>
      <description>&lt;p&gt;Recently started working on a finance-related project focused on trading data and analytics.&lt;/p&gt;

&lt;p&gt;Still in the early phase, but this is probably going to be one of the biggest and most technical projects I’ve worked on so far.&lt;/p&gt;

&lt;p&gt;Will share progress and things I learn while building it.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>productivity</category>
      <category>learning</category>
    </item>
    <item>
      <title>Why I Started Writing Technical Articles</title>
      <dc:creator>Dev Chavda</dc:creator>
      <pubDate>Fri, 08 May 2026 10:16:38 +0000</pubDate>
      <link>https://dev.to/daredevil_gotham/why-i-started-writing-technical-articles-2c06</link>
      <guid>https://dev.to/daredevil_gotham/why-i-started-writing-technical-articles-2c06</guid>
      <description>&lt;p&gt;For the past several years, I've been learning about different things like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;engineering,&lt;/li&gt;
&lt;li&gt;data analysis,&lt;/li&gt;
&lt;li&gt;automating processes,&lt;/li&gt;
&lt;li&gt;PR and recruiting processes,&lt;/li&gt;
&lt;li&gt;improving systems, and&lt;/li&gt;
&lt;li&gt;troubleshooting engineering problems. &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One thing I've noticed over and over again is that there are many engineering practices that are not documented very well.&lt;/p&gt;

&lt;p&gt;Most of what you find online about engineering is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;either too theoretical,&lt;/li&gt;
&lt;li&gt;or too simple,&lt;/li&gt;
&lt;li&gt;or is written by someone who has never tried to do the thing they are talking about. &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So I decided I was going to start writing.&lt;/p&gt;

&lt;p&gt;This blog will be about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;engineering techniques that work in real life,&lt;/li&gt;
&lt;li&gt;workflows that actually work,&lt;/li&gt;
&lt;li&gt;ways to automate tasks,&lt;/li&gt;
&lt;li&gt;how to recruit engineers,&lt;/li&gt;
&lt;li&gt;what you need to know about back-end development, &lt;/li&gt;
&lt;li&gt;using software to improve your productivity,&lt;/li&gt;
&lt;li&gt;and things I've learned along the way from building solutions like these. &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ultimately, my goal is to create useful content for engineers, recruiters, data analysts, and anyone else looking for ways to enhance their technical capabilities.&lt;/p&gt;

&lt;p&gt;No exaggerations. &lt;br&gt;
No "hacks" to making yourself more organised and efficient. &lt;br&gt;
No recycled fluff from someone who didn't build what they are writing about.&lt;/p&gt;

&lt;p&gt;Only useful descriptions of practical processes, observations from the field, and systems that produce positive results.&lt;/p&gt;

&lt;p&gt;Stay tuned for my first article soon!&lt;/p&gt;

</description>
      <category>programming</category>
      <category>beginners</category>
      <category>career</category>
    </item>
  </channel>
</rss>
