4 ms·
If it's NodeJS the fastest way is to check how many dependencies they have in total, bad developers will find a way to include 100s or 1000s of dependencies, an
by benologist 9y ago
If it's NodeJS the fastest way is to check how many dependencies they have in total, bad developers will find a way to include 100s or 1000s of dependencies, anonymous third-party blobs of code running within their application:
$ npm install
Another indicator is how elaborate their build process to munge w/e they wrote into w/e a machine understands.
- buckbova 9y agoDon't agree with the approach because using a proven solution can be superior and net a simpler code base than rolling your own. Fyi, by using webpack, couple loaders, babel, etc I net 100s of dependencies just for the build. Ymmv.
- deleted 9y ago[deleted]
- spinlock 9y agoI think this is right. I might as how they start the dev environment or kick off a build. Should be something like `yarn start` and `yarn build`. We all work with really complex systems. The trick is to abstract them to the point where they're simple to understand and use. 1000s of dependencies doesn't even have to be complex at all if you use simple patterns to manage those dependencies.