Developer writing

Make the next
step clearer.

Practical writing about returning to a project, choosing useful targets and reading activity without confusing it with ability.

· Vishal Pandey

How to set a daily coding target you'll actually keep

Most daily coding goals fail because they're sized for your best day. How to set a commit target you'll still hit on your worst one, with examples.

Read the article ↗

· Vishal Pandey

Designing a game economy that money can't buy

How we designed a habit game where money, ads and logging in can never buy progress, with the actual reward numbers and the trade-offs behind them.

Read the article ↗

· Vishal Pandey

Charging in rupees and dollars from day one: how we pick the currency

How we pick between ₹ and $ at checkout for an Indian developer tool: explicit choice, IP country, time zone, and a safe default, with the code and the mistakes to avoid.

Read the article ↗

· Vishal Pandey

Habit trackers, partners, building in public, or a game? Accountability systems for developers, compared

Habit trackers, accountability partners, building in public, or a game? An honest comparison of accountability systems for developers, including the weaknesses of the one we build.

Read the article ↗

· Vishal Pandey

Streaks without burnout: how to keep a daily habit that doesn't own you

Streaks work until they start working against you. How to keep a daily coding habit without burnout: floors, planned breaks, repairs, and why a missed day shouldn't erase anything.

Read the article ↗

Read on the Vigilante blog

The Vigilante blog has complete guides to restarting a quiet side project and building an accountability routine. Each guide focuses on a specific decision you can try in your own project.

Start with the evidence

Activity is a useful signal when you know what it measures. A public graph can show gaps but miss private work; a commit count can show changes but cannot judge their value. Use the free GitHub tools as a starting point for questions about your routine.