Have you ever worked on a project with any decent documentation?

[suityou01]

Just thinking. Can't remember the last time.

Architecture diagrams, ERDs, data dictionaries, system specifications?

Just piling through some code but I've not got a clue where it's used in the main solution so I need to do some hunting around. This will take a few hours. Would take seconds if there was documentation.

[SimonMac]

Just thinking. Can't remember the last time.

Architecture diagrams, ERDs, data dictionaries, system specifications?

Just piling through some code but I've not got a clue where it's used in the main solution so I need to do some hunting around. This will take a few hours. Would take seconds if there was documentation.

Every project I leave has impeccable documentation, if you can't find what you need, do it yoruself

[suityou01]

Every project I leave has impeccable documentation, if you can't find what you need, do it yoruself

So stop work on my deliverables and choose to deliver documentation instead? It's ballsy, but it just might work.

[DimPrawn]

At the top of each code file you will find a unique identifier that ties it to the functional specification, the test suite, design document and the requirements documentation, no?

[mudskipper]

My code's got comments in it - what more do you want?

[suityou01]

At the top of each code file you will find a unique identifier that ties it to the functional specification, the test suite, design document and the requirements documentation, no?

Ah that's where it is then.

Nope. SFA.

[suityou01]

My code's got comments in it - what more do you want?

<censored>

[Mich the Tester]

At the top of each code file you will find a unique identifier that ties it to the functional specification, the test suite, design document and the requirements documentation, no?

So you have a thousand files with identifiers like this;
FSBSHPQC123DDBSReqBS0_1
FSBSHPQC123DDBSReqBS0_2
FSBSHPQC123DDBSReqBS0_3
FSBSHPQC123DDBSReqBS0_4

Almost as useful as no documentation at all.

[tranceporter]

Documentation is a rarity these days. Most organizations push themselves to deliver more and beat the competition, and so the onus is always on getting the functionality tested and out of the door to be "first in the market to offer xyz". That being said, most business analysts don't have much of a clue as to how the system works either. All they do is pass your query to one of the senior fats cats who has been fossilised in his position for 15 years, and wait for him to answer in an "AGILE" way.

[VectraMan]

All my code is documented in C++. It isn't my problem if you're not intelligent enough to understand C++.