On May 24, 2014, at 8:55 AM, Jake <[email protected]> wrote:
> In discussions at my company about adopting node.js one concern that tends to
> come up is about managing the codebase of a large project where about 10
> developers are working on it concurrently.
>
> I would like to get some suggestions, techniques, best practices, and advice
> from the group here for:
>
> 1. maintaining a clean codebase for a large node.js web application
> 2. refactoring in a large node.js project (probably tied to #1)
> 3. having a team of about 10 developers working on the same node.js
> application
> 4. quickly ramping up new developers (that already know JS well) on a large
> node.js application
>
I have but one suggestion: choose one style of JS programming for the team and
stick to it. Are you going to mimic or emulate classic OO with classes,
prototypes, inheritance, etc? Are you going to use IIFEs for encapsulation? Are
you going to use callbacks, or promises, or some other "flattening" library?
--ravi
--
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/CBB29D88-C24B-40CB-A61C-BF955CA925F2%40g8o.net.
For more options, visit https://groups.google.com/d/optout.
