Hacker Newsnew | past | comments | ask | show | jobs | submit | seren1's favoriteslogin

Some additions to this I find useful:

> - Use the 15 minute rule to get started

I like to take this a step further, and I think I read it in a Brian Tracey book once. If I have a list of things that need doing that I am not especially excited about, I'll go through them doing five minutes max on each. This normally sufficiently unsticks each, but if it doesn't, then do a round of 10m on each.

> - Leave a currently solved code part partially done or leave a compile issue on the area you were working on

One way I handle this is by forcing myself to keep and update a "Next Work" list (in an outliner) that keeps a very current todo list for each project. Generally I'll update it each morning and break down the immediate next work into tasks that only take a minute or two to get that momentum going

> - Motivators and triggers

I'm only slightly ashamed to admit I make heavy use of:

https://www.youtube.com/watch?v=A6OwnNe9nMU (usually while walking, or very very first thing in the morning -- I downloaded the audio only)

https://www.youtube.com/watch?v=AjZ0KbJcav0

https://www.youtube.com/watch?v=OmkNKEHC8Pg

https://www.youtube.com/watch?v=PjP9r-HU4fk

and Apple's Think Different advert

I also really like writing out the answer to "What'll be different in a week's/month's time due to what you're about to do?"

> - Start the day right, work on something simple or one check in for instance before reddit/HN/news or distractions

Phone goes on airplane mode overnight, and comes out of airplane mode once I've completed my morning ritual, which takes about an hour and a half.


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

Search: