I have to qualify that both are good for different purposes. But do go ahead and share your experiences with your stack used and performance.

Yeah this is the part Im confused too. And when you think about JS and JSON ...messy.

By others meaning(Ruby, Python Java etc) for real time, concurrency type of capabilities? Or am I terribly misinformed? I dont have Node experience but Ruby seems not too easy to put together with AngularJS.

I understand Node.js's primary con is the usage of multiple CPUs. However my understanding of backend is not as good. This article also talks about difficulty with relational databases? Can someone explain it better or correct it if the link is wrong?

Wish to hear your experiences (both sides) dealing with Node.JS and other parts of your stack as a whole. Please feel free to rattle all you wish, I will be happy to hear more about them.

Thanks for the lengthy feedback, appreciate the elaboration on the bindings and the UI. Its actually the strength of Angular but I guess when it gets too big, it gets unwieldy in the case of meteor.js

Thanks Nico, I was in this direction just that real time comes with a hefty price tag and little or no open source options.

From preliminary obervations, Meteor.js as some users have earlier mentioned, is actually a full platform but yet with sketchy documentation and little support from users in terms of open source stuff and help.

I only started speaking at 3 and I was in an environment with English, Chinese, Malay and 2 other dialects. Certainly not a indicator of general well being and intelligence since I turn out ok, just not very sociable :) I also read that late speakers may hint at other stronger developments like spatial thinking. But in any doubt, bring him to see a doctor if unsure.

That's why most who have seen some success would say (or so I have heard from their mouths):

"The more you try, the luckier you get".

There may be an element of luck that may affect to a significant extent (think lottery) without or having little attempts but in the long run it pans out. This highlights not only the importance of sticking it out, but sticking it out long enough, even after getting smashed many times over.

But of course, there has to be a specific and unique insight as a starting point, ala how can you make something better than whats out there now?

Its not surprising that people whom are passionate about their circle of competency, those who would venture in all directions from their initial locus/loci, seemingly random areas would pick up observations that others miss.

And only those with a genuine passion and interest will continue sticking out, even in the darkest times.

Ermmm well we all learn by observing other codes out there many times and rest of it troubleshooting isnt it?

If it works, it works. Why bother re-writing it anyway? Unless its refactoring.

If its me, Ill confront him and ask him about his insecurities and if theres any issues.

But thats just me.

Its always good to teach and share to reinforce your existing skills and discover new ones.

Like many said, mentoring or taking up/ suggesting new projects may be a plausible avenue. You could also internally create some challenges for yourself in relation to work, for example I may want to have codes in portable modular form so I can use for other projects etc.

There is no need to burn bridges even if the work is not fitting, especially when people are nice.

Ultimately, this is admittedly short term. Alignment of interests and incentives are critical in the long run, thats why often people are willing to forgo larger stable paychecks to head over to risky startups with low paychecks.