Writing
Vigilante Blog: Coding Streaks, Habits & Shipping
Honest writing on developer consistency, shipping habits, and building products that actually survive past the first week.

Vigilante guide7 min read
The 72-hour rule: a restart checklist for a quiet side project
Use a three-day gap as a reminder to leave a clear next step, reduce the cost of returning and finish one small, useful change.
productivitywebdevshowdev
Read article

Vigilante guide7 min read
An accountability routine that helps you ship a side project
Define an observable result, keep a small evidence record and use a weekly review to adjust the plan without turning a streak into pressure.
developerproductivitybuildinpublic
Read article
Also on dev.to & X (Twitter)