Replies

Well, one who understands concepts of writing maintainable code would be nice... ;0)

Does the client want to pay for maintainable code? Does the client want to underwrite your experiments in making lovely philosophically pretty systems that you would be happy to show to your coder friends?

I havent been in the industry wrong, but I so far I am ashamed of everything I write. There isn't time to do it right.

Of course, this may only be the case at the very bottom of the food chain... but isnt that where vb belongs?

This isn't about the client, since we dont have client's paying us for custom products - we have a product line, of which VB is used for user interface layers, which are part of not just a software package, but a hardware package as well. We dont' write code that is given to a client.

Any code written needs to be maintanable, since a year from now I, or another coder, may need to go back and fix, update, or otherwise modify what was written - and it's pain in the a$$ if you have to waste time trying to figure out what the original coder did, or why they did something, because they neglected to comment the code or otherwise document it etc...

Well documented, well-structured code should be the norm, not just 'if the client is paying for it'.