What you are describing is optimal task scheduling. Procrastination is what you do with the time that you're not spending on your task.

I agree that there are a great many number for whom "time crunch" and the pressure of an imminent deadline help to produce a superior outcome. For those that know themselves well enough, I agree absolutely simply set your own start time, and don't built yourself up over "procrastination." You're simply scheduling your own work.

However, there is also another subset of people that put off starting projects and work until the last minute, and don't function well under pressure. Many produce inferior work; some break down.

Ultimately, the key is self-awareness and self-acceptance. Identify what kind of person you are, in terms of work habits and conditions, and be completely honest with yourself. Then don't feel guilty or silly or whatever other negative attitude people want to attach for structuring your own production schedule according to your strengths and superior functioning.

Though this is a good point, you are not really procrastinating at that point. Procrastination almost always implies being late to your due dates. You are just very good at calculating time you need to do something. I think you can consider yourself a procrastinator when you are habitually being late and making others be late because of your behavior (laziness or whatever it might be).

This is a great point.

I think what real trick or hack to take away here is psychological instead of code: don't feel bad about it.

Yes, that's exactly what I took away from the article. I do think severe laziness day-to-day is definitely detrimental. But being idle, resting and reflecting is important to "reset" yourself and preventing burnout.

Our society seems to condone any type of idleness, especially in the technology industry. This view needs to be changed at an institutional level. In every talk I've heard, people say one of the most important things working and running a startup is to maintain a healthy work-life balance. Instead of just acknowledging this concept, we need to actually implement it.

condone means to allow; I think you meant condemn

Lol, yeah *condemn. Although condone is to allow reluctantly. And no one's going to disallow me of my laziness when I want it.

This happened to me recently. I was thinking of spending a lot of time perfecting a feature when my boss told me not to waste too much time designing it as they'd change their minds in a few weeks anyway and then all my effort would go to waste.

He was sort of right but the end result is that the codebase is now a mess.

thats a good point in the short term sense.

but what about the long term procrastinators? how does your theory fit into the aspect of long term goals? Say I want to switch careers and become an actor or something. Obviously I'd want to begin as early as possible and not wait until "there's optimal time you know you need left" because you obviously don't know the optimal time to begin a long term goal.

Just a thought.

This is not procrastination, this is late-binding ;)

I need fewer developers with that attitude, I want people who can get stuff done, but by their nature, put it off. There will always be those that procrastinate in a team and there will, thankfully, always be those that just get it down. The reason why your technique seems to work for you is more likely because are picking up your slack.

I wholeheartedly advocate you getting off my team :)

You have no idea of the context from which he is making that statement.

You have no idea of his technical competence or his efficacy with regard to completing tasks and shipping products.

You have very little legitimate basis from which to extrapolate that he/she would _ever_ want to be a member _your_ team in the first place.

Judging by the implicated narrative you seem to be espousing, I'm sure _I_ wouldn't want to be a part of your team.

Even disregarding the fact that you mistakenly omitted the word "others" your haughty comment could not have been better phrased to portray a small-minded project manager with little understanding or empathy for those that _apparently_ work under you.

The assumption that any programmer commenting here is equivalent to a 'member of your team' is little and less based in reality, and much and more based in your own flawed interpretation of it.

I've worked with developers who "just got it done", I would often spend months afterwards fixing up their messy code.