If a jobs worth doing

[suityou01]

Will code for food.


Sent from my iMinion using Tapatalk

[suityou01]

I think I am unemployable. I just want to sit down and RTFM. People nowadays are all "agile" which means hopping around from foot to foot "trying stuff" and getting more and more animated.

Under enemy fire (clientco) I said I suspected it was a WCF config problem, that I don't know all that much about WCF and I was going to sit down with a coffee and calmly read the MSDN.

I read the MSDN. Changed the config as per what I read. It worked perfectly and I am now getting on with it.

Why is my approach so wrong?

[minestrone]

"you have been a great worker over the last 3 years but before you go at 5 tomorrow do you mind writing a handover document explaining everything one needs to know to do your job"

[MicrosoftBob]

"you have been a great worker over the last 3 years but before you go at 5 tomorrow do you mind writing a handover document explaining everything one needs to know to do your job"

That's easy just write Google

[barrydidit]

Why is my approach so wrong?

I reckon it's the Frank Spencer look. If you ditch the trechcoat and the beret you might inspire more confidence when you open your mouth.

[darmstadt]

I think I am unemployable. I just want to sit down and RTFM.
Why is my approach so wrong?

You also have to be able to UTFM

[suityou01]

You also have to be able to UTFM

[smatty]

You shouldn't need documentation, the code should be self documenting.

[DimPrawn]

[suityou01]

On reflection

An interesting point (for me anyways)

When I start a thread whining about unclear requirements, the consenus is it's my fault and I should be able to develop a system with vague requirements.

When I pose a question on here, the consensus complain about the requirements.

Then, with aforementioned "vague" requirements the forum guru strolls in and solves it.

Perhaps some of you should take your own medicine.

Just sayin