Coding Kata Log
Track coding problems solved with platform, language and time.
Overview
The coding kata log is a focused journal for tracking every algorithm problem, exercise, or interview prep question you work through. Each entry captures the date, problem name, platform, difficulty, language used, time spent, and an optional notes field for the approach, gotchas, and follow-up reading. Over weeks and months that record turns into a personal study guide showing which patterns you have practised, which languages you reach for most, and which difficulty levels still slow you down.
Beyond plain bookkeeping, the log surfaces totals at the top of the list: katas solved, total minutes invested, problems completed in the current week, and a day-streak counter that resets when you skip practice. Those stats reward consistency the same way a habit tracker does, while the notes field doubles as a long-term reference you can grep later when a similar problem appears in an interview or code review.
How it works
Add an entry by filling in the date, problem title, and any optional metadata such as platform (LeetCode, Codewars, Exercism, Advent of Code), difficulty label, language, and minutes invested. The notes textarea handles up to two thousand characters, so it comfortably holds an outline of the algorithm, a complexity analysis, edge cases you missed, or a link-free reminder of the trick that unlocked the solution.
Once entries exist, the dashboard recomputes the totals on every save and shows the rolling seven-day window plus the current consecutive-day streak. A sample-kata loader inserts a curated problem dated today, which is handy for verifying the layout before you start logging your real work.
Examples
- Daily interview prep: Log "Two Sum" on LeetCode, Easy, Python, 12 minutes, with notes describing the hash-map approach and why brute force times out.
- Pattern study: Log "LRU Cache" on LeetCode, Medium, C#, 35 minutes, with notes contrasting linked-list plus dictionary against an ordered dictionary.
- Language learning: Re-solve "Valid Parentheses" in Rust to practise borrow-checking, recording the slower 25-minute time honestly so future-you can see the learning curve.
- Advent of Code recap: Capture a Day 14 puzzle on AoC, Hard, TypeScript, 90 minutes, with takeaways about cycle detection.
FAQ
Does the streak counter require a kata every single day?
Yes. The streak counts back from today and stops at the first missing day, so logging on the same calendar date keeps the streak alive even if you only manage one short problem.
Can I track platforms beyond LeetCode?
The platform field is free text. Exercism, HackerRank, Codeforces, Project Euler, AoC, and internal company drills all work without configuration.
Is the time field required?
No. Leave minutes at zero if you do not time yourself, and it will be excluded from the total time stat.
How long can my notes be?
The notes textarea accepts up to two thousand characters, enough for a paragraph or two summarising the algorithm and any follow-ups.
Can I delete a mistaken entry?
Yes. Each row has a trash button that removes that kata immediately.