--- In [email protected], Nick Collins <ndcoll...@...> wrote: > > I think you should have a functional knowledge of several backend languages > with which you might interface. Java of course, is the biggie, but also > Ruby, C#, Coldfusion, maybe Python... which is not to say that I think it is > necessary to have experience architecting the entire back end from scratch. > You should, however, know enough to be able to read the code given to you > and know what you need to do to interface with it.
Bottom line, it doesn't matter what _you_ think (or I think for that matter). Only what the recruiter/hiring manager thinks. And that means that if you're not an EXACT match for what's on that sheet of paper, you are SOL. Because they don't know that ASP.Net=backend and Java=backend, so if you know ASP.net you already have a lot of foundational knowledge that can be applied to Java (or vice versa), or that MySQL is a database and SQLServer is a database, so knowledge in one carries across to the other. They also do not look at resumes and say "Wow! He/she has picked up a lot of languages to a fair amount of depth in x years. He/she can probably be up to speed in pretty much anything quickly." I think this is because life as a hiring manager or recruiter doesn't really involve the skill of learning large bodies of knowledge quickly, so they can't really recognize it as a skill. And even if they could, could they then turn around and sell that skill to a hiring body that probably doesn't really see that either? JMO; Amy
