Dev Notes

Daily journal of what I built, learned and shipped. Two-minute entries. Public because writing in the open sharpens thinking.

Structure

2026/
  07/
    2026-07-16.md
    2026-07-17.md
    ...

One file per day. Format is loose but usually:

• What I did — 3 bullets max
• Learned — one non-obvious thing worth remembering
• Tomorrow — one thing to try next

Daily flow

./new.sh              # creates today's note in the right folder
# edit, save, then:
git add . && git commit -m "note: $(date +%F)" && git push

Two minutes. Every day. The habit compounds.

Why

• Forces a daily reflection I'd otherwise skip
• Searchable log of solutions I found the hard way
• Public receipts of consistent work
• Bonus: keeps my GitHub contribution graph honest and green

Rules I follow

1. Never fake a date. If I skipped a day, I skipped a day
2. No client-sensitive details. Anonymize projects, redact keys
3. Prefer specifics over generic advice. "Fixed CSP so Stripe iframe loaded" beats "learned about CSP"
4. Ship even if the note is short. Two lines beats zero lines

---

Kept by Nazir Abbas. Web Developer and SEO Specialist for luxury brands.