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
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.
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.
1) Everything. Even simple things like pushing codes to repositories took me eons to pick up. Also, programming isnt hard, in fact its easy. The hard part is understanding how to link up everything, front to back and to others such as codetesting, for example with Rspec.
2) I felt sites that promote start-to-end lessons step by step are great. Like codelearn.org. Videos and all are good too but they often target experienced people, so its much more painful to use those.
Failure is usually an iteration. My most recent project failed too.
Good thing is cheer up, at least now you know what doesnt work, focus on what works or what you think may work. I got myself a day job while working on another project on the side.
Girlfriend wise, well it happens. Love your family more.
"Pick yourself up, dust yourself off and start all over again!"
Apart from that, a bulk of people are learning Ruby and hence rails most of the time as the support and gems are pretty vast.
Also, Python is more defined in terms of how you structure the code, while Ruby has more ways to express the same thing, and more tolerant of errors in some sense. With that also comes the problem of harder to troubleshoot errors.
I think if this can be extended to make the changes easy to apply (with real time checking of how the output will be) and understanding the code differences, then many of the wireframe companies out there may lose their appeal....
Feels like the author is trying hard to debunk the book's claims by attacking the definitions. I would think that by providing counter examples or counter thesis would have been more effective.
For example, saying the excavator firm perished due to lack of innovation was due to mismanagement and LBO rather than poor product and market was really missing the point.
And the last paragraph
"Disruptive innovation is a theory about why businesses fail. It’s not more than that. It doesn’t explain change. It’s not a law of nature. It’s an artifact of history, an idea, forged in time; it’s the manufacture of a moment of upsetting and edgy uncertainty. Transfixed by change, it’s blind to continuity. It makes a very poor prophet"
I think its more than just that. It talks about how people adapt to changes and how the needs interact with supply of products, services and even resources. Thats how fracking and shale came about isnt it and author is saying it doesn't explain change? Saying disruptive innovation is a poor prophet is just inaccurate. It may be because the timeframe is off, observations are off or the space itself is off. I wouldn't shrug it off just like that...
Most times, it isnt really about how much calculations you make because the permutations and combinations are almost infinite and one could never yield anything useful with the current state of computing.
Im currently working on a start-up and can relate to this.
The truth always hurts and people worry that their dreams will be dashed or the need to correct things early on which is most times, tremendous hard work (But it becomes crazy amount of effort if the change is much later on).
I targeted a low price, sales-free model, until i realized cost is not the key issue, getting feedback is! Hearing what people want and need is crucial! Its the reason why small firms are more nimble, simply because they move fast and are able to change rapidly from the feedbacks they received. Also important is that through talking, I noticed many times, people not only like to share painful experiences, they kind of impart their "ideal state" solution to you which can be incredibly helpful from a different perspective standpoint as well as a imaginative point.
In fact, I would rather spend more time talking to people in person (which I am doing now) than to rub shoulders and network.
Its like delayed gratification. Have incredible amount of pain upfront so there will be less (much less) hiccups later on in development.