It is totally possible to create an Angular application, even a "large appliation", by only using one module. So why do we even have named modules in the first place, and when do you really need to use different modules?
I was recently viewing the Pluralsight course Making the Business Case For Best Practices by Erik Dietrich, and I really found this to be an excellent slide. This is Erik's view of the common best practices in software development today, and in my descriptions below I'll try to explain how these ideas can be applied to Angular front-end development.
Last night I went to the "GothamSASS" meetup group event at the ThoughtWorks NYC office (which is awesome by the way) which was about Visual Regression testing.
The posts on this site are written and maintained by Jim Lynch. About Jim...