1–6 of 6 posts
I’m pretty confident there will be learning curve to deal with, but also potentially more separation of skills.
Great to understand people’s experiences and how to best organise the team and dev process to better use these frameworks.
I cannot really offer exact things you can use , but I can share some insights , as we are also in a similar situation.
As you have mentioned that its Angular.js project , I am assuming you will have an internal API , make sure there is a clear API Doc .
For inspiration :
https://github.com/wordnik/swagger-spec
http://developer.wordnik.com/docs.html#!/
You really cannot expect a backend developer to learn Angular.js just like that.
I hear this a lot, "I have completed the back end work and waiting for the front end guys to do it" .( can be the other way also , but they can always use mocks ). This is where proper planning has to be done.
it will be good to have a generalist who can contribute to both the front end and back end.
will try to add more info after a while .
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…
this will have a high impact on the complete dev process ( at least in the beginning ). I cannot really offer exact things you can use , but I can share some insights , as we are also in a similar situation. As you have mentioned that its Angular.js project , I am assuming you will have an internal API , make sure there is a clear API Doc . For inspiration : https://github.com/wordnik/swagger-spec http://developer.wo…
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…
Good 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