I returned to a project wiki on confluence after a few months break, and was looking through the documentation wondering if it was still relevent. The code and requirements had changed in places, so I knew some was out of date – however the documentation of the new areas looked good. There were also other design artifacts that seemed important at the time, but now I felt had questionable value.
In my experience the problem is that we create lots documentation at the start of a project to set direction, but as the project continues it becomes easier to see how the requirements slot into the overall design. This means we are less likely to update the documentation in these areas as they are covered at a high level in the existing documentation. This means the information can slip through the cracks.
I’ve had a look into solutions to this problem –
I would be interested to read how other people manage project documentation, especially in small teams
What does Spring DelegatingFilterProxy do?
Java8 – Methods in Interfaces
Java8 – Date and Time examples
Java8 – Optional’s Overview with Examples
Java 8 – Streams Cookbook
How Lambda’s And Anonymous Inner Classes(AIC) Work
Another Java Lamdba Post
Google – Site Reliability Engineering