You know when...
-
...The business tries to implement something and you say "there's no way that can be done". So it get's pushed back up the chain and back to the customer and they change everything because YOU said it couldn't be done and everything gets delayed as you only noticed it couldn't be done a week before roll-out. Then you start reviewing the new proposal and it dawns on you that actually the old way could have been done? Yeah that's just happened to me this morning. I will be keeping stum. :-O
-
...The business tries to implement something and you say "there's no way that can be done". So it get's pushed back up the chain and back to the customer and they change everything because YOU said it couldn't be done and everything gets delayed as you only noticed it couldn't be done a week before roll-out. Then you start reviewing the new proposal and it dawns on you that actually the old way could have been done? Yeah that's just happened to me this morning. I will be keeping stum. :-O
keep fingers crossed and prey nobody else realize that it could be done the old way. Spare some time to find, why the old way is / was NOT the right way, even if it could be done (which you may have to admit if someone else finds out).. and then don't un-cross the fingers :-)
Thanks, Milind
-
...The business tries to implement something and you say "there's no way that can be done". So it get's pushed back up the chain and back to the customer and they change everything because YOU said it couldn't be done and everything gets delayed as you only noticed it couldn't be done a week before roll-out. Then you start reviewing the new proposal and it dawns on you that actually the old way could have been done? Yeah that's just happened to me this morning. I will be keeping stum. :-O
How long would the change have taken to write and test? Would it delay the roll out? Could you guarantee that it wouldn't have impacts elsewhere? If the answer to any of these questions indicates that it's a risk then you were right to state it couldn't be done. You just left out the phrase, "and deliver the project to time and on budget".
This space for rent
-
keep fingers crossed and prey nobody else realize that it could be done the old way. Spare some time to find, why the old way is / was NOT the right way, even if it could be done (which you may have to admit if someone else finds out).. and then don't un-cross the fingers :-)
Thanks, Milind
-
...The business tries to implement something and you say "there's no way that can be done". So it get's pushed back up the chain and back to the customer and they change everything because YOU said it couldn't be done and everything gets delayed as you only noticed it couldn't be done a week before roll-out. Then you start reviewing the new proposal and it dawns on you that actually the old way could have been done? Yeah that's just happened to me this morning. I will be keeping stum. :-O
PompeyThree wrote:
I will be keeping stum.
Personally, I'd forget the unfermented grape juice[^], and keep shtum[^] instead. ;P Especially when you also realise that the new proposal really can't be done.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
How long would the change have taken to write and test? Would it delay the roll out? Could you guarantee that it wouldn't have impacts elsewhere? If the answer to any of these questions indicates that it's a risk then you were right to state it couldn't be done. You just left out the phrase, "and deliver the project to time and on budget".
This space for rent
Pete O'Hanlon wrote:
How long would the change have taken to write and test? Would it delay the roll out? Could you guarantee that it wouldn't have impacts elsewhere?
It would probably be quicker to use the original method - but it would mean asking a lot of people (Pm's , EC engineers etc) to undo a lot of changes I asked them to make for no reason. There probably is an element of risk in the future as my solution would just be more tribal knowledge. The customer is a homophone of the surname of the famous gangster twins - so it's not as if we are speaking a big deal or anything :doh:
-
PompeyThree wrote:
I will be keeping stum.
Personally, I'd forget the unfermented grape juice[^], and keep shtum[^] instead. ;P Especially when you also realise that the new proposal really can't be done.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
:thumbsup: Thought I was spelling it wrong but Google didn't give me the curly red line - so I thought I was OK.
I thought it was spelled differently, but I decided to stay MUM about it. Yes, I'm American. What of it?
-
:thumbsup: Thought I was spelling it wrong but Google didn't give me the curly red line - so I thought I was OK.
-
MT_ wrote:
keep fingers crossed and prey nobody else realize that it could be done the old way.
Nobody else will notice - it's a tribal knowledge thing and I'm chief of this particular tribe.
-
...The business tries to implement something and you say "there's no way that can be done". So it get's pushed back up the chain and back to the customer and they change everything because YOU said it couldn't be done and everything gets delayed as you only noticed it couldn't be done a week before roll-out. Then you start reviewing the new proposal and it dawns on you that actually the old way could have been done? Yeah that's just happened to me this morning. I will be keeping stum. :-O
"New programming technology has made it possible." Followed by: "I've managed to give the customer exactly what he wanted. Where's my bonus?"
I wanna be a eunuchs developer! Pass me a bread knife!
