<?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: Vishal Pandey</title>
    <description>The latest articles on DEV Community by Vishal Pandey (@vishal_vigilante).</description>
    <link>https://dev.to/vishal_vigilante</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%2F4036770%2F56410924-c986-4a5a-ad11-fc0ac7c4426c.jpg</url>
      <title>DEV Community: Vishal Pandey</title>
      <link>https://dev.to/vishal_vigilante</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vishal_vigilante"/>
    <language>en</language>
    <item>
      <title>I capped my game's streak bonus at 1.5x. Here's the math on breaking a streak.</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Tue, 17 Nov 2026 04:32:00 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/i-capped-my-games-streak-bonus-at-15x-heres-the-math-on-breaking-a-streak-9og</link>
      <guid>https://dev.to/vishal_vigilante/i-capped-my-games-streak-bonus-at-15x-heres-the-math-on-breaking-a-streak-9og</guid>
      <description>&lt;p&gt;The most dangerous day in any streak isn't day 1. It's the day after you break it.&lt;/p&gt;

&lt;p&gt;You miss one evening. The counter goes from 23 back to 0. And some quiet voice says: well, that's ruined, might as well take the week off.&lt;/p&gt;

&lt;p&gt;I've felt that voice. If you've ever done #100DaysOfCode, you probably have too.&lt;/p&gt;

&lt;p&gt;So when I was designing the daily rewards for Vigilante (my free browser game where real GitHub pushes open the next day of a 3D survival story), I had one question that took longer than any of the 3D code:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How big should the streak bonus get?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The answer I shipped is small and a bit boring: the daily supply crate gets &lt;strong&gt;x1.2 at 3 days&lt;/strong&gt; and &lt;strong&gt;x1.5 at 7+ days&lt;/strong&gt;. And then it stops growing. Forever.&lt;/p&gt;

&lt;p&gt;That sounds like a weak reward. Here's why I think it's the right one, with the numbers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The usual advice: make long streaks feel huge
&lt;/h2&gt;

&lt;p&gt;Most streak systems scale with the streak. The longer you go, the bigger the bonus, because you want people to feel the weight of what they've built.&lt;/p&gt;

&lt;p&gt;That works great right up until the streak breaks. Then the same weight lands on your foot.&lt;/p&gt;

&lt;p&gt;Let's compare three ways to scale a reward. This is a simplified sketch to show the shape of the curves, not the production code:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Three ways to scale a daily reward by streak length.&lt;/span&gt;
&lt;span class="c1"&gt;// Simplified sketch for this post, not Vigilante's real code.&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;linear&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;streak&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="mf"&gt;0.1&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;streak&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;          &lt;span class="c1"&gt;// +10% per day, no cap&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;doubling&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;streak&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;pow&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;floor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;streak&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// doubles every week&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;capped&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;streak&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;streak&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="mf"&gt;1.5&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;streak&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="mf"&gt;1.2&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="mf"&gt;1.0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now the question that matters: &lt;strong&gt;what does a break cost you?&lt;/strong&gt; When a streak breaks, the multiplier falls back to 1.0. So the loss is how much of your daily reward vanishes overnight:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;lossOnBreak&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;scale&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;streak&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt;
  &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="nf"&gt;scale&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;streak&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;14&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;30&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nf"&gt;lossOnBreak&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;linear&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toFixed&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nf"&gt;lossOnBreak&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;doubling&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toFixed&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nf"&gt;lossOnBreak&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;capped&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toFixed&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run that and you get:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Streak broken at&lt;/th&gt;
&lt;th&gt;Linear (+10%/day)&lt;/th&gt;
&lt;th&gt;Doubling weekly&lt;/th&gt;
&lt;th&gt;Capped (x1.5)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Day 7&lt;/td&gt;
&lt;td&gt;41%&lt;/td&gt;
&lt;td&gt;50%&lt;/td&gt;
&lt;td&gt;33%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Day 14&lt;/td&gt;
&lt;td&gt;58%&lt;/td&gt;
&lt;td&gt;75%&lt;/td&gt;
&lt;td&gt;33%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Day 30&lt;/td&gt;
&lt;td&gt;75%&lt;/td&gt;
&lt;td&gt;94%&lt;/td&gt;
&lt;td&gt;33%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Read the last row slowly.&lt;/p&gt;

&lt;p&gt;With the "make it feel huge" curves, the person who showed up for 30 days straight is the one who gets punished hardest for one bad evening. With a doubling curve, they lose 94% of their reward. The most loyal player takes the biggest hit.&lt;/p&gt;

&lt;p&gt;With the cap, a break always costs the same 33%. Day 7 or day 300, missing a day stings exactly as much. Not more.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why "not more" matters
&lt;/h2&gt;

&lt;p&gt;Think of a cricket batter on 94. The crowd is quiet. Every ball feels like it could end everything. Cricket even has a name for it: the nervous nineties.&lt;/p&gt;

&lt;p&gt;An uncapped streak turns every day after day 30 into batting on 94.&lt;/p&gt;

&lt;p&gt;I don't want someone's side project to feel like that. I want day 41 to feel like day 8: show up, push something real, open the crate, go to sleep.&lt;/p&gt;

&lt;p&gt;The cap also kills a second problem. When the bonus keeps growing, the bonus becomes the reason you code. With a cap, after a week the crate stops getting bigger. The only thing still growing is the project. That's the thing I actually want to grow.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a "day" has to be for any of this to work
&lt;/h2&gt;

&lt;p&gt;A gentle reward system only works if the days are real. Otherwise people (me included, on a tired night) will just feed it junk.&lt;/p&gt;

&lt;p&gt;So a day in Vigilante is only verified from real GitHub push data, and some commits are filtered out on purpose: merge commits, empty commits, and commits that only touch lock files or config. The game never reads the code itself, only commit IDs, timestamps and file names.&lt;/p&gt;

&lt;p&gt;That's the deal: the reward is gentle, the definition of a day is strict.&lt;/p&gt;

&lt;h2&gt;
  
  
  The other two rules I keep coming back to
&lt;/h2&gt;

&lt;p&gt;Capping the bonus was one decision. Two others came from the same thinking.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. A repaired day is not a verified day.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;There's an item called Revival Fluid that repairs a missed day so the story can continue. But it never counts as verified. Your share card and your record still show the truth. I'd rather the game forgive you than lie for you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Money never opens a day.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;There are optional purchases, but buying anything never opens a story day or counts as verified work. If money could buy a day, the streak would stop meaning "I showed up." It would mean "I paid."&lt;/p&gt;

&lt;p&gt;Both of these are the same idea as the cap: protect what the streak means, and keep the pain of a bad day small.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you're building any kind of streak
&lt;/h2&gt;

&lt;p&gt;Here's the short version I wish I'd had before starting:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Calculate the loss on break, not just the reward.&lt;/strong&gt; Run &lt;code&gt;lossOnBreak&lt;/code&gt; for day 30 before you ship any curve. If the number scares you, it'll scare your users more.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cap early.&lt;/strong&gt; A week is long enough to build a habit worth rewarding. After that, the reward should be the work itself.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Be strict about what counts.&lt;/strong&gt; Gentle rewards plus loose rules equals a streak full of empty commits.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Let people recover, but never fake the record.&lt;/strong&gt; Repairs keep someone in the game. Honest records keep the game worth playing.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this is new psychology. It's mostly just refusing to punish the people who stayed the longest.&lt;/p&gt;

&lt;p&gt;If you want to see how it feels in practice, the &lt;a href="https://vigilante.ocix.in/github-streak-tracker?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=automarket&amp;amp;utm_content=p76" rel="noopener noreferrer"&gt;GitHub streak tracker&lt;/a&gt; is free and Day 1 of the game needs no sign-up. Full disclosure: I built it, nights and weekends, around a Java day job.&lt;/p&gt;

&lt;p&gt;What's the longest streak you've ever broken, and what did you do the next day?&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>productivity</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
    <item>
      <title>How many of your commits are real? A 20-line git script</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Fri, 13 Nov 2026 17:21:35 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/how-many-of-your-commits-are-real-a-20-line-git-script-4ll9</link>
      <guid>https://dev.to/vishal_vigilante/how-many-of-your-commits-are-real-a-20-line-git-script-4ll9</guid>
      <description>&lt;p&gt;Your GitHub graph says 30 commits this month. Does it mean 30 days of real work?&lt;/p&gt;

&lt;p&gt;I build Vigilante, a free browser game where verified GitHub pushes open the next day of the story. To make that fair, I had to answer one question: what counts as a real commit? Some commits are noise. Merges, empty commits and lock-file-only changes are the usual ones. Vigilante filters those out.&lt;/p&gt;

&lt;p&gt;You don't need my game to check this. Here is a small script that sorts your own history. I tested it on a throwaway repo.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three kinds of noise
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Merge commits.&lt;/strong&gt; They have two parents. Git creates them when you join branches. The work was done in the branch commits, so the merge adds no new work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Empty commits.&lt;/strong&gt; &lt;code&gt;git commit --allow-empty&lt;/code&gt; makes a commit with no file changes at all. It takes two seconds and keeps a green square alive. It also proves nothing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Lock-file-only commits.&lt;/strong&gt; A dependency bump can touch only &lt;code&gt;package-lock.json&lt;/code&gt; or &lt;code&gt;yarn.lock&lt;/code&gt;. That is machine output, not your thinking.&lt;/p&gt;

&lt;h2&gt;
  
  
  The script
&lt;/h2&gt;

&lt;p&gt;Save this as &lt;code&gt;junk.sh&lt;/code&gt; and run it inside any repo:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;#!/usr/bin/env bash&lt;/span&gt;
&lt;span class="c"&gt;# Sort the last N commits into "real" and "noise"&lt;/span&gt;
&lt;span class="nv"&gt;N&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;${1:-30}&lt;/span&gt;
&lt;span class="nv"&gt;real&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;0&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="nv"&gt;noise&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;0
&lt;span class="k"&gt;for&lt;/span&gt; c &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nv"&gt;$(&lt;/span&gt;git rev-list --max-count=&lt;span class="s2"&gt;"$N"&lt;/span&gt; HEAD&lt;span class="o"&gt;)&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;do&lt;/span&gt;
  &lt;span class="c"&gt;# 1 word = root commit, 2 = normal, 3+ = merge&lt;/span&gt;
  &lt;span class="nv"&gt;parents&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$(&lt;/span&gt;git rev-list --parents -n 1 &lt;span class="s2"&gt;"$c"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; wc -w&lt;span class="o"&gt;)&lt;/span&gt;
  &lt;span class="nv"&gt;files&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$(&lt;/span&gt;git diff-tree --root --no-commit-id --name-only -r -m --first-parent &lt;span class="s2"&gt;"$c"&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt;

  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="o"&gt;[&lt;/span&gt; &lt;span class="s2"&gt;"$parents"&lt;/span&gt; -gt 2 &lt;span class="o"&gt;]&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then&lt;/span&gt; &lt;span class="nv"&gt;kind&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"merge"&lt;/span&gt;
  &lt;span class="k"&gt;elif&lt;/span&gt; &lt;span class="o"&gt;[&lt;/span&gt; -z &lt;span class="s2"&gt;"$files"&lt;/span&gt; &lt;span class="o"&gt;]&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then&lt;/span&gt; &lt;span class="nv"&gt;kind&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"empty"&lt;/span&gt;
  &lt;span class="k"&gt;elif&lt;/span&gt; ! &lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"$files"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; grep -qvE &lt;span class="s1"&gt;'(^|/)(package-lock\.json|yarn\.lock|pnpm-lock\.yaml|Cargo\.lock|poetry\.lock|go\.sum)$'&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then&lt;/span&gt; &lt;span class="nv"&gt;kind&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"lockfile-only"&lt;/span&gt;
  &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="nv"&gt;kind&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"real"&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;fi&lt;/span&gt;

  &lt;span class="nb"&gt;printf&lt;/span&gt; &lt;span class="s1"&gt;'%-14s %s\n'&lt;/span&gt; &lt;span class="s2"&gt;"$kind"&lt;/span&gt; &lt;span class="s2"&gt;"$(git log -1 --format='%h %s' "&lt;/span&gt;&lt;span class="nv"&gt;$c&lt;/span&gt;&lt;span class="s2"&gt;")"&lt;/span&gt;
  &lt;span class="o"&gt;[&lt;/span&gt; &lt;span class="s2"&gt;"$kind"&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; real &lt;span class="o"&gt;]&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nv"&gt;real&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$(&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;real+1&lt;span class="o"&gt;)&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="nv"&gt;noise&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$(&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;noise+1&lt;span class="o"&gt;)&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;done&lt;/span&gt;
&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"real: $real  noise: $noise"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bash junk.sh 50
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;git rev-list --parents -n 1 &amp;lt;commit&amp;gt;&lt;/code&gt; prints the commit and its parents. Counting the words tells us if it is a merge.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;git diff-tree --name-only&lt;/code&gt; lists the files the commit touched. No files means an empty commit. The &lt;code&gt;--root&lt;/code&gt; flag makes the very first commit of a repo show its files too. Without it, the first commit of a repo would be reported as empty.&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;grep -qvE&lt;/code&gt; line asks one question: is there any file that is not a lock file? If not, the commit is lock-file-only.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  A test you can repeat
&lt;/h2&gt;

&lt;p&gt;I made a repo with five commits: one real change, one empty commit, a lock-file-only commit, a feature on a branch, and the merge of that branch.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;merge          5d58535 Merge f
lockfile-only  a64ba80 lock
real           bf53283 feat
empty          0ac05eb keep streak
real           5700773 real work
real: 2  noise: 3
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Five commits on the graph. Two days of actual work. That gap is the whole point.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the script can't know
&lt;/h2&gt;

&lt;p&gt;Be honest about the limits.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It cannot tell a thoughtful commit from &lt;code&gt;fix typo&lt;/code&gt; repeated daily. Judging that is hard, and I won't pretend a regex can.&lt;/li&gt;
&lt;li&gt;It treats config files as real. If you want to filter &lt;code&gt;.github/&lt;/code&gt; or formatting-only commits, add patterns to the lock-file list.&lt;/li&gt;
&lt;li&gt;Squash merges look like normal commits, which is correct, since they carry real changes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So treat the output as a prompt for a question, not as a grade.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I care about this
&lt;/h2&gt;

&lt;p&gt;A streak is only motivating if it is true. If an empty commit can keep it alive, the streak measures whether you opened a terminal, not whether you built anything. That is why a verified day in Vigilante comes from real pushes, and why buying something in the game never counts as one.&lt;/p&gt;

&lt;p&gt;If you want a quick look at your own last 30 days without running anything, Vigilante has a free GitHub check-up for public activity. Full disclosure, I built it. The script above is enough if you prefer to stay in your terminal.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it on yourself
&lt;/h2&gt;

&lt;p&gt;Run the script on a repo you have worked on for a month. Count the noise. Then ask one thing: on how many of those days did I actually change something that matters?&lt;/p&gt;

&lt;p&gt;I'm curious what ratio you get. Drop it in the comments, and tell me which kind of noise shows up most in your history: merges, empty commits or lock files.&lt;/p&gt;

</description>
      <category>git</category>
      <category>github</category>
      <category>bash</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Designing streak rewards that don't pay for commit spam</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Tue, 10 Nov 2026 04:34:58 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/designing-streak-rewards-that-dont-pay-for-commit-spam-1l66</link>
      <guid>https://dev.to/vishal_vigilante/designing-streak-rewards-that-dont-pay-for-commit-spam-1l66</guid>
      <description>&lt;p&gt;Streaks are a strange design problem. The moment you reward people for showing up every day, you also reward them for faking it.&lt;/p&gt;

&lt;p&gt;GitHub's contribution graph is the classic example. A green square for an empty commit looks exactly the same as a green square for a real fix. So when I started building Vigilante, a free browser game where your GitHub pushes open the next day of the story, the reward rules mattered more to me than the 3D city did.&lt;/p&gt;

&lt;p&gt;This post walks through the rules as they exist today, and why each one is there. The code is a simplified sketch in Java (my day job language) to show the shape of the logic, not a copy of production code.&lt;/p&gt;

&lt;h2&gt;
  
  
  The rule everything else hangs on: one verified day
&lt;/h2&gt;

&lt;p&gt;You pick one repo and a daily commit target. When GitHub sends a push webhook for that repo, the game checks the commits. If enough of them are meaningful, that day is verified, and the next day of the game opens.&lt;/p&gt;

&lt;p&gt;"Meaningful" is doing a lot of work there. Vigilante filters out:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;merge commits&lt;/li&gt;
&lt;li&gt;empty commits&lt;/li&gt;
&lt;li&gt;commits that only touch lock files or config&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It also only looks at metadata: commit IDs, timestamps and file names. It never reads your code or diffs. Commit messages are only used if you opt in.&lt;/p&gt;

&lt;p&gt;Here is roughly what that filter looks like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="k"&gt;record&lt;/span&gt; &lt;span class="nc"&gt;CommitInfo&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;String&lt;/span&gt; &lt;span class="n"&gt;id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;Instant&lt;/span&gt; &lt;span class="n"&gt;timestamp&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;parentCount&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;List&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="kt"&gt;String&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;files&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="kt"&gt;Set&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="kt"&gt;String&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="no"&gt;LOCK_FILES&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kt"&gt;Set&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;of&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="s2"&gt;"package-lock.json"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"yarn.lock"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"pnpm-lock.yaml"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"Cargo.lock"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"poetry.lock"&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="kt"&gt;boolean&lt;/span&gt; &lt;span class="nf"&gt;isMeaningful&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;CommitInfo&lt;/span&gt; &lt;span class="n"&gt;c&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;parentCount&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;          &lt;span class="c1"&gt;// merge commit&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;files&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;isEmpty&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;          &lt;span class="c1"&gt;// empty commit&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;files&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stream&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
            &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;anyMatch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt; &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nf"&gt;isLockOrConfigOnly&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// at least one real file&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="kt"&gt;boolean&lt;/span&gt; &lt;span class="nf"&gt;isLockOrConfigOnly&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;String&lt;/span&gt; &lt;span class="n"&gt;path&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kt"&gt;String&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Path&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;of&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;path&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getFileName&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toString&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="no"&gt;LOCK_FILES&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;contains&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="nf"&gt;isConfigFile&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The list of what counts as "config" is the part that needs the most judgment, and I'd rather keep it conservative than clever. The point isn't to catch every trick. The point is that the cheapest possible move (an empty commit) gets you nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rewards scale with consistency, not volume
&lt;/h2&gt;

&lt;p&gt;Once a day is verified, you get a daily supply crate. The crate has a streak multiplier:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;3 days in a row: x1.2&lt;/li&gt;
&lt;li&gt;7 or more days in a row: x1.5&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's it. There is no bonus for pushing 40 commits instead of 4. Your daily target is the bar, and going way past it doesn't pay extra.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="kt"&gt;double&lt;/span&gt; &lt;span class="nf"&gt;crateMultiplier&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;streakDays&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;streakDays&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="mf"&gt;1.5&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;streakDays&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="mf"&gt;1.2&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="mf"&gt;1.0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="nc"&gt;Crate&lt;/span&gt; &lt;span class="nf"&gt;dailyCrate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;verifiedStreak&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nc"&gt;Crate&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="k"&gt;base&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;scaledBy&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;crateMultiplier&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;verifiedStreak&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I like this shape for two reasons.&lt;/p&gt;

&lt;p&gt;First, it rewards the thing that's actually hard. Writing a lot of code on one good Saturday is easy. Showing up on a tired Tuesday after office is the hard part, and that's what the multiplier is tied to.&lt;/p&gt;

&lt;p&gt;Second, it caps out early. After a week, the reward stops climbing. Nobody needs to feel that day 60 is "worth more" than day 8. You just keep the x1.5 as long as you keep showing up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Missing a day: repair, but never fake
&lt;/h2&gt;

&lt;p&gt;Real life happens. Mondays happen. So there's an item called Revival Fluid that repairs a missed day.&lt;/p&gt;

&lt;p&gt;The important part is what it does not do. A repaired day never counts as verified. It keeps your story from collapsing, but it doesn't pretend you coded.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="k"&gt;enum&lt;/span&gt; &lt;span class="nc"&gt;DayStatus&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="no"&gt;VERIFIED&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="no"&gt;REPAIRED&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="no"&gt;MISSED&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="kt"&gt;boolean&lt;/span&gt; &lt;span class="nf"&gt;countsAsVerified&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;DayStatus&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="nc"&gt;DayStatus&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;VERIFIED&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// REPAIRED is never verified&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That separation shows up everywhere else too. The share card you get for each day is only for verified days, because the whole point of the card is that it's proof.&lt;/p&gt;

&lt;h2&gt;
  
  
  Money never buys a verified day
&lt;/h2&gt;

&lt;p&gt;Vigilante is free to play, and every story day is included. There are optional purchases (Revival Fluid, and a Pro pass with no auto-renewal), but buying anything never unlocks a day and never counts as verified work.&lt;/p&gt;

&lt;p&gt;If you build anything with streaks and payments, I'd treat this as a hard wall in the data model, not a policy line in the FAQ. Keep "what the user paid for" and "what the user actually did" in separate fields, and never let one write to the other.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Purchases can add items to the inventory.&lt;/span&gt;
&lt;span class="c1"&gt;// They can never change a DayStatus.&lt;/span&gt;
&lt;span class="kt"&gt;void&lt;/span&gt; &lt;span class="nf"&gt;applyPurchase&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;Player&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;Item&lt;/span&gt; &lt;span class="n"&gt;item&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;inventory&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;item&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Small daily loops around the big one
&lt;/h2&gt;

&lt;p&gt;Around the main loop there are a few lighter ones: a 7-day check-in calendar, 3 daily missions, and a daily mystery coding question. These are there so that opening the game feels like something, even on a day you haven't pushed yet.&lt;/p&gt;

&lt;p&gt;But none of them can stand in for a push. The story only moves when GitHub says you shipped something real.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell anyone designing streaks
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Decide what the cheapest fake looks like, and make it worth zero.&lt;/strong&gt; For commits that's empty and merge commits.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reward consistency, not volume.&lt;/strong&gt; A multiplier based on streak length is enough. Don't pay for raw commit counts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cap the multiplier.&lt;/strong&gt; Make the reward flat after a point so people aren't scared of breaking a huge number.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Let people recover without lying.&lt;/strong&gt; A "repaired" state is kinder than a reset, as long as it's clearly not "verified".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Wall off payments from progress.&lt;/strong&gt; In the schema, not just in the copy.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you want to see how these rules feel from the player side, Day 1 is free in the browser with no sign-up: &lt;a href="https://myvigilante.ocix.in/sign-up?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=devto_streak_rewards_20261110" rel="noopener noreferrer"&gt;play Day 1 of Vigilante&lt;/a&gt;. Full disclosure, I built it.&lt;/p&gt;

&lt;p&gt;How do you handle missed days in your own habit or streak systems? Reset to zero, or something softer?&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>github</category>
      <category>java</category>
      <category>productivity</category>
    </item>
    <item>
      <title>AI code review just delayed PostgreSQL 19. Finding bugs is now cheap and fixing them isn’t.</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Sat, 17 Oct 2026 16:30:43 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/ai-code-review-just-delayed-postgresql-19-finding-bugs-is-now-cheap-and-fixing-them-isnt-2mm5</link>
      <guid>https://dev.to/vishal_vigilante/ai-code-review-just-delayed-postgresql-19-finding-bugs-is-now-cheap-and-fixing-them-isnt-2mm5</guid>
      <description>&lt;p&gt;PostgreSQL 19 was supposed to ship in October. The release team now says general availability is November 19, with RC 2 on November 12 (postgresql.org’s RC 1 announcement has the dates). The reason is the interesting part.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What happened&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;According to The Register’s report, developers reverted or pulled between 8 and 10 significant features and pushed them to PostgreSQL 20. Some of them, like SQL/PGQ graph queries, had architectural issues that would have been hard to fix during beta.&lt;/p&gt;

&lt;p&gt;LLM-assisted code review also surfaced a long list of defects. The Register cites roughly 40 defect reports, mostly small edge cases that would previously have turned up later, if at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It wasn’t “vibe coding”&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Peter Eisentraut (EDB, a PostgreSQL committer) was explicit, as relayed by The Register: vibe coding did not cause the reverts, because those tools weren’t available when most of the features were written. The AI didn’t write the bugs. It found them.&lt;/p&gt;

&lt;p&gt;One caveat. Independent write-ups argue that AI wasn’t the only cause. Review capacity, and late-cycle review timing, mattered too. Treat “AI found the bugs” as the headline, not the whole story.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;The real lesson: the bottleneck moved&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Every defect still needs a human to triage it, fix it, test it, and review the fix. Finding bugs got cheap. Fixing them didn’t.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you maintain a codebase, the practical takeaways are:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Run AI review before you merge, not after. Late findings are expensive. Early findings are cheap.&lt;/li&gt;
&lt;li&gt;Keep changes small. A small diff means a small fix.&lt;/li&gt;
&lt;li&gt;Verify every fix with tests. AI-suggested fixes still need proof.&lt;/li&gt;
&lt;li&gt;What I’m doing about it&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I’m biasing toward small, verified commits. I build &lt;a href="https://myvigilante.ocix.in/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=settlement-autumn-2026&amp;amp;utm_content=devto-2" rel="noopener noreferrer"&gt;Vigilante&lt;/a&gt;, a free game that turns GitHub-verified commits into a settlement you build. It’s a small nudge toward the habit this story argues for.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sources:&lt;/strong&gt; &lt;em&gt;postgresql.org RC 1 announcement; The Register (Oct 16, 2026).&lt;/em&gt;&lt;/p&gt;

</description>
      <category>postgres</category>
      <category>ai</category>
      <category>opensource</category>
      <category>codereview</category>
    </item>
    <item>
      <title>My PixiJS game worked locally and broke in production. The culprit was one CSP word.</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Fri, 16 Oct 2026 18:27:49 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/my-pixijs-game-worked-locally-and-broke-in-production-the-culprit-was-one-csp-word-b4j</link>
      <guid>https://dev.to/vishal_vigilante/my-pixijs-game-worked-locally-and-broke-in-production-the-culprit-was-one-csp-word-b4j</guid>
      <description>&lt;p&gt;Vigilante’s town is a PixiJS 8 scene inside a React 19 and Vite app, hosted on Vercel. Locally it was fine. In production, the settlement scene broke.&lt;/p&gt;

&lt;p&gt;The screen became a blank canvas and one console error.&lt;/p&gt;

&lt;p&gt;Nothing in the code had changed between the two environments. The page’s security headers had.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;Dev and production aren’t the same browser environment&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Our production Content Security Policy is set in vercel.json. It’s strict on purpose: scripts only from our own origin and a short list of payment and ad domains, and no 'unsafe-eval'. That blocks eval() and new Function().&lt;/p&gt;

&lt;p&gt;npm run dev doesn’t serve those headers. So anything that evaluates code at runtime works locally, and you only find out in production.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why a renderer needs eval&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For speed, PixiJS generates small pieces of JavaScript at runtime, such as the functions that upload shader uniforms, and compiles them with new Function(). It’s a common performance trick, and a strict CSP blocks it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The fix: one import with a confusing name&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;PixiJS 8 ships eval-free versions of that generated code. You opt in with a side-effect import before creating the renderer:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Production CSP has no 'unsafe-eval'; this swaps Pixi's generated&lt;/span&gt;
&lt;span class="c1"&gt;// shader/uniform code for eval-free versions.&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;pixi.js/unsafe-eval&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Despite the name, this import lets Pixi work without unsafe-eval. We kept the policy strict and fixed the renderer, rather than loosening security for one game scene.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Making sure it can’t come back&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A unit test holds both halves in place. It checks that the production CSP still has no 'unsafe-eval', and that the scene file still starts with that import. If someone “cleans up” the odd-looking import, or loosens the policy, the test fails.&lt;/li&gt;
&lt;li&gt;Anything that adds a library, worker, canvas or WebGL code, or an external request gets tested as a production build served with the real headers, not just in npm run dev.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Other ways to handle it&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Add 'unsafe-eval' to the policy. It’s the easiest option and the worst one: it weakens the whole app to fix one scene.&lt;/li&gt;
&lt;li&gt;Serve different headers in dev. It catches this class of bug earlier, but the two drift apart easily.&lt;/li&gt;
&lt;li&gt;Test a production build locally with the real headers. That’s what we do now for anything risky.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What the scene is for?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The Pixi scene is a town that your real GitHub work rebuilds. Every verified day drops a crate, and the crates build Lantern District.&lt;/p&gt;

&lt;p&gt;Play: &lt;a href="https://myvigilante.ocix.in/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=settlement-autumn-2026&amp;amp;utm_content=devto-2" rel="noopener noreferrer"&gt;https://myvigilante.ocix.in/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=settlement-autumn-2026&amp;amp;utm_content=devto-2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Have you been caught by a dev/production header mismatch? What broke for you?&lt;/em&gt;&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>webdev</category>
      <category>security</category>
      <category>gamedev</category>
    </item>
    <item>
      <title>I built a browser game where your GitHub pushes will help build a city. Read the Journey and provide your brutally honest feedback</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Thu, 15 Oct 2026 20:04:47 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/i-built-a-browser-game-where-your-github-pushes-will-help-build-a-city-read-the-journey-and-3eei</link>
      <guid>https://dev.to/vishal_vigilante/i-built-a-browser-game-where-your-github-pushes-will-help-build-a-city-read-the-journey-and-3eei</guid>
      <description>&lt;p&gt;So, I was working on a project called Vigilante (by Ocix) for the last 6-7 months. And now people have started looking into it and actually using it. The numbers are still very low but I feel Reddit will help me to reach this project to all the developers out there.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Problem statement -&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For the last year, I have been very serious about building something so that I can survive if AI takes over my job. But whenever I try to build something. I'm just motivated for the initial 5-6 days, and then motivation fades.&lt;/p&gt;

&lt;p&gt;I planned to do something for this first.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How I proceed:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Currently, we are at v7 of the application, and it was not like this from the start.8&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The first version only had the dashboard and Pomodoro + it charged money if I missed a day.&lt;br&gt;
&lt;strong&gt;Response&lt;/strong&gt;: It doesn't even let people try it. Worst UI and bugs. But it helped me to stick around it.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Second version: I improved the UI a bit, but it was still a dashboard; no one liked it.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Till v5, the same story was repeating: I was improving the font, UI, adding unwanted features, and no one was giving a f*.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;In v6, I got the idea of why not to make it a game; this one was completely not my idea at all, but a subtle hint I got from one of my followers. I built it and made it an action game.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Now people are starting to show interest, but a big issue came up as the games are costly. So need to think about the cost also. For some of the fields, I used the image in the background, and that was spoiling the game.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;In v7, I figured out what I needed... I was playing a city builder game, and it was so addictive that I played it day and night for 3 days just to complete all its levels. That's when I got the final idea.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It took me a lot of time, but every time I learned a lot.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What does Vigilante even do?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Till now, I told you the story. Now let me tell you what it does.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Log in with GitHub.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Attach the repo you are going to work on.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a goal&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;and you will enter the game.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Every day, whenever you push your commit to GitHub, the game automatically progresses. It's super fun.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Play: &lt;a href="https://myvigilante.ocix.in/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=settlement-autumn-2026&amp;amp;utm_content=devto-2" rel="noopener noreferrer"&gt;https://myvigilante.ocix.in/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=settlement-autumn-2026&amp;amp;utm_content=devto-2&lt;/a&gt;&lt;/p&gt;

&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F83xcd73ok23y9aboxnvm.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F83xcd73ok23y9aboxnvm.png" alt="Lantern ward homepage screenshot" width="799" height="503"&gt;&lt;/a&gt;&lt;/p&gt;

&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffsnh4m6nsvbmibd5pmbd.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffsnh4m6nsvbmibd5pmbd.png" alt="Lantern district homepage screenshot" width="800" height="502"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>browsergame</category>
      <category>100daysofcode</category>
      <category>consistency</category>
    </item>
    <item>
      <title>I turned GitHub pushes into a town-building game, and kept the honest part</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Tue, 13 Oct 2026 19:30:06 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/i-turned-github-pushes-into-a-town-building-game-and-kept-the-honest-part-5dpd</link>
      <guid>https://dev.to/vishal_vigilante/i-turned-github-pushes-into-a-town-building-game-and-kept-the-honest-part-5dpd</guid>
      <description>&lt;p&gt;Most streak apps trust you. You tap “done,” the number goes up, and nothing checks. On a good day that’s fine. On a bad day, that trust is the problem, because nothing stops you letting yourself off.&lt;/p&gt;

&lt;p&gt;I wanted a streak that checks the one thing I can’t fake: whether code reached GitHub.&lt;/p&gt;

&lt;p&gt;What it checks, and what it doesn’t&lt;/p&gt;

&lt;p&gt;Setup takes about a minute. Connect GitHub, pick a repo, and set a daily commit target.&lt;/p&gt;

&lt;p&gt;GitHub sends push notifications. Vigilante uses the push payload: commit IDs, timestamps and file names. Commit messages are stored only if you turn on sharing them. It never requests your code or diffs.&lt;/p&gt;

&lt;p&gt;Not every push counts. Merge commits, empty commits, and changes to documentation, lock files or repo config alone don’t count. A day needs at least one other changed file. I drew that line on purpose: a day is “did you ship something real,” not “did you touch a file.”&lt;/p&gt;

&lt;p&gt;The honest limit: it can’t tell a thoughtful commit from a typo fix, and it doesn’t try. What it guarantees is that a verified day means code actually reached GitHub.&lt;/p&gt;

&lt;p&gt;Why a game on top&lt;/p&gt;

&lt;p&gt;Every verified day drops a crate with Materials, XP and a chance of a bonus. Streaks raise the reward: ×1.2 at 3 days, ×1.5 at 7 and up.&lt;/p&gt;

&lt;p&gt;You spend Materials on a settlement called Lantern District, which has six buildings with five levels each. Survivors move in as you upgrade. The game is a ledger for the streak: when you miss a day, the salvage pauses and the town goes quiet, so the gap is something you can see. Revival Fluid can repair one missed day.&lt;/p&gt;

&lt;p&gt;Design decisions&lt;br&gt;
Only verified work makes progress. Logging in, tapping, or watching anything grants nothing. That rule is in the code, not just the copy.&lt;br&gt;
Store as little as possible. The app keeps counts. Commit text is kept only with consent. Deleting an account removes its data and keeps one anonymous row of totals.&lt;br&gt;
Try it&lt;/p&gt;

&lt;p&gt;Play: &lt;a href="https://myvigilante.ocix.in/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=settlement-autumn-2026&amp;amp;utm_content=devto-1" rel="noopener noreferrer"&gt;https://myvigilante.ocix.in/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=settlement-autumn-2026&amp;amp;utm_content=devto-1&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you’d rather not connect GitHub yet, the free check-up needs no sign-up: &lt;a href="https://vigilante.ocix.in/audit" rel="noopener noreferrer"&gt;https://vigilante.ocix.in/audit&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What’s the one signal you’d trust in a streak tool? I’d like to know what you’d check first.&lt;br&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzms4v2jckzivdsibqo84.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzms4v2jckzivdsibqo84.png" alt="Lantern Ward map screenshot of the real game" width="800" height="520"&gt;&lt;/a&gt;&lt;/p&gt;

&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhva76fl5dhwlx7aw2cnl.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhva76fl5dhwlx7aw2cnl.png" alt="Lantern District map screenshot of the real game" width="800" height="520"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>webdev</category>
      <category>sideprojects</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Is it relatable to you too?</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Sun, 11 Oct 2026 12:45:54 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/is-it-relatable-to-you-too-9j0</link>
      <guid>https://dev.to/vishal_vigilante/is-it-relatable-to-you-too-9j0</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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzomlnun92qhjathn4s7e.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzomlnun92qhjathn4s7e.png" alt="This image shows a fun side of using AI" width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>aimemes</category>
    </item>
    <item>
      <title>I built a game that only grows when you push real GitHub commits. Roast it?</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Tue, 06 Oct 2026 21:04:09 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/i-built-a-game-that-only-grows-when-you-push-real-github-commits-roast-it-4c55</link>
      <guid>https://dev.to/vishal_vigilante/i-built-a-game-that-only-grows-when-you-push-real-github-commits-roast-it-4c55</guid>
      <description>&lt;p&gt;I'm the solo dev behind this, so take my enthusiasm with salt.&lt;/p&gt;

&lt;p&gt;My problem: I start side projects and quietly drop them around week three. So I built Vigilante, a free game where you connect one repo, and your settlement only grows when you push verified work. No push, no daily supply crate.&lt;/p&gt;

&lt;p&gt;How it works, briefly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You connect a single GitHub repo. It never clones the repo or reads your source, private diffs, or credentials. It only sees push signals.&lt;/li&gt;
&lt;li&gt;Verified pushes earn daily supplies that build six buildings (Lantern House, Salvage Yard, and so on).&lt;/li&gt;
&lt;li&gt;Streaks give bonuses, and there's one "mend a missed day" item a month so a bad day doesn't wreck everything.&lt;/li&gt;
&lt;li&gt;There's a story campaign, plus a daily share card if you want to show your progress.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's free to start. There's also a free GitHub check-up that audits your repo's recent activity with no signup, in case you only want that.&lt;/p&gt;

&lt;p&gt;What I'd like to know:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does "game progress tied to real commits" feel motivating, or gimmicky?&lt;/li&gt;
&lt;li&gt;What would make you stop using it after day 3?&lt;/li&gt;
&lt;li&gt;Is "it doesn't read your code" enough to make you comfortable connecting a repo?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Link: &lt;a href="https://vigilante.ocix.in" rel="noopener noreferrer"&gt;https://vigilante.ocix.in&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Happy to answer anything, including "why does this exist."&lt;/p&gt;

</description>
      <category>github</category>
      <category>productivity</category>
      <category>100daysofcode</category>
      <category>buildinpublic</category>
    </item>
    <item>
      <title>Your Side Project Died Because You Stopped Pushing Code (The 72-Hour Rule)</title>
      <dc:creator>Vishal Pandey</dc:creator>
      <pubDate>Sun, 19 Jul 2026 17:22:22 +0000</pubDate>
      <link>https://dev.to/vishal_vigilante/your-side-project-died-because-you-stopped-pushing-code-the-72-hour-rule-19hf</link>
      <guid>https://dev.to/vishal_vigilante/your-side-project-died-because-you-stopped-pushing-code-the-72-hour-rule-19hf</guid>
      <description>&lt;p&gt;We’ve all been there. &lt;/p&gt;

&lt;p&gt;You get a burst of inspiration late on a Friday night. You purchase the domain, bootstrap the repo, configure your Tailwind variables, and write 800 lines of beautiful, clean code. You go to sleep feeling like a future startup founder.&lt;/p&gt;

&lt;p&gt;Fast forward three weeks: the repository has been silent for 15 days, the domain is sitting unused, and you’re already thinking about a new project.&lt;/p&gt;

&lt;p&gt;Why does this happen? &lt;/p&gt;

&lt;p&gt;It’s not because your idea was bad, and it's not because you ran out of time. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It’s because you broke the 72-Hour Rule of momentum.&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  The Anatomy of a Abandoned Repo
&lt;/h3&gt;

&lt;p&gt;Momentum in software development behaves like a heavy flywheel. It takes immense energy to start spinning, but once it's moving, it carries itself. &lt;/p&gt;

&lt;p&gt;However, developer momentum decays exponentially. The moment you stop pushing code:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Day 1 offline&lt;/strong&gt;: You still remember the context. You know what function to write next.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 2 offline&lt;/strong&gt;: You start losing the mental map. Re-starting requires a minor effort.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 3 offline&lt;/strong&gt;: Cognitive friction sets in. You have to spend 15 minutes reading your own code just to remember what you were doing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 4+ offline&lt;/strong&gt;: The project is dead. The thought of opening the code feels like a chore, so you avoid it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your inactive gaps stretch past 72 hours, the probability of abandoning your side project increases by over 80%.&lt;/p&gt;




&lt;h3&gt;
  
  
  The Audit: Look at the Mirror
&lt;/h3&gt;

&lt;p&gt;Before you promise yourself that "this time will be different," you need to look at your actual baseline. &lt;/p&gt;

&lt;p&gt;A lot of developers think they are consistent because they commit code in massive, 12-hour weekend sessions once every two weeks. But that is the programming equivalent of crash dieting. It doesn't build the habit.&lt;/p&gt;

&lt;p&gt;I wanted a way to visualize my own shipping gaps without looking at the cluttered GitHub heatmap (which hides inactive gaps behind total contribution counts). &lt;/p&gt;

&lt;p&gt;So, I built a free, zero-signup utility called &lt;strong&gt;Vigilante Audit&lt;/strong&gt;. It scans your public GitHub profile and extracts three simple metrics from the last 30 days:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Active Days&lt;/strong&gt;: Out of 30, how many days did you make a meaningful commit?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Longest Streak&lt;/strong&gt;: Your consecutive coding run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Longest Inactive Gap&lt;/strong&gt;: The silent periods where momentum died.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Here is what the dashboard looks like when you run it:&lt;/p&gt;

&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%2Fvigilante.ocix.in%2Fopengraph-image" 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%2Fvigilante.ocix.in%2Fopengraph-image" alt="Vigilante Audit Screenshot" width="1200" height="630"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can run it for free on your username in 5 seconds:&lt;br&gt;
👉 &lt;a href="https://vigilante.ocix.in/audit" rel="noopener noreferrer"&gt;vigilante.ocix.in/audit&lt;/a&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  How to Fix Your Rhythm (The No-Zero-Commit Protocol)
&lt;/h3&gt;

&lt;p&gt;If your audit shows a high "Longest Gap" (e.g., 5+ days), your main focus shouldn't be writing &lt;em&gt;more&lt;/em&gt; code. It should be &lt;strong&gt;narrowing the gaps&lt;/strong&gt;. &lt;/p&gt;

&lt;p&gt;Here is how you do it:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Establish a Daily Minimum Quota&lt;/strong&gt;: Commit to making just &lt;em&gt;one&lt;/em&gt; meaningful line change per day. Even if it's just fixing a typo, renaming a confusing variable, or adding a single unit test. &lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Automate Accountability&lt;/strong&gt;: Don't rely on self-discipline. Use a tool like &lt;a href="https://vigilante.ocix.in" rel="noopener noreferrer"&gt;Vigilante&lt;/a&gt; to link your repository. It automatically monitors your commits via webhooks. If you miss a day, your streak resets, and you face a virtual penalty.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Protect Your Streaks&lt;/strong&gt;: Use streak freezes on days you genuinely need a rest. Rest is fine; silent, unexcused gaps are what kill momentum.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Stop trying to code for 4 hours a day. Start by coding for 10 minutes a day, every single day.&lt;/p&gt;

&lt;p&gt;Go run your audit, see your reality, and drop your score in the comments below. Let's see who has the lowest "inactive gap" this month!&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
