16. A Brief Personal History
•Born in Atlanta, grown in Birmingham, AL
•Auburn University - Computer Science
•Currently in Orlando, FL
•Largely working with Ruby, Python, Rust,
18. How Did I Get Into Ember?
•Popularity among Ruby and Rails folks
using Ember for their products.
•A lot of my early gigs involved writing APIs
for Ember apps.
•Started actually writing Ember in
professional context at IZEA.
21. What’s Going on at IZEA
•We’re slowly taking apart of Rails view
layer and converting into an Ember
frontend. Right now, that involves
injecting Ember into our view layer -
not replacing it.
•While a lot of our team constantly uses
Ember, there are still people we’re
teaching and training.
•This includes new hires and long-time
Rails monolith w/ injected Ember
New project w/ completely new
We sort of inject the new app into
Its kind of weird, right now
No more Rails monolith
100% Ember frontend supported by
No more injection
Lord haste the day
24. We’re pretty
invested in Ember.
The point of all of this is:
And we don’t plan on slowing down
this investment anytime soon.
25. IZEA is looking for more
Engineers to help us
achieve higher goals
26. Your Company is likely
looking for more
Engineers to help you
achieve higher goals with
27. “Well, why don’t you just hire more
Its tempting to think is the right
answer to your stafﬁng needs.
28. You can’t just throw people at a problem.
Really good book
This remind me of…
30. You can hire more
developers, but you
have to teach and
takes a bit longer to pay
off - in terms of results.
31. All of these things assume
that you have a vibrant
talent pipeline outside
your front door.
32. Its not all about trying to
hire within your salary cap
33. At IZEA,
We Hire Local To HQ
This somewhat restricts the
immediate talent pool we can
Speciﬁcally, if you’re looking for a
really good Ember developer and
your HQ is in Orlando.
37. Taking Small Bets
• For us, the idea of integrating Ember into what we did was
a pretty big deal. We started small as a trial to see if it
• As we scaled our investment, we began to slowly teach
and draw in new developers to this eﬀort.
• This allowed for teaching in a smaller setting rather than
“just read the docs because we’re all busy here”
Let’s look at two types of JS Developers:
44. JS Newbies
have a pretty good opportunity to help introduce its ideas.
• Ember has opinions, but they’re less controversial if you really
don’t have anything that challenges it.
• Ember not only has opinions to learn, but you also have to teach
• The learning curve can be quite high because of lack of
45. JS Veterans
hard time ushering in Ember’s way of thinking with issues
have issues dealing with those opinions plus explaining
• Learning with happen faster, but your experience may
vary depending on their general attitude towards learning
•The core ideas of Ember
•The core toolset and the opinions or
requirements that exist behind using them.
•To fully understand, we’ve got to dig a bit
48. Newbies + Foundations
•Are impressionable since they likely don’t
have much to compare to.
•Should be limited in exposure until they
actually dive into Ember for a bit.
•Follow up after some initial Ember work
has been done.
49. Veterans + Foundations
•Less impressionable and likely more
•Foundations might need to be explored
more upfront in order to sell and pitch
what the beneﬁt of using something like
•Not much followup needed on concepts.
•Things that make Ember stick out in the
•Things that are buzz worthy but not really
core to what makes Ember unique.
51. Newbies + Features
•Often confuse them with the foundations.
•Might become a bit dependent on them
without understanding the foundation
52. Veterans + Features
•Features help cement why the foundations
•Can tell between feature and foundation
but may not be as sold on every feature.
56. “I’m Used To React”
• Common threads around the idea of Components and the React
• Ember’s design patterns are much more structured than React’s.
Redux is possible with Ember too!
• No more Webpack
• Ember Data and the idea of data modeling are a lot more
structured than React.
58. I’m Used To Angular
• Explaining the consistency of Ember vs the drastic depreciations
• Moving away from Webpack
• Shared ideas around Controllers, Routers, and Services
• Component-based ideas might come oﬀ as foreign
60. “I Used Ember 5 Years Ago”
• This is something not a lot of folks think about.
• While a lot of Ember has stayed the same, a lot has changed.
longer require that “brute force” approach
• Conversely, API methods that were previously available may or may
not be around.
• ES5, ES6, Whatever else is next also has inﬂuenced how Ember
61. The Context of a
Leverage This to
64. Hiring People
• How they work with people is more important than
• Looking for people who are both teachers and
• Looking for people who will make a positive impact
on team culture. Doesn’t always mean “culture ﬁt”
65. Hiring Skillsets
• More concerned about hiring [x] skillset for [y]
• Concerned about how open they are in
working on things.
• Looking for people who can make a positive
impact of creating products - results.