<?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: Sanjaya Sahu</title>
    <description>The latest articles on DEV Community by Sanjaya Sahu (@sanjucse).</description>
    <link>https://dev.to/sanjucse</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257130%2F7d2b6bf6-a666-472a-8c1d-c2feae17c8ac.jpg</url>
      <title>DEV Community: Sanjaya Sahu</title>
      <link>https://dev.to/sanjucse</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sanjucse"/>
    <language>en</language>
    <item>
      <title>5 Cron Expression Mistakes That Wake You Up at 3 AM</title>
      <dc:creator>Sanjaya Sahu</dc:creator>
      <pubDate>Sat, 21 Nov 2026 10:51:39 +0000</pubDate>
      <link>https://dev.to/sanjucse/5-cron-expression-mistakes-that-wake-you-up-at-3-am-3h10</link>
      <guid>https://dev.to/sanjucse/5-cron-expression-mistakes-that-wake-you-up-at-3-am-3h10</guid>
      <description>&lt;p&gt;Cron looks simple until it pages you at 3 AM. Here are the mistakes I see most, and how to catch them before deploy.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Day-of-month and day-of-week are OR, not AND
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;0 9 1 * 1&lt;/code&gt; does not mean "9:00 on the 1st if it's a Monday". In standard cron, when both fields are restricted, the job runs when &lt;strong&gt;either&lt;/strong&gt; matches. So it fires on the 1st of every month and on every Monday.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Timezones and DST
&lt;/h2&gt;

&lt;p&gt;Cron runs in the server's timezone, and many hosted schedulers use UTC. A job at &lt;code&gt;30 2 * * *&lt;/code&gt; may be skipped or run twice on a DST change in local-time systems. Prefer UTC for anything important.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. &lt;code&gt;*/5&lt;/code&gt; is not "every 5 minutes from now"
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;*/5 * * * *&lt;/code&gt; means minutes 0, 5, 10... of each hour. &lt;code&gt;*/7&lt;/code&gt; fires at 0, 7, ..., 56, then again at 0, so there is a 4-minute gap at the top of each hour.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Overlapping runs
&lt;/h2&gt;

&lt;p&gt;If a job takes longer than its interval, you get parallel runs. Use a lock (&lt;code&gt;flock&lt;/code&gt;) or your scheduler's concurrency policy.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Not checking the next runs
&lt;/h2&gt;

&lt;p&gt;The cheapest test is to print the next 10 execution times and read them. I built a &lt;a href="https://webdevtoolbox.com/tools/cron-parser/?utm_source=devto&amp;amp;utm_medium=article" rel="noopener noreferrer"&gt;Cron Expression Parser&lt;/a&gt; that runs in your browser and shows the next runs. Nothing is sent to a server.&lt;/p&gt;

&lt;p&gt;Disclosure: I'm the author of that tool. What cron gotcha got you?&lt;/p&gt;

</description>
      <category>devops</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>linux</category>
    </item>
    <item>
      <title>Stop Pasting Your JWTs and API Keys Into Random Websites</title>
      <dc:creator>Sanjaya Sahu</dc:creator>
      <pubDate>Sat, 21 Nov 2026 10:25:25 +0000</pubDate>
      <link>https://dev.to/sanjucse/stop-pasting-your-jwts-and-api-keys-into-random-websites-1b89</link>
      <guid>https://dev.to/sanjucse/stop-pasting-your-jwts-and-api-keys-into-random-websites-1b89</guid>
      <description>&lt;p&gt;You have a failing request. You copy the JWT from the Authorization header, search "jwt decoder online", and paste it into the first result. Ten seconds later you know why the token is rejected.&lt;/p&gt;

&lt;p&gt;You also just handed a signed token, with user IDs, tenant names and maybe an email address, to a site you know nothing about.&lt;/p&gt;

&lt;h2&gt;
  
  
  What actually leaks
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;JWTs&lt;/strong&gt;: claims often contain user IDs, emails, roles and internal tenant identifiers. Until it expires, the token may also be replayable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;JSON payloads&lt;/strong&gt;: API responses copied from production regularly contain PII, internal hostnames and secrets.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Configs and logs&lt;/strong&gt;: &lt;code&gt;.env&lt;/code&gt; snippets, connection strings, Nginx configs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Base64 blobs&lt;/strong&gt;: people forget that Base64 is encoding, not encryption.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A 30-second check for any online tool
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open DevTools (F12) and go to the &lt;strong&gt;Network&lt;/strong&gt; tab.&lt;/li&gt;
&lt;li&gt;Clear the log, then paste your input and click the tool's button.&lt;/li&gt;
&lt;li&gt;If a request fires with your input in the body or query string, the tool sends your data to a server.&lt;/li&gt;
&lt;li&gt;If nothing fires, processing is happening locally. For extra safety, turn on "Offline" in the Network tab and try again. A client-side tool keeps working.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Note that analytics scripts can load on the page. That is different from your input being transmitted, so look at what the requests contain.&lt;/p&gt;

&lt;h2&gt;
  
  
  Safer habits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Prefer tools that run entirely in the browser.&lt;/li&gt;
&lt;li&gt;Use local CLI tools for anything sensitive: &lt;code&gt;jq&lt;/code&gt;, &lt;code&gt;base64&lt;/code&gt;, &lt;code&gt;openssl&lt;/code&gt;, &lt;code&gt;jwt-cli&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Never paste long-lived production secrets anywhere. Rotate them if you did.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Client-side tools I built for this
&lt;/h2&gt;

&lt;p&gt;I built &lt;a href="https://webdevtoolbox.com/?utm_source=devto&amp;amp;utm_medium=article" rel="noopener noreferrer"&gt;WebDevToolbox&lt;/a&gt; because I wanted these utilities without worrying about where the input goes. They run in your browser, with no signup:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://webdevtoolbox.com/tools/jwt-decoder/?utm_source=devto&amp;amp;utm_medium=article" rel="noopener noreferrer"&gt;JWT Decoder&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://webdevtoolbox.com/tools/json-formatter/?utm_source=devto&amp;amp;utm_medium=article" rel="noopener noreferrer"&gt;JSON Formatter&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://webdevtoolbox.com/tools/base64-encode/?utm_source=devto&amp;amp;utm_medium=article" rel="noopener noreferrer"&gt;Base64 Encode / Decode&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://webdevtoolbox.com/tools/password-generator/?utm_source=devto&amp;amp;utm_medium=article" rel="noopener noreferrer"&gt;Password Generator&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Disclosure: I'm the author. Verify the claim yourself with the Network-tab check above; it works on any tool, including mine.&lt;/p&gt;

&lt;p&gt;What developer tool would you like to see added next?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>security</category>
      <category>privacy</category>
      <category>tools</category>
    </item>
  </channel>
</rss>
