My "Ember" Job Posting on Hacker News
gist.github.com
My "Ember" Job Posting on Hacker News
1–10 of 28 posts
Re: My "Ember" Job Posting on Hacker News
#2Interesting. I don't work for quite so sexy a company as Apple, and positions aren't going to get you working on much hot new tech, so I'm not sure I'd post "we're hiring". I assume most people here have no desire to work at boring old companies, hence the "Wtf php? Are you a noob?" type comments.
Re: My "Ember" Job Posting on Hacker News
#3Interesting. I don't work for quite so sexy a company as Apple, and positions aren't going to get you working on much hot new tech, so I'm not sure I'd post "we're hiring". I assume most people here have no desire to work at boring old companies, hence the "Wtf php? Are you a noob?" type comments.
Many "boring old companies", well, aren't. I work in Cable and could have written the same job post (subbing Ember for AngularJS in our case). In a culture where results count, and fast results count more, you may be surprised where you can look for jobs.
Edit: It's actually remarkable how close my tech stack lines up. CodeIgniter (php), node.js, JRuby, AngularJS, socket.io, d3 & highcharts, memcached (reddis soon, I think). It's a good time to be a polyglot in the enterprise space.
Re: My "Ember" Job Posting on Hacker News
#4> We're rebuilding an internal app from scratch and it needs to be blazing fast and real-time.
At risk of dragging the OP into a framework/language war...if you're building an internal app from scratch...why use Symfony? Is it because the rest of the Apple internal apps are in PHP/Symfony and it doesn't make sense to have the internal app group write in different frameworks?
(I'm assuming different languages isn't a huge deal, since the OP mentions using Ruby to handle deployment)
Re: My "Ember" Job Posting on Hacker News
#5> In my opinion [Ember.js] the best client-side MVC framework out there.
How does Ember.js compare to AngularJS and Backbone.js?
Re: My "Ember" Job Posting on Hacker News
#6Sounds like a perfectly normal professional stack to me: solid tried and proven technology at the foundation for the generic solutions, more hot new stuff around the edges to optimize for specific cases (and let's face it, sometimes just for the hell of it).
It's only the inexperienced unprofessional wannabees that bitch about anything that doesn't use all the cool new toys top to bottom, and try to solve every problem using the coolest tool instead of the most appropriate.
And the only thing "wrong" with PHP is that it's inelegant and inconsistent as language. 90% of the people bitching about PHP couldn't put two solid arguments together.
The argument that it attracts the worst programmers is no longer true since Ruby's "coolness" started attracting large numbers of less than mediocre programmers, proving publicly on Github that you can write crappy code in even the most elegant of languages.
Re: My "Ember" Job Posting on Hacker News
#7+1 for polyglot, but I find PHP in the mix strange though. Is there a reason why you think PHP/Symphony2 is the best choice?
Re: My "Ember" Job Posting on Hacker News
#8Interesting. I don't work for quite so sexy a company as Apple, and positions aren't going to get you working on much hot new tech, so I'm not sure I'd post "we're hiring". I assume most people here have no desire to work at boring old companies, hence the "Wtf php? Are you a noob?" type comments.
I assume most people here have no desire to work at boring old companies
That's a really bad assumption. It's actually very difficult to find jobs with established companies because they maintain such a low profile. I wish they would be better at promoting themselves.
Re: My "Ember" Job Posting on Hacker News
#9You can tell someone who hasn't had broad professional experience when they are aghast at the idea of a multi-technology stack like this. The reality is any company bigger than startup size is going to be using lots of different technologies for lots of different things, for a variety of reasons. Hopefully all good but sometimes not so good.
I'm curious about the choices that lead to doing the API in PHP/Symfony as opposed to Node, though. I've written APIs in both PHP and Node and it seems to me that Node has the advantage in terms of being more lightweight for the task. So I'd love to hear what Jarrod sees as the advantages PHP presents that make it a better fit.
EDIT:
Got the following response to the question on Twitter, for anyone else curious:
> I have but honestly I'm just not comfortable enough yet w/ Node to a jump. :) We're capable and productive w/ PHP. Maybe in time.
So, totally solid reason. :)
Re: My "Ember" Job Posting on Hacker News
#10Hey all, Jarrod Nettles here (hayvok - OP).
The original code base was in PHP. Very, very terrible proceduralish PHP. Since we have to continue to maintain the current system while we rewrite we can implement once and port that code (if necessary) to the new system with minimal effort.
Could I switch us to Rails? Yes, but I don't see the point. We're a PHP shop and in my professional opinion (having used both extensively) Symfony 2 is virtually on-par with something like Rails and switching at this stage of the game would be project suicide.
* If you're using Rails, and like it - stick with it.
* If you're using a good PHP framework like Symfony 2 or Zend Framework, and like it - stick with it.
You'll be just as productive and successful either way.