OpenWest 2015
6 - 9 May 2015 at Utah Valley University

Great talk! They pulled off both legible code examples and live coding.

Enjoyed the talk. The diagrams were very informative.
Could you post a link to the slides for your talk

Thanks for the feedback Jarrod! Sure thing, I've attached the slides above.

Good talk and presented very well. I did not anticipate the Angular-only examples. I would have preferred more high-level discussion about Flux applied to multiple frameworks (React included), and less low-level dive into only Angular.

Also would you post slides? I specifically want to see the book recommendations. There was one book mentioned that I wanted to get but can't find.

I was a little confused by the title - "the next 42" part. I was expecting advanced directives but got intro to directives. In retrospect, the session description does indicate intro to directives.

As an intro to directives this was good.

Gave me a good idea of what Docker does and how it would be useful to me. Just what I was looking for in an intro.

When I read "enterprise-grade app" and "100-line demos" and "code base remains maintainable" I was expecting some tips on how to organize and manage a very large AngularJS project. I'm currently working on transitioning a very large one page app to Angular and these are some of the questions I have:

- What are some good ways of organizing files in a very large Angular app?
- Is there a size at which lazy loading of code starts to make sense? How and why would you incorporate AMD/CommonJS?
- If you aren't going to lazy load, would it make sense to break a large one page app into multiple smaller one page apps? How to organize this.
- How to effectively route a very large app. How does that change if your very large app is actually a collection of smaller apps?
- How to best modularize the code to share as much as possible across projects. How to manage modularized projects.
- When to use directives instead of composed controllers/views. Managing large numbers of one vs the other.

Like others, much of the first part of the talk was old information for me and I tuned out. The end had some useful thoughts. Not necessarily novel, but they applied well to the problems I wanted to address with this topic. For example: start small and release often, don't optimize prematurely, use tools that will help in refactoring (Clojure in their case).

Ultimately, enterprise in this case meant 20,000 lines of data in a table, not 50 different views in a one page app with potentially 100s of directives.

Went to this talk because I have a similar device on the way that I kickstarted (Onion Omega). Was very informative and has me excited for my hardware.

Great session. Very informative. It has me really excited to use this in my projects. The presentation and the Q&A gave me everything I needed to get started.