[Nykc]

Let me chime in on this point. I worked in a banking environment that does everything Baavgai described. We would attend meetings, write our own requirements documentation, write our own tech designs, then someone else would look it over and green light it, then we would code. Also when doing Tech Design documentation we wouldn't write out psuedocode, we had to write out the actual code with no way of telling whether or not it actually worked and half the time it didn't. Now of course who do you think all this time is getting billed to? The Client.

It is a waste of time in my eyes, but that is how they wanted it. There is no reason we could have not just contributed to the Tech Design document and start writing and debugging our code.

[Bort]

Of course there was. You would get less of the client's money.

[baavgai]

Nykc, on 21 Oct, 2008 - 11:49 AM, said:

I worked in a banking environment that does everything Baavgai described.

Banks are notorious. They used to do things like have programmers only write portion of the code for a system and never let them see the rest. They're one of the last big clients for the monolithic mainframes, mostly because they're terrified to turn them off. The systems are often very well documented, but it can take a few years to get through the docs.

[supersloth]

guys, you all seemed to miss out on the really important point here, 'who the fuck cares?' it's a self-imposed title with little meaning. coder, programmer, who cares, you will never use except to describe what you do for a living to people who don't know what the fuck you are talking about or don't give a shit.

i can call myself "king marmalade, duke of ethnic shoes and sasquatch hunter" all i want, doesn't change the fact it's meaningless (until it changes to "sasquatch killer", you can't fuck with that)

[Nykc]

Lol - the average Requirements document for a simple program was 50-60 pages. Mostly rehashing the same BS that is summed up in the first few pages.

We still had a few COBOL Developers and Mainframers were in high demand. The bank I worked for was supposedly the 28th Largest bank in America.

They did not want us writing any code without going through a 4 tier approval process. It was ridiculous, out of the time I was there until some of us got laid off I wrote maybe 2500 lines of code in the year I was employed with that department.

The bulk of my days were in team meetings, briefings, writing requirement documents, tech design documentation and reading through horribly notated code.

As for the documentation - besides being thorough but highly fragmented, you have better luck searching MSDN Knowledgebase.

Wow I do not miss that place.

[baavgai]

supersloth, on 21 Oct, 2008 - 02:26 PM, said:

i can call myself "king marmalade, duke of ethnic shoes and sasquatch hunter"

Someone needs a new sig. And maybe a hug.

[supersloth]

i just changed my sig yesterday!

[Mikhail]

Here we go a few standards if would use before hiring anyone:

1. Do you have any experience college not necessary can you code? can I understand your code?
2. Do one of my challenges within 2 weeks Most of the hardest I gave was: Create Dynamic Signature in PERL and UI software for updating it <yes its possible with the right modules
3. Learn to wipe your own ass - And don't ask me about any minor programing stuff.