Answer the question
In order to leave comments, you need to log in
Practice with AngularJS?
Hello.
I've been working on the web for a long time, I'm a freelancer, I have a very solid rate on upwork.
I have already devoted 150 hours to studying with Angular, but for some reason I am afraid to take a real project with my high rate. And in general I'm afraid, no practical knowledge at all.
Tell me, does it make sense to take a project in Angular with a rate 3-4 times lower than my current one, just for practice, so that there is an experienced team leader who, if anything, will show and tell? Well, purely for practical experience.
Or is it better to take some kind of coaching from an experienced senior angular?
Answer the question
In order to leave comments, you need to log in
options:
- a project with a team of experienced anglers, where there is a review code. It seems to me that this is a very rare case, but as for me the best.
- hire a person with experience to do a code review and tell you how. There are risks of running into the opinion of one particular person. Angular can be prepared in many different ways.
- join some chat (like frontend ua, etc.) and terrorize the community with questions about who cooks what and what problems you might encounter. Cheap and cheerful. You can even agree on a code review from a couple of people. Sharing experience and knowledge is good.
- dig into more modern solutions (for example, reactjs + redux), in order to have a more complete idea of how to prepare Angular and get a more complete understanding of the shortcomings of the first branch (in the second, there are no problems like imposing a two-way date binding, but the second Angular is still in beta and I would not recommend using it for commercial projects for at least a couple of months). Everything the same as in React can be done in Angular, it’s just that there are places in the first branch that are not very beautiful. Maybe they will even fix it in version 1.5, but so far it is doubtful.
Well, yes - I recommend coding in angular1 with an eye on angular2. stateless components, one-way data flow and all those trends that all popular frameworks use. Well, at least write everything on ES6 (babel) and bundlers like webpack or system.js, it’s more convenient to cook angular with it. Example . Well, tests, then the risks are less.
Coaching is great when combined with practice. Therefore, of the two proposed - IMHO the first option is better.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question