DevDiary: I Finally Finished My GitHub Coding Journal App 🌱

Submitted for the GitHub Finish-Up-A-Thon Challenge

---

What I Built

DevDiary — a personal developer journal that connects to your GitHub activity and lets you annotate your coding journey, commit by commit.

Every developer knows the feeling: you push a commit, close the laptop, and two weeks later you have no idea what you were thinking. DevDiary fixes that. It pulls your real GitHub commits and gives you a space to write why you made a change, how you were feeling, and what you learned.

---

The "Before" — What I Started With

About 3 months ago, I started building a GitHub stats dashboard. I had a half-baked idea: what if I could see my commit history with personal context attached?

What I had:

• A single index.html with hardcoded fake commit data
• A textarea that saved nothing
• Zero styling (just browser defaults)
• No GitHub API connection
• No way to retrieve or view past entries

It sat untouched in a private repo, committed exactly once: "initial messy code".

Screenshot of the before state:

---

The "After" — What I Shipped

DevDiary is now a fully working app with:

---

How GitHub Copilot Helped Me Finish

This is the honest part. I'd looked at this abandoned project twice before and closed the file both times. Here's what Copilot actually changed:

1. Breaking through the blank-page paralysis

When I reopened the old file, Copilot immediately suggested auto-completions for the GitHub API fetch logic I'd left half-written. Just seeing those suggestions made the project feel resumable rather than abandoned.

2. The localStorage persistence I never got around to

The original idea always included saving entries, but I kept putting it off because it felt tedious. Copilot generated the full save/load/delete pattern — including the try/catch for JSON parsing edge cases — in seconds. That was the feature that kept blocking me.

3. Mood and tag UI boilerplate

I had mood tracking in my original design notes but never implemented it. Copilot's autocomplete on the mood state arrays and toggle functions made what felt like "another hour of work" into about 5 minutes. That freed me to focus on the parts that actually needed thought.

4. CSS micro-interactions

I described what I wanted (a subtle done-dot indicator on journaled commits, toast notifications, staggered entrance animation) and Copilot filled in the CSS keyframes and transition properties. Small details, big difference in feel.

The honest summary: Copilot didn't write the app for me. It handled the remembering — all the small implementation details I already knew how to do but couldn't hold in my head at once. That's what let me go from "this feels like a mountain" to "I can see the finish line."

---

Technical Stack

• React (functional components + hooks)
• GitHub Public Events API (no auth required for public data)
• localStorage for persistence
• CSS-in-JS (no external CSS framework — all custom)
• Google Fonts — Instrument Serif + DM Mono
• Deployed on GitHub Pages / Vercel

---

What I Learned

1. Abandoned projects aren't failed projects — they're just unfinished ones
2. The biggest blocker is usually one specific feature you keep avoiding (for me: persistence)
3. AI tools like Copilot are best at reducing the activation energy to start, not replacing thinking
4. Shipping something imperfect beats polishing something forever

---

What's Next

• OAuth login to access private repos
• Weekly "developer retrospective" view grouped by date
• Export journal as Markdown
• Streak tracking for consistent journaling

---

Built with GitHub Copilot for the GitHub Finish-Up-A-Thon Challenge · May 2026