As a programmer myself, I can understand that perfectly, which is why I sort of post this as a just-in-case note.
I'm just placing my bets on which is more important to the developers :
1) Keeping their full access to their code (note that this is not ownership.. e.g. In a company, programmers have access to the code, but the code is still owned and controlled by the company)
2) Wanting to push the development forward with greater speed (and the way to do that usually involve getting the basic framework right which enables modularity and parallel development)
But there's a lot of other non-code related things that can help if the parties are interested and not afraid to redo some problematic parts as early as possible (basically, speaking from real experience, it is better to overcome the reluctance to fix certain costly problems early before it becomes even more costly to fix should other things dependent on it gets created). Things could involve system architecture (both the software system as well as the information system), data design (meta data, on-disk data, data/system forward/backward compatibility).
Architecture is often get ignored in 1-developer sense (myself being guilty more than a few times). 2+developer can still make do if they rely on heavy communication. But if ever somebody drop out or is required to take over another person's stuff, things can get ugly. A proper architecture will ensure that at least the interface of the modules workings together are well defined and good practices will help to make the team more dynamically scaleable (e.g. outsource a module to somebody else without them having to access rest of the core code).
blah blah blah... the list goes on too long for me to want to talk about it at this pt..
As to why I'm posting it here, first and foremost, there isn't an explicit development website. secondly, feel that it is easier for the "receiver" if I post instead of an email (which to me, seems more troublesome ... or it could be just me dislike receiving such things via email). Lastly, I do know that the out front answer will negative. So sort of like leaving a record here in-case and when they need it. (old emails gets lost in time). Also, it seems that a thread makes a more convenient vehicle if there's any quick queries to request.