3 ms·

Another reason to stop hating on Java is that in a lot of cities, it would be a fool's errand to assemble another kind of dev team. Like Ruby? Great. Good luc

by a5seo 15y ago

Another reason to stop hating on Java is that in a lot of cities, it would be a fool's errand to assemble another kind of dev team. Like Ruby? Great. Good luck building a team in Omaha. Skills go where the jobs are: http://www.indeed.com/jobs?q=ruby&l=Omaha%2C+NE http://www.indeed.com/jobs?q=ruby&l=Omaha%2C+NE = 11 jobs http://www.indeed.com/jobs?q=j2ee&l=Omaha%2C+NE http://www.indeed.com/jobs?q=j2ee&l=Omaha%2C+NE = 101 jobs Bottom line: if you expect to hire developers, in most places, you'll want a language with the deepest bench of talent. The trick is to resist the Java framework nazi's and keep it simple.

onemoreact 15y ago
Unless you have horrable retention issues highering someone who does not know the language your using is not that big of an issue. Taking a C# ASP.NET developer > Ruby on rails is faster than bringing a Java developer who knows nothing about the web into a large Spring/Struts project.
- a5seo 15y ago
  That might be true for a basic/early Rails app where it's ok to have script kiddie relationship with Ruby, but if you have a more complex app, I don't think the learning curve is quite as easy as you're making it sound. My own experience with Rail is that I quickly wanted to see inside and control all of the implicit stuff that was going on, and I needed to invest a lot more time to learn Ruby to have the knowledge that would give the amount of control I wanted.
run4yourlives 15y ago
Hiring any programmer that can't adapt to an unfamiliar new language is a bad idea (TM). I'm far from a guru, but I've been able to pick up quite a few different languages, frameworks and structures over my tenure. It's the ones that limit themselves to a single language (be it Java or not) for long periods of time that you need to worry about. These are the programmers that will build a square wheel because that's what the spec told them to build. Employ them at your peril.
- a5seo 15y ago
  That's cool, but when I'm hiring a team and paying their salaries with my own money, I'm just not going to bank on transitioning anyone from X to Y. No time for it, no appetite for the risk. But if you raise VC, more power to you.

by a5seo 15y ago

onemoreact 15y ago

Unless you have horrable retention issues highering someone who does not know the language your using is not that big of an issue. Taking a C# ASP.NET developer > Ruby on rails is faster than bringing a Java developer who knows nothing about the web into a large Spring/Struts project.

a5seo 15y ago
That might be true for a basic/early Rails app where it's ok to have script kiddie relationship with Ruby, but if you have a more complex app, I don't think the learning curve is quite as easy as you're making it sound. My own experience with Rail is that I quickly wanted to see inside and control all of the implicit stuff that was going on, and I needed to invest a lot more time to learn Ruby to have the knowledge that would give the amount of control I wanted.

run4yourlives 15y ago

Hiring any programmer that can't adapt to an unfamiliar new language is a bad idea (TM). I'm far from a guru, but I've been able to pick up quite a few different languages, frameworks and structures over my tenure. It's the ones that limit themselves to a single language (be it Java or not) for long periods of time that you need to worry about. These are the programmers that will build a square wheel because that's what the spec told them to build. Employ them at your peril.

a5seo 15y ago
That's cool, but when I'm hiring a team and paying their salaries with my own money, I'm just not going to bank on transitioning anyone from X to Y. No time for it, no appetite for the risk. But if you raise VC, more power to you.