Carl,

I would recommend you to separate in files, though each developer has a 
region to work. In my experience it is no good to have long method with 
long lines and either long files. Cut to the chase. My architecture´s view. 
Take it or leave it.




El viernes, 28 de agosto de 2015, 23:42:40 (UTC-3), Carl Swanson escribió:
>
> Does anyone work on a large nodejs project with a decent sized team where 
> code source branching problems and re-merging becomes a problem? Where 
> multiple people touch the same relative code area, and then have effort 
> needed on successive check ins to merge code back together?
>
> What have you done to solve this type of issues?
>
> I'm doing some research and would love to hear from ideas in this area.
>
> Thanks,
>
> Carl S
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/392aee26-3835-4bd8-b87c-af8daf3afa76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to