I Procrastinate
Procrastination is typically perceived as a bad thing. After all, when someone puts something off until the last possible moment, then they are lazy, right? Well, this may be true for some, but not all of us procrastinators. I put off things until the last minute because that means I can do other things now. Where I work, there is a constant barrage of work to be done. "Emergencies" pop up on a daily basis that require immediate IT attention. All of these urgent requests inevitably put off other work. So, some of my procrastination isn't my own choice. Still, given any two tasks, I try to weigh when it's due related to how long I think it'll take me to get it done plus 33%.
I think that I write better code when I'm in rush mode. I know this seems very counter-intuitive, but hear me out. By waiting until the last minute, and then working it out until it's done, you:
- spend less time on that one project. When a project drags out, you inevitably take time re-aquatinting yourself with your former code. That's wasted time in my book.
- get to complete the task in one mindset. Code is more consistent throughout the program. I'm less likely to do something a different way than I did 5 minutes ago versus 5 weeks ago. I think this makes for a higher quality end product.
- could have learned a better way to do the task that I would be doing. Something that would have taken me 2 days to complete may now take half a day because of my new found knowledge. Research does pay off!
- get more done. Since the total time dedicated to task is smaller, you can cram more into your 8 hours a day.
Nothing is 100% good. Procrastination does bring it's own set of problems.
- Stress! Working up to a deadline can be stressful. There are people and dollars counting on you making your deadline. That thought is stressful enough, but those who are waiting will push their stress on you. Double stress!
- You get things done faster. So, what happens when people realize you can churn out huge things in a very brief period of time? They expect it all of the time of course! This isn't normally a problem until they expect you to work as fast on an emergency as you did on a project that you had in the pipeline for a month. Part of what makes the burst of work so successful is the planning that led up to that. Code meditation if you will.
- Managing 2+ projects that come due at the exact same time. I try to make sure that I get one task totally out of the way until I move on to another. The problem lies in the go-live date. There is always some amount of babying a project needs when it's going live. This isn't necessary a procrastination problem until you miss a target time.
Procrastination isn't bad until you have problems meeting deadlines. There are people who don't procrastinate and have problems keeping a timeline, so it's not a bullet point issue Please keep in mind that procrastination != half-assed work. I have a standard of quality that I won't compromise no matter what is on my plate. Nothing from me will go live until it's right. Period.
Comments(0)