- Organizational Standards and Conventions
- Putting the "Engineering" in Software Engineering
- Working with Logging and Tracing
- Project and Packaging File Structure
- Unit Testing Requirements
- Code Completion and Review Process Requirements
- Communicating the Vision the Wiki Way
- Links to developerWorks Articles
This chapter outlined the importance of setting standards within your organization or project. I am not able to provide complete answers to every nuance of what you might need, but the general flavor and type of standards that you need to be successful have been outlined in this chapter. This book just scratches the surface of what you need for many projects within your organization.
If you are asked to put together standards for your organization, I believe it would take a small team of three or four people several weeks of part-time work to come up with a solid, comprehensive set of standards. This is a minimum effort; a comprehensive set will take longer.
As for any of the discussion within this chapter if you disagree with any of my advice, then feel free to call me an idiot and do your own thing. I have always made the point
I would rather you have any standard, maybe even bad ones, then no standards at all. I still believe this today, although more and more I am learning to commit to recommendations based on my experiences with many development teams working on the WebSphere platform.