Could use a lot of the statistics Evan showed to clients and business owners to make them allocate time for performance optimization.
I really appreciate Amit stepping in giving this talk. It is interesting information, and the discussion afterward was almost more useful. He acts in that moderator role well.
This is a good overview of a few various strategies of mobile development using JavaScript. Steve is a good speaker and is passionate about what he's doing. My only recommendation is to limit the examples to a couple frameworks and expand on the examples and process. I think this could help focus the attention on how to build these apps versus just how many choices and different ways of doing things there are.
Also, try to not rely on the Internet working!
Very cool examples.
This is the 3rd presentation I've seen on this topic (both others at large conferences) and this was the best. Such a natural speaker, and the material was a great mix of immediately accessible and references to where you can dig deeper. He had to rush through automation a bit but still clear/concise overall.
Thanks for the feedback, Jordan. Definitely a topic worth a deep-dive on the rendering side in particular.
All good information, some a bit basic, but necessary. I was hoping to see a bit more on advanced tools / processes.
Also, Evan seems to discount his knowledge a lot. That detracts somewhat from his authority on the material - although he seems to be knowledgeable. Also, not a comment on his content, but don't rely on the Internets. ;)
Very Helpful and easy to follow. As a beginner and having graduated from the most recent cohort at the Nashville Software School, I learned the practice and importance of TDD as it pertains to backend development. However, I was ignorant to applying this to JS. Covering the importance of Namespace, lowest-level testing, and the available tools to use in this talk was very helpful for me personally as I grow as a developer.
Take Aways:
- Write testable code
- Write code that's easy to pinpoint bugs to specific functions
- Refactor your testable code
- Actually Test your code
- Keep actively testing your code as you make changes
- Blame IE (insert sarcasm)
Enjoyed the amount of demos and story.