If it works for you then awesome. I just don't like how it feels personally. Also we don't use node on our backend where I work, that may account for my thoughts on the matter.
Since browserify is taking npm modules and making them compatible on the browser. As the article points out, you will only know if it works when you try and either fail or succeed. And as the article comments point out, you would then need to make node_modules public or have something/someone in place to copy the files over to the public dir and keep them in sync.
NPM is great and so is browserify, but I just can't comprehend the idea of basing your front-end module system around something that confused about its own identity.
I'm glad to read this blog post. This has always been the point of my confusion regarding front-end devs using Browserify.
It isn't very intuitive unless you're also a nodeJS dev and you're usually going to end up using things in a very hacky way.