I've been working on an open-ended project for about 2 years now, and up until this point, I've been the only developer.
I take the specs from my boss and translate them into code. I did my best to document everything I did with JavaDoc comments and such, but sometimes when I'm feeling really creative, I can't take the time to break my train of thought to properly comment.
Now, I've got a new guy coming in who will probably be replacing me when I leave in a few months. What is the best way to bring him up to speed on how things work in the project?
I've tried to modularize things so that he will only have to look at small, independent chunks instead of the entire project, but each chunk is still pretty sizeable.
Any thoughts? Any books been written about this?
Thanks,
Micah