DevRecall

A while back I was going through a stretch of interviews, and noticed something annoying: without daily practice, my own skills were getting rusty. Not dramatically - just enough that I'd hesitate on things I used to know cold.

The bigger problem wasn't the rust itself. It was prep. Before every interview I'd re-recap the same fundamentals - googling the same concepts, asking GPT the same questions I'd already asked three months earlier. Nothing I'd learned the first time was easy to find again. It was scattered across docs, bookmarks, half-finished notes, gone.

So I started building something for myself: a place to keep what I learn organized enough that I could actually come back to it fast and targeted, instead of researching it from scratch on every interview cycle.

That's how DevRecall started. No roadmap, no plan to launch anything - just a tool I wanted to exist.

Somewhere in the process I got pulled in further than I expected. Once the notes were structured, a bigger shape showed up underneath: not just "where do I keep what I learn", but rather "how do I know what to learn next, and how does that connect to where I actually want to go career-wise". That's the direction it has been growing in since - less a notebook, more as an ecosystem around how developers organize knowledge and grow professionally.

Still early, still solo, still free (devrecall.com). I will be posting more here as I go - technical stuff, product decisions, the occasional "why did I build it this way".

For now: if you've ever caught yourself re-googling the same interview topic for the third time in six months, I'd love to hear how you deal with that - genuinely curious what other people's systems look like.