"The US government has the biggest bankroll of any nation. We should be putting it to better use if you ask me."
Well...if you ask me (not that anyone did) we should be reducing the "bank roll" (more like
"bank robbery").
Word (or whatever for all you anti-M$ freaks) documents to start. There is a program called Visio that we use at work. It is a neat program that helps with flow-charts.
We also use something called PVCS Version Manager and PVCS Tracker. Version manager is just that (there are other, even free, version managers). It allows for code versioning. You can also use it to version changing documentation.
PVCS Tracker is a system of keeping track of open "issues". If there is an enhancement/bug fix/whatever, you just open a ticket, and close it when it is done. You can also assign owners to the tickets, as well as a progress label. So when the coding is done, you can change to "testing" and the person responsible for that would then take over...
I'm not a PVCS advocate or anything, it's just what we use...company wide.
I think the MAIN thing to do is to start doing something. If you START documenting, you will, over time, refine your documentation process. There will be mistakes, but just keep improving and working on them...
I've had a hard time finding a good reference book on SQL. Maybe something like...the first half of the book covers ANSI standard SQL (plus common functions), with remaining parts of the book covering a couple specific implementations (Oracle, MySql). One or two would be good.
Slashdot Mirror
"The US government has the biggest bankroll of any nation. We should be putting it to better use if you ask me." Well...if you ask me (not that anyone did) we should be reducing the "bank roll" (more like "bank robbery").
Word (or whatever for all you anti-M$ freaks) documents to start. There is a program called Visio that we use at work. It is a neat program that helps with flow-charts.
We also use something called PVCS Version Manager and PVCS Tracker. Version manager is just that (there are other, even free, version managers). It allows for code versioning. You can also use it to version changing documentation.
PVCS Tracker is a system of keeping track of open "issues". If there is an enhancement/bug fix/whatever, you just open a ticket, and close it when it is done. You can also assign owners to the tickets, as well as a progress label. So when the coding is done, you can change to "testing" and the person responsible for that would then take over...
I'm not a PVCS advocate or anything, it's just what we use...company wide.
I think the MAIN thing to do is to start doing something. If you START documenting, you will, over time, refine your documentation process. There will be mistakes, but just keep improving and working on them...
I've had a hard time finding a good reference book on SQL. Maybe something like...the first half of the book covers ANSI standard SQL (plus common functions), with remaining parts of the book covering a couple specific implementations (Oracle, MySql). One or two would be good.