4 ms·
It definitely has some impact. From my [limited] experience it seems you'll need one person to really deeply understand Angular to be your team guru and Angular
by auganov 12y ago
It definitely has some impact. From my [limited] experience it seems you'll need one person to really deeply understand Angular to be your team guru and Angular advocate. Angular might take a bit to grasp. If you'll have every teammate only sort-of know what's going on it will create a lot of trouble. That's surely not exclusive to Angular but from what I experienced it's easier to get away with nasty hacks in other frameworks.
Did all team members agree to use it? My primary concern would be how each team member will like it, especially if they have prior front-end dev experience.
- markwillcollins 12y agoGood point about getting a guru. We are all a bit new to it, but a good friend of mine is a guru and will help training. But this strategy has its risks. Not everyone was fully supportive, particularly a person who works mainly on back-end. Perhaps we've been a bit too directive and might need to get more support first
- thoughtpalette 12y agoDefinitely need one person intimate with the framework or they'll be a lot of mistakes made along the way. The backend guy (if he's not working on FE) should just be building an API for the Service/HTTP calls. He should have a very easy time. There is a lot of communication between the BE dev and FE dev on Models though. We'd usually have our FE guys implement a mock model for testing and implement it in (at the time) C#.