Re:Ask HN: Enterprise Java guy needs advice on what to trans...
by alavrik on Thursday May 05, 2011 @05:30PM
(#2518984)
> The language/tools are not the problem, it's the people/organization.
The language is a problem, because Java was specially created for this type of organizations. And it is not surprising that Java attracts this type of people (fungible crowds having no pride in their craft).
Re:Ask HN: Enterprise Java guy needs advice on what to trans...
by brown9-2 on Thursday May 05, 2011 @05:51PM
(#2519044)
I disagree that it's possible to paint all developers using this language with such a broad brush. By this notion everyone that uses Rails loves being a "ninja" and monkey patching.
Re:Ask HN: Enterprise Java guy needs advice on what to trans...
by alavrik on Friday May 06, 2011 @05:03PM
(#2522480)
My comment was about the language, not the people. I have no doubt that there are many good programmers who use Java.
But I'm not sure one can be a good programmer if Java (or any other mediocre language) is the only thing she knows.
If this is the type of thing you want to move away from, then I don't think that the problem is teams that use Java - the problem seems to be working for large enterprises.
I suggest that as a first step, ignore any questions of language/platforms/tools and instead think about what type of company you would like to be working for: a small start-up, a more-established medium size business, etc. Do you want to work in a place where the primary business product is software (i.e. a software development company), a place where software is something that is done in support of the primary product being sold, or are you interested in consulting for others?
Once you decide what type of environment you'd like to work in, then the rest of the decisions follow naturally from that.
As a single anecdote, I work for a medium-to-large software-as-a-service company business where most of our work is in Java, but we are very far from the notion of monolithic apps with 1M LOC and offshore teams.
The language/tools are not the problem, it's the people/organization.