Nothing like waiting until the last minute...
-
Now you know who the snakes are.
A snake?! A snake!! A snake!! J
"I am the Lorax. I speak for the trees."
-
Two years ago I started receiving printed emails on my desk. Burried in these emails were the requirements for a particular part of this project. Over the following months, I pieced them all together and created a gigantic spreadsheet summary. This went to my boss. He confirmed them. It then went to the end-users. They confirmed them. Fast-forward to today. September 9 2003. We freeze in 2 days. Count 'em. 2. Now, all of a sudden, someone has noticed my specs chart and explained that parts of it are wrong. I have a list of things left to do - none of which involve re-engineering the analysis for the eleventh time. And all I can say is... ... badger, badger, badger, badger, badger, badger, badger, badger, mushroom! mushroom! J
"I am the Lorax. I speak for the trees."
Jamie Hale wrote: someone has noticed my specs chart and explained that parts of it are wrong f 'em. if they're so smart, why weren't they paying attention two years ago? FWIW, i've got the same thing going on here. "yeah, we really want it to do X!" so i implement X. three months later they come to me and ask "why does it do X?" when i say "because you asked me to make it do that", they tell me that maybe i should "take that out". F. U. A hole. Jamie Hale wrote: badger, badger, badger, badger i've been singing that song for 12 hours straight. :) ImgSource | CheeseWeasle
-
A snake?! A snake!! A snake!! J
"I am the Lorax. I speak for the trees."
Run Away! Run Away! *cough* Monty Python *cough* My code isn't buggy. Those are all fleatures.
-
Jamie Hale wrote: someone has noticed my specs chart and explained that parts of it are wrong f 'em. if they're so smart, why weren't they paying attention two years ago? FWIW, i've got the same thing going on here. "yeah, we really want it to do X!" so i implement X. three months later they come to me and ask "why does it do X?" when i say "because you asked me to make it do that", they tell me that maybe i should "take that out". F. U. A hole. Jamie Hale wrote: badger, badger, badger, badger i've been singing that song for 12 hours straight. :) ImgSource | CheeseWeasle
Chris Losinger wrote: when i say "because you asked me to make it do that", they tell me that maybe i should "take that out". F. U. A hole. I've got 2 weeks left in the contract, and I'm this close (**puts index finger and thumb together**) to explaining to them exactly what they can do with their changes. Thankfully I don't really have a deliverable. J J
"I am the Lorax. I speak for the trees."
-
Two years ago I started receiving printed emails on my desk. Burried in these emails were the requirements for a particular part of this project. Over the following months, I pieced them all together and created a gigantic spreadsheet summary. This went to my boss. He confirmed them. It then went to the end-users. They confirmed them. Fast-forward to today. September 9 2003. We freeze in 2 days. Count 'em. 2. Now, all of a sudden, someone has noticed my specs chart and explained that parts of it are wrong. I have a list of things left to do - none of which involve re-engineering the analysis for the eleventh time. And all I can say is... ... badger, badger, badger, badger, badger, badger, badger, badger, mushroom! mushroom! J
"I am the Lorax. I speak for the trees."
Hey, you had a specs chart... (This is liable to turn into the Monty Python 'When I were a lad...' sketch...)
-
Two years ago I started receiving printed emails on my desk. Burried in these emails were the requirements for a particular part of this project. Over the following months, I pieced them all together and created a gigantic spreadsheet summary. This went to my boss. He confirmed them. It then went to the end-users. They confirmed them. Fast-forward to today. September 9 2003. We freeze in 2 days. Count 'em. 2. Now, all of a sudden, someone has noticed my specs chart and explained that parts of it are wrong. I have a list of things left to do - none of which involve re-engineering the analysis for the eleventh time. And all I can say is... ... badger, badger, badger, badger, badger, badger, badger, badger, mushroom! mushroom! J
"I am the Lorax. I speak for the trees."
Read my sig (the last part) - it says it all... ¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned
-
Run Away! Run Away! *cough* Monty Python *cough* My code isn't buggy. Those are all fleatures.
Awimsatt wrote: Those are all fleatures. Your feature-full code is interfering with your keyboard driver. J
"I am the Lorax. I speak for the trees."
-
Two years ago I started receiving printed emails on my desk. Burried in these emails were the requirements for a particular part of this project. Over the following months, I pieced them all together and created a gigantic spreadsheet summary. This went to my boss. He confirmed them. It then went to the end-users. They confirmed them. Fast-forward to today. September 9 2003. We freeze in 2 days. Count 'em. 2. Now, all of a sudden, someone has noticed my specs chart and explained that parts of it are wrong. I have a list of things left to do - none of which involve re-engineering the analysis for the eleventh time. And all I can say is... ... badger, badger, badger, badger, badger, badger, badger, badger, mushroom! mushroom! J
"I am the Lorax. I speak for the trees."
I had experiences like this at my last company. We were a fairly formal shop in that we created requirements docs, spec docs, and then started coding. For each document, we had a meeting to go along with it. Attendees would be development, marketing, support, training, QA, and maybe sales. Everyone would get their two cents in before it was all over. The final document would be mailed out. When development was near over and various folks would be "testing" it, they would ask why it does (or it should do) this or that. Referring them back to the two documents meant nothing. It's the here and now that counts!
Five birds are sitting on a fence. Three of them decide to fly off. How many are left?
-
I had experiences like this at my last company. We were a fairly formal shop in that we created requirements docs, spec docs, and then started coding. For each document, we had a meeting to go along with it. Attendees would be development, marketing, support, training, QA, and maybe sales. Everyone would get their two cents in before it was all over. The final document would be mailed out. When development was near over and various folks would be "testing" it, they would ask why it does (or it should do) this or that. Referring them back to the two documents meant nothing. It's the here and now that counts!
Five birds are sitting on a fence. Three of them decide to fly off. How many are left?
DavidCrow wrote: Five birds are sitting on a fence. Three of them decide to fly off. How many are left? Five? J
"I am the Lorax. I speak for the trees."
-
A snake?! A snake!! A snake!! J
"I am the Lorax. I speak for the trees."
> A BIG GREEN SNAKE BARS THE WAY!
Software Zen:
delete this;