Keep a personal copy of all documentation you create.
Keeping a copy of all of the documentation you create is a pretty general benefit. It helps you in three major ways;
- Having a personal copy means that if the systems that have the public copies become unavailable, you will still have access to them.
- Some times projects that get shelved, lose their documentation. If you have a personal copy, when the project comes back to life, you will not be starting over.
- And you never know what future project you will be working on that will spark the memory, “Hey we solved a problem like this on this other project…” And having the documentation for it will help you. (more…)
Monday, November 14th, 2011



One of the things that I advocate is keeping a copy of the documentation you produce, and the documentation that you encounter and use. Over a short period of time, this can become a large amount of stuff. If you are just throwing it all in your MyDocuments folder, it can quickly get out of hand. To help out in this ongoing task and fight against the chaos, I am going to share some basic approaches that can help keep the sanity and utility in your documentation collection.
One of the things that Integration Engineers are asked to do is create documentation. But as we all know, many times documentation is the last and poorest part of a project. Developers and programmers don’t generally like writing documentation, and are generally considered the most qualified.