I almost always document how to set up a good development setup (live code reloading, tests running, decent error reporting, you know the drill), and how to cre

I almost always document how to set up a good development setup (live code reloading, tests running, decent error reporting, you know the drill), and how to create a production build (these both should be a single line on the command prompt). Aside from these I tend not to document anything else about the development process -- not for any specific reason, though. I don't expect anything else to be a big time saver until I end up on a team with more than 3 people working on the same codebase.