- Thanks received
- 454
Don't do any work until a few days before the deadline. That way, you'll tulip yourself and work your ass off to complete in fear of being found out, terminated and sued.
Works for me.
WHS
Don't do any work until a few days before the deadline. That way, you'll tulip yourself and work your ass off to complete in fear of being found out, terminated and sued.
Works for me.
Don't do any work until a few days before the deadline. That way, you'll tulip yourself and work your ass off to complete in fear of being found out, terminated and sued.
Works for me.
That is my normal M.O. but I am being micro managed by an on site customer (of my clients) rep.I thought I was the only one doing that. Seems to be standard practice!
Don't do any work until a few days before the deadline. That way, you'll tulip yourself and work your ass off to complete in fear of being found out, terminated and sued.
Works for me.
That's how I often work as well - in this case, however, there doesn't seem to be a specific or even made up dead-line or goal - it could be that that's killing it for me - I don't see the end of it, when it gets 'done'.
In software, obviously nothing ever really is done, but you can only progress by setting up goals and sprints and stuff, where I am at the moment, there's no such pressure, thus I feel no urge to do anything....
set yourself tight deadlines. Meet them and take the rest of the week off for plan b then deliver them at the end of the week.
nextDon't do any work until a few days before the deadline. That way, you'll tulip yourself and work your ass off to complete in fear of being found out, terminated and sued.
Works for me.
I thought I was the only one doing that. Seems to be standard practice!
WMFS
But I wouldn't recommend for every contract (just the dead-end ones)
I only just got round to this thread as I've spent all morning catching up on Frozen Planet, err I mean on mute on a lengthy boring conf call.. it's almost lunchtime soon 