|
And especially on the day of the demo when the customer says
"This is not we wanted" 
|
|
|
|
|
Oh, god. I have something similar. I'm withholding names and won't go into specifics to protect the innocent.
At a previous job, I'd been telling the boss for years something he wanted automated couldn't be automated, unless he hired somebody to maintain the automation code, pretty much as a full-time job. Basically, the process being automated was a moving target.
So one day he decided to go ahead anyway and wrote the code over a weekend. It only worked for a week. And yes, somebody had to maintain his code all the time from that point forward.
|
|
|
|
|
Being told your little side project you had been working on, because you were never really sold on the current design would work.
Well they hit the wall and now your baby is it, only you aren't really sure about it either
In vino veritas
|
|
|
|
|
Oh sh*t, I'm doing a prototype in WPF for a Java project - I hope like hell they don't go forward with the WPF
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
1) Requirements
2) Licensing
3) Component interfaces and ways of doing things
4) Unsupported code
|
|
|
|
|
Mehdi Gholam wrote: 2) Licensing
oh yes!!!
I'd rather be phishing!
|
|
|
|
|
And especially at the moment of the release.
|
|
|
|
|
|
Multi-Byte Vs Unicode; why on earth was it not dealt with the day after it was discovered that there are people outside of Europe and USA. Windows should have been 100% unicode every since it no longer depends on MS-DOS.
|
|
|
|
|
Yep and especially when they say:
"I think we would not be needing the feature you have developed. Its redundant" after banging heads on weekends and after prior instructions.
|
|
|
|