Hacker News new | past | comments | ask | show | jobs | submit login

Same, the legwork of "working hard" on a problem for me these days is just making sure I have all the information I need to stew over. I write up a factfinding doc of points in the codebase that I think are relevant, any context that's relevant, and symptoms of the bug. I never used to write it down but I work across a bunch of projects now so I can sometimes have the bug de-prioritised in my brain.



Writing something down, even if not for long term storage, is great. It feels like freeing up RAM that can be used for something else.

But definitely there needs to be preparatory work before you need to let everything stew. Get all the facts, internalise them, and move on.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: