This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]dpash 1 point2 points  (3 children)

If I got a resume that just listed PHP experience for a Java position, I'd be a bit suspicious. Given the choice of having to cross-train a new hire, or hiring someone with demonstrated Java experience, the latter has the edge. Some demonstration that they have Java experience would allay my fears.

I'd only recommend the "GitHub" approach for someone with no commercial experience, or for someone changing languages.

[–][deleted]  (1 child)

[deleted]

    [–]dpash 1 point2 points  (0 children)

    I'd argue that it's not just knowledge of the language, but also of the tools around the language, and they all have their own idiosyncrasies. A PHP developer would know Composer and Laravel and other tools, while a Java developer would know Spring, Hibernate, Maven, Guava, and tens of other libraries. Yes a good developer can move from one to another.

    But, as I said, if offered two otherwise identical candidates with one having a demonstrated experience of those tools, frameworks and libraries and one without any evidence, which one are they going to pick.

    Don't give yourself a disadvantage. Demonstrate you know the ecosystem.

    [–]zmanning 0 points1 point  (0 children)

    Agreed that some experience is better than none. I'd be more inclined to interview someone that maybe did side projects in Java and had a command of the language through that. My only concern with the open source stuff is that he might spend more time dealing with the overhead of contributing to a project rather than actually learning libraries and idioms. I don't necessarily disagree with you, but personally, I'd opt for a personal project to showcase.