I'm a big fan of Todo comments in the codebase. Especially recently, since I've been working on the browser project. When I come across something that I think would be nice to have or don't know how to make it work right now, I use the // Todo: comment with usually a line explaining what needs to be done in the future. It helps me get unstuck almost instantly. Sometimes the best way to solve a problem is to leave it alone.
Although recently I've been noticing something. A few times, it's turned out that I did not even need to solve the problem in the first place at which point I simply delete the comment. Or even better, the problem gets solved on it's own as I build ahead. These are rare, but quite satisfying.
The reason I decided to mention is that, it's helped me get unstuck quite quickly by ignoring the problem temporarily. Early on during a project or when working on something hard, this helps build momentum. As I was working on the browser in a language I had only picked up, I think a few weeks ago, I'll take all the help I can get, to move ahead ever so slightly. It's key to avoid projects being dropped before they ever see daylight. I think.
This is especially true, as once I get the compression and caching done, the next task is to draw the screen. I'm looking forward to this quite a bit. All I need to ensure is I get to that stage.