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

I would suggest taking copius notes and using writing documentation to get over the switch.

For example, when I get started on a project, I normally sit down at my computer and surf the internet for maybe 20 minutes and play around in the command line. This "down-time" helps me get into the flow of things. Plus I normally try to avoid tight-deadlines so I don't really care if I spend 20 minutes dinking around on Hacker News.

If you have a similar work-pattern, maybe those 20 minutes could be spent instead reviewing a README.md or working on a Trello board, or adding new links to an internal wiki you've set up for the project.

I've found that touching the documentation that I've created really helps me snap back into a project since I can see exactly where I left off. And if I don't know what to do, I work on planning out the project.

Also, if all of a sudden I have a great idea of what to do, I'll spend half and hour or so making files and directories and writing the code entirely in comments. Then, when I come back to the project, it's only a matter of replacing the comments with real code.



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

Search: