Live data from Hacker News

At the End of a Procrastinated Day

removed.posterous.com

41–50 of 113 posts

Re: At the End of a Procrastinated Day

#41
Something that helps when acknowledging I´m procrastinating is to fast forward to the future and think: How will I feel after I´ve wasted a perfectly good day doing nothing, when the day before I told myself I was so going to do all of those things?

Getting myself out of the present, in a nutshell.

Re: At the End of a Procrastinated Day

#42
Procrastination shouldn't just suck, it should be unacceptable. Don't tolerate it. No excuses. Not even if it's "just today".

Close everything! Ask yourself why you're not enjoying your work today. If you're not enjoying what you're doing, do something about it. Either finish it, so you can move on to something you enjoy. If that's not the case, talk to someone about how boring your stuff is and fix this problem.

DON'T ACCEPT PROCRASTINATION!

Re: At the End of a Procrastinated Day

#43

I feel you. I've been procrastinating a project for 3 years already (yes 3 years). I write code maybe half of one day each week. The rest of the time I do as you describe. I'm so ashamed of it I tell no one. Glad to have quite a bit of savings.

I don't mean to come off as a dick, but switch projects. I procrastinated for a month straight on something, as soon as I dropped the project the code flowed.

I did twice already. Both times because competitors beat me due to my chronic procrastination.

Re: At the End of a Procrastinated Day

#44
The Hemingway Trick: Stop in the middle. Never stop working at the natural barriers. They next time you start working, the barrier will be the first thing you encounter, and you won't have the momentum to overcome it. Try to stop writing mid-chapter, or mid-sentence (or mid function). Know how to finish, but stop working. The next time you start, you know exactly what needs to be done. There will even be the urge to start working to finish the unfinished.

Nearing the end of a unproductive day, accept that the day was not productive, start on what you will work on tomorrow, do a little, and stop in the middle.

Re: At the End of a Procrastinated Day

#45

my tactic: if you are burned out on coding, stop and do something else positive: * go for a run * do an errand that has to be done anyway * balance your checkbook This gets your mind on something else which is probably the problem - we aren't meant to stare at a screen doing exactly the same things over and over for 8 hours. And remember, you are not alone in this. No depression allowed - you are not weak, you are hu…

Doesn´t work for me. After I get my mind off the issue at hand and do an errand, when I come back I´m at the same position I was before. Sometimes even worse, because of the context switching.

Re: At the End of a Procrastinated Day

#46
post #44

The Hemingway Trick: Stop in the middle. Never stop working at the natural barriers. They next time you start working, the barrier will be the first thing you encounter, and you won't have the momentum to overcome it. Try to stop writing mid-chapter, or mid-sentence (or mid function). Know how to finish, but stop working. The next time you start, you know exactly what needs to be done. There will even be the urge to…

This works extremely well for me. I wouldn't recommend stopping mid-sentence but leaving an implementation incomplete (eg. just have to fill out another method and everything fits together) allows me to start the next day running.

Re: At the End of a Procrastinated Day

#47
post #6

For me, procrastination always come from a lack of having a digestible plan of attack. When you find yourself procrastinating, figure out a single next step for your project, one single feature, or one single task in that feature that needs to be done. If you know what your next step in the project is, you'll have this urge to jump back in and do that task. If you can't find that task, then you need to step back and…

This sounds a lot like the advice given in Zen and the Art of Motorcycle Maintenance on how to overcome writer's block. In the book, the narrator is teaching a writing course, and a student says she doesn't know what to write about. So he suggests that she pick a building, but not just a building, start with a single brick and describe that, then the next one and so on. She ends up writing voluminously.

This advice of breaking down the problem to its smallest domain of attack has been around for a long time.

Re: At the End of a Procrastinated Day

#48
post #11
post #10

I find procrastination is a symptom, not the actual problem. The very root of the problem is that I'm either faced with something I just don't want to do or can see that the NEXT thing is something I really don't want to face. It usually means I need to do some introspection.

Yes, this. I have no problem working when I'm excited about the work. If I'm not excited, then it's usually some extra-curricular problem or the work is not the kind of work that inspires me.

Sometimes you just have to work on less interesting things, there's no way around it.

Re: At the End of a Procrastinated Day

#49
I think procrastinating is one of the most obvious symptoms of low EQ. You are just to emotional, you feel extremely unmotivated because you do not want to do what you need to do(studying etc). You just can not overcome your emotions and you do what ever your emotions want you to do, which is procrastinating and feeling better for this moment of time.

Emotions do not care about what you will feel in the future, they just care about what you feel right now. Procrastinating makes people happy. It is some type of addiction. You just can not ignore your emotions, and you do what makes you happy right now which is procrastinating.

Post reply on HN