> IMHO, ideally, developers should not be sharing any > resources. In most cases I agree, if 'personal' versions of large products are available, manageable, not cost-prohibitive, etc.
> What happens if a developer drops a table, or renames > a column, or changes a stored proc? > What happens if a developer > bounces or crashes the server? > What happens if a developer renames a stored proc, > changes the arguments to one, or changes the type of a > column? If the system, including the data model, was adequately designed, then table defs, code interfaces (signatures), etc. should be documented and adhered to during coding. I understand that small development efforts do not always employ such rigorous steps such as design, but the project described in the original post didn't sound like a small effort to me. I agree that server problems are a risk, but steps can be taken to mitigate those risks. > Of course, if there are only a few developers, the > problems from above may be tolerable. OTOH, if > there's more than just a few developers, work starts > to become fighting amongst each other. Again, a good design and stakeholder/SME consensus can help reduce or eliminate this kind of behavior. That is, unless office politics, workgroup rivalries, and other such human-related problems become more important than producing quality software. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
