> I think yours is a dangerous attitude, I've seen a lot of mess produced by people who come in to angular knowing other frameworks and their output is terrible

> I think yours is a dangerous attitude, I've seen a lot of mess produced by people who come in to angular knowing other frameworks and their output is terrible. > > Part of that is because angular is different, it's not very nice and it has obscure knowledge needed to make it play nicely with unit testing. A possible approach is to let developers new to a framework on a prototype or toy project first, and, very important, throw away that prototype. Yes, that means you might have to wait two or three weeks longer until you get started with the real project, but the result will be so much better. But that's one of the prices you pay for using an immature technology. For a more mature one, you could read a book on successful usage pattern of the technology.