Coding tracker
A GitHub contribution graph counts commits, pull requests and issues. Reading docs, working through exercises, debugging locally and studying system design never appear. This habit uses the same kind of day grid, filled from what you report, so an hour of practice counts whether it ended in a commit or not.
Set it up
- Habit
- Code daily
- Goal
- 60 minutes per day
- Schedule
- Every day
- Color
- Green
Pick a target
- Starting out30 minutes
One kata, one tutorial section or one small bug fix.
- Steady60 minutes
The daily hour that 100 Days of Code is commonly described with.
- Stretch2 hours
Enough for real progress on a side project after work.
When to schedule it
A 100-day challenge means every day, and that's the schedule here. If you're learning outside a job, Monday to Saturday with Sunday off is gentler. Developers who code all day at work should count only study or side-project time, or the grid fills itself and stops telling you anything.
What to say in ChatGPT
What helps
- Write the next step in a comment before you stop. Opening the editor tomorrow is easier when you know the first thing to type.
- Reading docs and chasing a stubborn bug are practice too, so log that time.
- For interview prep, problems solved can be its own habit. A target of 2 problems a day says more than minutes.
Questions
Does it read my GitHub activity?
No. It doesn't connect to GitHub, GitLab, your editor or a time tracker like WakaTime. You tell ChatGPT the minutes.
Can I use it for 100 Days of Code?
Yes. Create a 60-minute daily habit and ask for your streak as you go. The challenge, as commonly described, also asks you to post progress publicly; that part happens outside the app.
Similar habits
- Typing tracker10 minutes per day · Weekdays
- Deep work tracker2 hours per day · Weekdays
- Online course tracker2 lessons per day · Mon, Wed, Sat
- Pomodoro tracker8 sessions per day · Weekdays