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

Same; some exceptions are when I write things down to turn into a presentation or blog post, or if it's like notes / actions from a meeting.

That said, for me writing things down does help me organize my thought process.

Another thing that I do think is beneficial but directly work-related is writing ADR's (https://github.com/joelparkerhenderson/architecture_decision... basically technical documentation, one file per decision (architectural, language, library, etc); I can start those as a stream-of-consciousness ramble, then add some research / alternatives, and finally do some formatting and commit it into my project's repository.

From there it'll take on a life of its own, I'll reconsider things down the line (most recently, replacing Reach with React Router because the former is end-of-life and in retrospect had some quirks I ran into). My hope is that when more people join my project or take over, they'll be able to read it and understand where things have come from, and then add their own ideas to it.

Of course, they'll likely opt to just ignore it entirely because tl;dr show me the code.



Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

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

Search: