3 ms·

"And whar are no-no factors for angular? Teams with varying experience. Projects, which are intended to grow. Lack of highly experienced frontend l

"And whar are no-no factors for angular? Teams with varying experience. Projects, which are intended to grow. Lack of highly experienced frontend lead developer, who will look through the code all the time." I am greatly interested in learning what is the alternative that would be a 'yes-yes' in these bulletpoints.

weavie 12y ago
I don't really see how any of these are a problem with Angular specifically and not just a general problem with any development. With any team that has varying experience, the beginner developers are more likely to write bad code regardless of the framework. You need to be careful with any project that is likely to grow.. it's called technical debt. You always want someone experienced with the domain to look through the code. The solutions include, coding standards, code reviews, pair programming, refactoring, automated tests.. all the usual agile suspects.
antihero 12y ago
I'm checking the first two boxes with React/Flux. Having an experienced developer is usually a good thing, though.
sytelus 12y ago
This kind of distorts the issue here. The problem is not lack of highly skilled devs but rather the fact that you need highly skills devs to digest and maintain the level of complexity that Angular produces. I'm big believer on light frameworks that does least amount of abstractions and can get out of way if you need. You definitely want to avoid frameworks that claims to abstract everything away and especially those that requires to learn entirely new way of doing pretty much everything and its own world of lingua franca. My preference therefore gravitates towards lighweight stuff like KnockoutJS and likes. Any average dev can understand KnockoutJS in just hour or two. More importantly, most devs can immediately have intuitive understanding of how things work under the hood and therefore can anticipate performance issues or easily extend it.
- Cthulhu_ 12y ago
  You don't need highly skilled devs, you need a disciplined team - which should review each other's members' code, stick to a style guide, research best practices, etc. Like with every software development, actually.

weavie 12y ago

I don't really see how any of these are a problem with Angular specifically and not just a general problem with any development. With any team that has varying experience, the beginner developers are more likely to write bad code regardless of the framework. You need to be careful with any project that is likely to grow.. it's called technical debt. You always want someone experienced with the domain to look through the code. The solutions include, coding standards, code reviews, pair programming, refactoring, automated tests.. all the usual agile suspects.

antihero 12y ago

I'm checking the first two boxes with React/Flux. Having an experienced developer is usually a good thing, though.

sytelus 12y ago

This kind of distorts the issue here. The problem is not lack of highly skilled devs but rather the fact that you need highly skills devs to digest and maintain the level of complexity that Angular produces. I'm big believer on light frameworks that does least amount of abstractions and can get out of way if you need. You definitely want to avoid frameworks that claims to abstract everything away and especially those that requires to learn entirely new way of doing pretty much everything and its own world of lingua franca. My preference therefore gravitates towards lighweight stuff like KnockoutJS and likes. Any average dev can understand KnockoutJS in just hour or two. More importantly, most devs can immediately have intuitive understanding of how things work under the hood and therefore can anticipate performance issues or easily extend it.

Cthulhu_ 12y ago
You don't need highly skilled devs, you need a disciplined team - which should review each other's members' code, stick to a style guide, research best practices, etc. Like with every software development, actually.