[gnrlbzik]

Well I can relate to notion. Not to the exact manner. But when I had a small team and we worked on app, about 2.5 years ago. I would say that general premise was in regards of PRs that i have reviewed, is that more junior devs, would over populated logic in templates and in general just do little bit of extra code in places where it should of not existed. That said, I think it is applicable to any junior developer, when documentation is a bit convoluted. I can't say that Angular has the best documentation and has no ramp up time to get on board with it, if anything it has longer ramp up time. Especially if you start from scratch as a team.

[robertthegrey]

You've hit the nail on the head, but I honestly don't know why more senior developers can't see it - unless they don't actually work with juniors on a regular basis? Anyway, due to all the cries about FUD on the topic of juniors specifically, I decided it needs its own writeup - you can find it here if you want more clarification: https://news.ycombinator.com/item?id=8965935

[craigching]

Actually I work pretty closely with my juniors and teach them the right way to do it. That and provide a code base of conventions that shows them the right way to do it. It's really hard for me to understand how you let juniors get to the point of having bad habits. If you see them doing something wrong, let them know, provide them feedback telling them why what they did was wrong and show them how to do it right. It's really not that hard, just part of the job.

Any technology (not just Angular) has the potential to be misused. As a senior developer/architect it's my job to review and mentor my teammates as appropriate. I don't really see this as a problem particular to Angular, it's something you have to watch out for everywhere.

[gnrlbzik]

Well thats the goal of PRs : ) But its not one time affair, and takes time and investment from your self. So I like to think that I have done right by devs i worked with, helped them out a lot, gave them freedom and responsibilities. It paid off for those who stuck around.

Bottom line, it depends on so many things and so much time, to bring everyone on same level. And some developers are brought for only like 3 months. For a project that I ve been part of, so devs just did not like the project that they worked on, and cycled right through.

[craigching]

Thank you, that example makes sense. You see, as an experienced developer I would never think to intertwine my logic into my templates, so it's hard to envision what a junior developer might do.