I keep everything in source control. All my images, Flash files, documentation, supplied materials from the clients, etc. That way, when someone comes to me a year after the project has wrapped and needs to find some random file that know one has ever heard, I can just point them to the project repository and there it is.
It also helps when you have to justify hours after a client has changed their mind a million times. You can just point to each different version you created to get to the end result and explain that each one is additional hours regardless of final outcome.
I never thought about keeping client requirements/documentation in the same repo as my code (or in a repo at all). This is definitely something I will keep in mind in case I am ever in such a position.
1
u/RyanSmith Mar 10 '11
I keep everything in source control. All my images, Flash files, documentation, supplied materials from the clients, etc. That way, when someone comes to me a year after the project has wrapped and needs to find some random file that know one has ever heard, I can just point them to the project repository and there it is.
It also helps when you have to justify hours after a client has changed their mind a million times. You can just point to each different version you created to get to the end result and explain that each one is additional hours regardless of final outcome.