<story><title>AngularJS Style Guide</title><url>https://gocardless.com/blog/angularjs-style-guide/</url><text></text></story><parent_chain></parent_chain><comment><author>MaybiusStrip</author><text>I still don&amp;#x27;t understand why everyone recommends different folders at the project root for controllers, directives, services, etc... You end up with closely related code being far apart. It&amp;#x27;s a thoughtless way of dividing up your files based on the most obvious feature rather than how things actually fit together.&lt;p&gt;My idea of a good modular file structure is that you could delete any random directory and delete it and it would lop off that feature as cleanly as possible. Each directory should represent an angular module, and each module should contain the routing, controllers, services, directives, and tests that it uses. If some of these are used across the app then you can have a &amp;quot;common&amp;quot; module.</text></comment>
<story><title>AngularJS Style Guide</title><url>https://gocardless.com/blog/angularjs-style-guide/</url><text></text></story><parent_chain></parent_chain><comment><author>MrOrelliOReilly</author><text>Very helpful. I&amp;#x27;ve unsuccessfully search for a way to do one-time binding before in a data intensive application and never came across the {{::ctrl.foobar}} syntax.&lt;p&gt;One thing I&amp;#x27;m hesitant about is their advice to use directives instead of ng-controller=&amp;quot;MyCtrl&amp;quot;. Since controllers really are app specific glue code I rarely find myself wanting to reuse them - what advantages are directives supposed to give here?</text></comment>