Our Guest this Weekend
Developer / Co-Founder at Code All Day
Katie has in-depth experience building rich, interactive web apps with modern UX. She also brings expertise in managing product development and building development teams.
Tell us a little about yourself.
How did you get started in Ember?
What type of contracting does Code All Day typically do?
Between rescues / new code / advising which do you prefer?
In rescues how often do you see no tests?
How do you help move toward testing?
What is your testing strategy when working in uncharted waters?
Are you always strict about testing?
Do you sometimes spike a solution to throw away later?
When testing Ember do you find yourself using any of the test types more than the others? (ie unit, acceptance, integration)
How do you cover the air gap between frontend/backend while testing?
What is your strategy for deploying Ember right now?
What inspired you, Louis, and Phil to write Ember Observer?
Have there been any surprises while working with Ember Observer?
What made you decide to write Ember Try?
Are there any plans on testing different versions of Ember CLI also?
What is the personal project consuming most of your time now?
What can the Ember community learn from other open source communities?
What do you think the focal point of the Ember community is?