There's a lot more to worry about than just the first developer. Unfortunately, the kind of organizations who build software that they can afford to literally burn to a CD and leave in a box for the next dev won't pay that first dev to spend time on most of the items described here. They usually don't understand QA--you can leave them with all the docs, source control, and automation you want, but the VBA programmer they accidentally mis-hire, or the departmental power-user who thinks he can program are going to mess it all up before the Chad Myers of the world arrive. These people spend days or weeks rolling in the source code breaking 100 things because they don't know how to fix 1; in any case QA is out the window and the source is left in a trashed state. If any developer in the chain doesn't appreciate the tenets you describe, they'll just break or remove any infrastructure you give them.