Joined October 2012
·
Posted to
Node.js is not suitable for generic web projects (V)
over 1 year
ago
Excellent article.
Coming over to NodeJS has been an interesting battle for me. I had written a couple simple generic service apps in NodeJS, and never really got to "liking" it. Primarily because of Callback Hell. Just dealt with some of the idiosyncrasies that it has. Then I ended up doing a much larger project in it, and that 'sealed the deal' for me. Comparing what NodeJS offers to other frameworks doesn't really capture the feel of the language, and the power that it has. I'm not really sure there is a good way to capture the feeling. It's almost something that you have to just jump in with both feet (as opposed to dipping in a toe), and see for yourself.
Achievements
69 Karma
0 Total ProTip Views
Honey Badger 3
Have at least three Node.js specific repos
Honey Badger
Have at least one original Node.js-specific repo
Kona
Have at least one original repo where CoffeeScript is the dominant language
Charity
Fork and commit to someone's open source project in need
Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos
Forked
Have a project valued enough to be forked by someone else
Mongoose
Have at least one original repo where Ruby is the dominant language
Nice post. A couple comments though:
1) Don't undercut your skills, and the skills of other engineers. It takes a long time to learn the skills to be any level of decent engineer. A waitress only has to bring food around to tables and smile. Yes, it's harder physical labor, but anybody could (could being the key word) do it. An engineer has to learn all sorts of different ways to bend their brain, and solve real world problems. Workers that do skilled labor have always made a higher salary than their unskilled counterparts. That's the way the world works. Is it worth 100k+? Of course it is. The market will bear it, and therefore that is the salary. Supply and demand.
As you get in to freelancing, this becomes even more noticeable. Depending on your notoriety and skill set, you can charge far more to clients than you can if you're an unknown quantity. That's partly how you set your hours. By setting your rates for certain times that are well above most companies acceptable limits. Sometimes they will surprise you and accept the $400/hour rate that you quote, but more often than not, they wont. Particularly when you say '$400/hour for this week, but the following week is only $90/hour.'
2) Avoiding SQL joins. I found this highly amusing. I've been saying that for a long time. If you take it to heart, it completely throws any reason to use relational databases out the window, in favor of NoSQL ones like Mongo, Couch, Riak, Cassandra, etc. At least from my stand point. But that argument is probably worth its very own post, so I'll leave it at that.