Beyond Modules–Using Node To Build Actual Products

How Many of You Have Written Modules?

Besides @substack

How Many Modules Have Been Written?

As of literally right now there are




NPM modules available.

( via: http://npm-count.jit.su )

MOAR MODULES!!!1!!1!

Number of Modules I've Written

0

But, I've Built Some Products (Apps)

Gunnar

Dillinger

PhotoPipe

So Joe let me get this straight. You can build products,
but can't write a module?

Nah bro, I just do what feels good.

The reality is, many of us are good at writing libraries, modules and plugins.

And some of us are good at taking those modules, libraries and plugins and assembling them.

So My Challenge to the Module Authors Is...

Go Assemble Your Voltron!

Or simply, build a product.

How Do I Get Started?

The Philosophy

Be one with your neckbeard.

Adopt the UNIX philosophy of simple, discrete modules that do one thing and one thing well.

Not only should your modules be discrete, but your application architecture should be modular as well.

Case Study: Dillinger

Dillinger 1.0
worked fine

But, it was not modular.

Adding new features or functionality was painful.

Difficult for devs to contribute due to dependencies.

This was an architectural flaw. I called myself out and decided it had to be fixed.

Dillinger 2.0 is modular, pluggable and way easier to contribute to.

See much more here:

What About New Features
for the Product?!

Tools

• Express -- Great for Network Apps
• Nodejitsu -- Great for Hosting and Scale
• App.js -- Great for Desktop Apps

But Why?

Building a product, even as uselessware, enhances your skills as a developer and will actually improve the way you write modules.

Final Thought

Before writing your next module, consider how that module will be used in an actual product.

If you're unsure, then build something with it to find out!

The consumers of your module will thank you.