3 ms·

I submitted it because it's exactly how I feel lately, and would like to know what others think about it. My current (personal/academic) project involves Node.j

I submitted it because it's exactly how I feel lately, and would like to know what others think about it. My current (personal/academic) project involves Node.js, (Iced)CoffeeScript, MongoDB (with Mangoose), PhantomJS, Mocha, Neo4j, Nutch, Solr, Hadoop and Mahout. All of them are new technologies and are changing rapidly and daily, and I find new stuff every day that forces me to change my APIs and the way I do things, and it's getting frustrating... It's the price you pay by using cutting-edge technologies and I accept that, but I can't help thinking that maybe Java+MySQL was a better/easier choice!

gouranga 14y ago
I suffer from the same trouble on occasions. I primarily deal with the Microsoft ecosystem which is volatile and fragmented at the best of times. I would kill to do something in good old java/mysql. A lot of the new ideas and principles are a mess. Don't get too absorbed - just use what lets you get the job done quickly and efficiently. a lot of it is just noise. I tend to find that a complete break from everything for a day helps. That and cider :)
- Morg 14y ago
  Try postgreSQL next time, at least it's ACID compliant ;)
gfosco 14y ago
Try using less things... How about just using Node and Mongo, and building the rest yourself? Node being in its infancy is a pretty good reason in itself to not tie yourself to the frameworks which are likewise infantile. I've got several production back-ends and a full-stack e-commerce site running with Node and MySQL only.
engtech 14y ago
Experience has taught me that if you want to get something done, you need to stay off the bleeding edge, or at the very least only drag yourself to the bleeding edge at controlled increments. The only thing that should be changing often is YOUR code. Everything else should be as stable as possible. What I find works best is playing leap frog: * your code is unstable / upgrade nothing * your code is stable, stop changing it and upgrade things one at a time test suites / regressions are a must.
helper-method 14y ago
A month ago I finished a project for university, involving Node.js - nothing more. At the beginning, I've started with Node.js, mongoDB, socket.io. express and connect. Half way through the project, I realized I would never be able to deliver in time. So I started to cut out technologies... first mongoDB, socket.io, express, and in the end, even connect. Even dealing with Node alone, I had a hard time finishing my project... but I did. I still got quite a good grade because in contrast to my fellow students, I was able to deliver.

gouranga 14y ago

I suffer from the same trouble on occasions. I primarily deal with the Microsoft ecosystem which is volatile and fragmented at the best of times. I would kill to do something in good old java/mysql. A lot of the new ideas and principles are a mess. Don't get too absorbed - just use what lets you get the job done quickly and efficiently. a lot of it is just noise. I tend to find that a complete break from everything for a day helps. That and cider :)

Morg 14y ago
Try postgreSQL next time, at least it's ACID compliant ;)

gfosco 14y ago

Try using less things... How about just using Node and Mongo, and building the rest yourself? Node being in its infancy is a pretty good reason in itself to not tie yourself to the frameworks which are likewise infantile. I've got several production back-ends and a full-stack e-commerce site running with Node and MySQL only.

engtech 14y ago

Experience has taught me that if you want to get something done, you need to stay off the bleeding edge, or at the very least only drag yourself to the bleeding edge at controlled increments. The only thing that should be changing often is YOUR code. Everything else should be as stable as possible. What I find works best is playing leap frog: * your code is unstable / upgrade nothing * your code is stable, stop changing it and upgrade things one at a time test suites / regressions are a must.

helper-method 14y ago

A month ago I finished a project for university, involving Node.js - nothing more. At the beginning, I've started with Node.js, mongoDB, socket.io. express and connect. Half way through the project, I realized I would never be able to deliver in time. So I started to cut out technologies... first mongoDB, socket.io, express, and in the end, even connect. Even dealing with Node alone, I had a hard time finishing my project... but I did. I still got quite a good grade because in contrast to my fellow students, I was able to deliver.