4 ms·
The exciting part of this for me would be around improvements in Yahoo - removing old cruft code. There's lot of strangeness and/or flat out errors I run into o
by fideloper 12y ago
The exciting part of this for me would be around improvements in Yahoo - removing old cruft code. There's lot of strangeness and/or flat out errors I run into on Yahoo regularly. Any improvement in that regard could be a big benefit.
On the topic of JavaScript - I love Node as a glue. For larger applications - I just don't know how to structure (architect) a large application on a language like JS. Maybe that's just my ignorance.
- woah 12y agoWrite modules.
- edwinnathaniel 12y agoThat's like saying write classes and methods. Not enough.
- woah 12y agoYea, I'm not saying it's a miracle cure, but in general I have found the following to be useful: 1) Break any functionality possible into a separate npm module - not just a separate file with module.exports. Keep the npm module small and break it up further if it gets too big. 2) This module will be small enough that it is trivial to debug, refactor, test, and document. If it gets to a size where these tasks are hard for any reason and you wish for strong typing or something, the module is too big. 3) Please make sure that you do test and document the module. This will make your team way faster in the future.
- spion 12y agoI don't know, I kinda wish for strong typing even in smaller modules. https://github.com/doxout/promise-observer https://github.com/doxout/promise-observer and its statically verified documentation as well (therefore never goes out of date)