3 ms·

I am stuck in a hiring war-room for the last 2 weeks (two to go). [1] We are using jQuery/EmberJS/Bootstrap/Grunt. Everyone of the FEs agreed that experience i

I am stuck in a hiring war-room for the last 2 weeks (two to go). [1] We are using jQuery/EmberJS/Bootstrap/Grunt. Everyone of the FEs agreed that experience in any JS MVC was acceptable. [2] So while I agree that it's not JS, JS, JS but it's not quite as bad as what you're saying. -------- [1]: We were having a problem getting front-end people so they had managers put 15 front-end engineers on the task full time for a month. Our mandate is 30 engineers in 30 days. [2]: sdumas [at] yahoo-inc [dot] com if your looking!

jared314 13y ago
> We were having a problem getting front-end people so they had managers put 15 front-end engineers on the task full time for a month I have never heard of a hiring war-room or lockdown of that type. Are you redesigning/improving the current process, or just interviewing people until you meet the quota?
- shawndumas 13y ago
  both and. the talent acquisition folk were very interested in how the engineers went about finding people. they shared all of what we were doing with the other talent acquisition people at their all hands meetings.
davidjnelson 13y ago
It's a real shame you guys chose ember over angular. Why did you do that?
- shawndumas 13y ago
  lol, tons of reasons... a few off the top of my head; routes are central to EmberJS and are key to SPAs. AngularJS uses primitives as models which means that at the kind of scale we are hitting in our apps performance suffers (dirty checking 10k rows is killer) (also, computed props are easy, and we're into UAP). EmberJS' caching rocks. But the big one is -- Google. When are they gonna pull the plug on AngulerJS, how broad is the contribution base outside of Google, and not using YUI was already a battle...