DEV JOURNAL
A personal changelog for developers — a private space to log every bug you fixed and how you fixed it, so the knowledge never gets lost.
The problem
As a junior developer, I kept solving bugs and problems, but the solutions lived only in my memory — or scattered across random notes. When I hit a similar issue weeks later, I had no reliable place to look back at how I solved it the first time
The solution
I designed the concept and UI direction myself, generated the interface using Claude Design from screenshots I described and refined, then built the app using Claude Code with shadcn/ui for clean, consistent components. Each entry follows a simple structure — Problem, Solution, What I Learned, and an optional Improvement Idea — tagged with the tech stack involved, so entries are easy to search and filter later.
My contribution
- Product Concept
- UI Direction
- AI-Paired Development
- Tagging System
- Search and Filter Logic
Challenges
This was a straightforward CRUD app, so no major technical challenges came up - the focus was more on shaping the idea and structuring the entry format in a way that would actually be useful to revisit later.
Results
- I use it daily now to log real bugs and solutions as I run into them
- The first real entry - a FIFO-logic bug in a debt-tracking system — is already logged and searchable