When developers get way to nitpicky

[stek]

The cancel button should move when you hover over it like in the old Windows piece of malarky about the size of ones personal member and a moving NO button that was going the rounds a few years back, another was whisperer.exe.....

HEY EVERYBODY, I'M LOOKING AT PORNO OVER HERE!!!!

[Scary]

or you are easily goaded

Way too nitpicky.

[suityou01]

Red rag to a bull.

or you are easily goaded

[Scary]

at time of writing this thread has 5 stars and a non offensive tag cloud

Red rag to a bull.

[MarillionFan]

A well reasoned and polite answer.

Who is using the MF account at the minute?

Can't say. But i've only got it until he gets back from lunch, he's just finishing his banana!!!

[suityou01]

at time of writing this thread has 5 stars and a non offensive tag cloud

[suityou01]

LOL.

This is a classic response that developers take to projects where there have been problems, delays, bugs and the blame game going on.

Developers shouldnt have to inherently know what a cancel button does for example. They do of course like to get clarification when they feel someone is going to jump on them or they wish to push out time.

They fall into:-

1) Outsourced. Where every minute detail has to be specced and double specced and discussed. Every penny counts!
2) The had a kicking before. Right I'm not going to put the extra effort in to keep this going. The PM dissed me, the BA dissed me and when i did do extra no-one noticed. So to make sure it's going to be the tester or BA's fault I'm going to seek clarification on every fcking inch of this project and spec so when someone says I want it to do A, I'll say, well you never specced it!!!!

Had the 'fortune' to have both of these on my last role and they would come back with a list of 20 questions, which they knew the answers to but would discuss in every detail. Eventually I just told them, we have a bottleneck here which is me, I cannot stamp every minute question you have, you are the professionals, some things are inherently understood, so lets work on that basis. If it's wrong later, we raise a JIRA and make the change, because that will work out quicker than delaying the development cycle.

Good luck. Sounds like you need it.

A well reasoned and polite answer.

Who is using the MF account at the minute?

[MarillionFan]

LOL.

This is a classic response that developers take to projects where there have been problems, delays, bugs and the blame game going on.

Developers shouldnt have to inherently know what a cancel button does for example. They do of course like to get clarification when they feel someone is going to jump on them or they wish to push out time.

They fall into:-

1) Outsourced. Where every minute detail has to be specced and double specced and discussed. Every penny counts!
2) The had a kicking before. Right I'm not going to put the extra effort in to keep this going. The PM dissed me, the BA dissed me and when i did do extra no-one noticed. So to make sure it's going to be the tester or BA's fault I'm going to seek clarification on every fcking inch of this project and spec so when someone says I want it to do A, I'll say, well you never specced it!!!!

Had the 'fortune' to have both of these on my last role and they would come back with a list of 20 questions, which they knew the answers to but would discuss in every detail. Eventually I just told them, we have a bottleneck here which is me, I cannot stamp every minute question you have, you are the professionals, some things are inherently understood, so lets work on that basis. If it's wrong later, we raise a JIRA and make the change, because that will work out quicker than delaying the development cycle.

Good luck. Sounds like you need it.

[Moscow Mule]

CMMI 5? Pile of old cack.

That said, if you don't tell an outsourced development team exactly what you want, you'll get something that doesn't work how you expect it to work. Then, they will charge you to "fix" it as it wasn't in the spec.

This is their business model. Either live with it or hire some locals.

[suityou01]

Briefly, I have written an F spec.

They are hounding me with questions on minutae like what should be the specific behaviour of the cancel button? Response "The cancel button should roll back any changes of state and data, and revert the user back to the previous screen such that the system state is returned to the state before the user entered the screen.

This is getting quite dull for me. I am thinking about writing

"Breathe in"
"Breathe out"

in the next spec.

This is common knowledge for a developer to understand basic and universally known system behaviour surely?