A public log of small things I build and learn in Python, one day at a time. The goal isn't a green streak for its own sake β it's the habit of writing real code consistently, and having something to show for it.
Started: 2026-06-01
| Day | Date | Topic | What I did |
|---|---|---|---|
| 001 | 2026-06-01 | Strings / Logic | FizzBuzz, the clean way |
| 002 | 2026-06-02 | Strings | Palindrome checker |
days/
day-001/
README.md <- what I learned / the problem
solution.py <- the code
day-002/
...
Each day lives in its own folder so the history stays readable.
To avoid "what do I even do today?" paralysis, I rotate through:
- Mon / Wed / Fri β a small coding challenge (algorithms, string/array problems)
- Tue / Thu β a concept I'm learning, with a tiny runnable example
- Sat / Sun β a piece of a slightly bigger mini-project
This is a guideline, not a rule. Showing up matters more than the schedule.
python new_day.py "Topic name here"This creates the next days/day-XXX/ folder with a starter README.md and
solution.py so I can jump straight into the actual work.
Consistency over intensity. Real code over filler commits.