Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As a developer, very often I'm locked into a problem (algorithms, trigonometry, "stuff you'd think you'd know by now, dumbass", etc.)

The only way for me to get out of it is doodling it down: write the keywords, link them, circle them around, draw the thing, depict it in 3D, flow chart it, boxes, structures, swimlanes, whatever.

It's like mansplaining it to my brain.

Works 11/10 times.

Always have a clean pad with a pen handy.



> Always have a clean pad with a pen handy.

Bought a Remarkable a couple of years ago, never looked back. I've written (doodled) 1000 virtual pages since then. Its permanent place is right in front of my keyword.

I also use it during Zoom calls to take notes and remember stuff. So much better than relying on my head alone.


Same here. Writing/sketching is thinking. By the time, I’m actually typing code, I know exactly what to expect. Having that clarity is quite empowering and ascertains control.


> Always have a clean pad with a pen handy.

This is why I love my Remarkable


Same with my Boox. It has the added advantage of reducing desk clutter (no more drawer full of notes!) and letting me handwrite notes, which always seems to help me remember things better.


I started writing down keywords a few months back and I honestly should have started much sooner.


What do you mean by writing down keywords? Can you walk me through an example? And how is that helping you? I’m curious to try it out.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: