Quote:

The best solution is always when it comes from you rather than someone else telling what/How you should do.

Humans tend to hate to be commanded to do something; even if it is right thing. One would rather fall flat on his face; redeem; be enlightened than listen to advice. Your legend probably knows this. Interesting guy. I would like to meet him somehow someday.

A big thank you for introducing me to Zoneminder. :thumbsup:

Choose one among several ways that lead to the cloud. 1. Pick a cloud provider ( Amazon and Microsoft are the two biggies ) 2. Learn their infrastructure as a service and platform as a service offerings and develop small applications with them ( You can have free credits of their cloud offerings ). Keep it public on git so that it reflects on your portfolio 3. Host your own website/blog on their free offering. 4. Build your resume with their taglines and start sending to small companies who are looking for cloud talent. See how you fare, come back and learn what you are lacking. Keep Repeating step 4 until you get your first gig. 5. Once you get your first gig, do not stop learning, keep building your knowledge. I have to tell you it is a slow and pain(ful) process till the time you get your first gig. Best of luck:thumbsup:

Rightfully said, I've known people rise to the top in terms of pay just by keeping pressure on the management for raises. Others lacked the vigor to push their agendas afraid of getting the pink slip. Take your chances. Sometimes it is better to be sorry (ephmerally) than to be safe. ;P

Let the future tell the truth, and evaluate each one according to his work and accomplishments. The present is theirs; the future, for which I have really worked, is mine

Hi Marc, Just my 2 cents for your questions 1. We got into this mess since nothing is perfect and can be bettered. Inevitably a javascript toolkit/framework will have its shortcoming, people will jump on the opportunity to fix it (albeit by spinning up a new framework). Look ma we have this new! thing that fixes the problems of that other framework. And oh btw it introduces a diff kinds of problems (which will be fixed by some other toolkit). Angular 1 -> Angular 2 -> Angular 3 React Aurelia you name it 2. If you want to believe a salesman then you have just the perfect toolkit for all your requirements. Now coming back to reality you have evaluate the frameworks purported claims against your own requirements. I would recommend having a grid listing at least your top level requirements :-D and checking off against the diff frameworks. Then pick the one which you can swallow with least difficulty. :sigh: 3. No, one can't tell if they've not used at least couple of them. I would really like to find someone who has dipped their fingers in majority of them and take their advice too. Anyone?:confused:

Thanks for the tool. Have you had a chance to use it? How did it go?

Since you're a novice first focus on what you are comfy with. Pick that layer. Pick up a tool like Ndepend or Nitriq and see how the layers interact. Then and only then start playing on the keyboard.