The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I had to watch in horror yesterday as a colleague worked with a client (over a remote) configuring and testing a brand new module that they rushed me to build!
Friday of previous week:
Them: 'I need a new module that does xyz. How long will that take?'
Me: 'At least 30 hours of dedicated time on the project.'
Them: 'Is it done yet?'
Me: 'Almost. With any luck I can have it done by the middle of next week.'
Them: 'But I told the customer you would have it done this week...Have it ready for next Monday.'
It worked mostly! Of course they had to throw in an edge case that hadn't been mentioned...specs, what specs?
After doing this for 16 years, with the same company, I continue to be amazed at the number of 'options' that have to be added to even the simplest software over it's life to satisfy everyone and accommodate each new situation.
A good night to think on it, spend this morning tweaking, and version 2 is now ready for abuse!
My experience has been that salespeople will promise anything to get the sale and/or retain the customer.
Whether they tell you about the feature they promised is optional.
Your compliance however, is mandatory, whether or not if it is possible.
If not, it's your fault, not theirs.
It still aggravates me when I remember the time the CEO and VP called me to bitch me out for not having something done and then finding out the two of them had decided on a new feature and neither bothered to tell me about it, but they were steamed because I had somehow failed to read their minds.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
I was working on a project where the clients actually did something similar. Always managed to sneak in a requirement/feature or two directly to the developer. We were working too close to the client in this scenario and did a lot of work which we didn't charge for. Ran a big loss at the end of the day. We're talking millions. We learnt a very important lesson from this.
P.S. CEO and VP's are also clients at the end of the day. Just internal ones. They should be treated the same as external ones. They should follow the correct routes if they want to add/change requirements.
One thing I like about scrum (and I don't like everything about it) is that it is very clear on setting boundaries in this area. It protects the developer from these pitfalls very nicely.
"Program testing can be used to show the presence of bugs, but never to show their absence."
He probably got a call 2 minutes after posting that, "Umm, I got a guy who did THAT, which fubarred the install, can you come take a look?"
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
"I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
Last Visit: 30-Oct-20 10:50 Last Update: 30-Oct-20 10:50