- X 4
Anyone who tells you they are "outdated" is misinformed.
Arun Giridharan wrote:They say these things are outdated.
I don't know where you are getting this, or who "they" are. I wrote in another thread that servlets have no sizzle. They are not new or exciting. They are used all the time, and I expect they will stay in heavy use as long as Java is alive. Maybe longer, since a lot of what makes servlets work is not specific to the Java language.
I expect servlets to stay in use long after JSPs are gone. These days the sizzle is in client side stuff that talks REST to a server. This makes the presentation layer, where JSP lives, a lot less important on the server. All of my REST stuff is implemented with servlets.
leo donahue wrote:Client side knowledge of which framework/plugin? jQuery, Flex, Silverlight, something else?
Yes. Those or some others.
What are you really asking here? You need to be facile with one or more. Which one? That changes weekly. For me, only the open source ones are viable, so Flex and Silverlight are out. You may have other criteria, you may want to use a proprietary approach.
When I hire junior engineers, I want them to be really smart, and have exposure to a number of tools and techniques. I do not care if they know exactly the toolset that we are using on the particular project/assignment, since the next one is likely to use different tools.
When I got our of school, the DEC PDP-10 was way cool. I worked on it. But it was dying by the time Bear was working on the DEC Vax. And both the Vax and DEC itself were dead after a few years (well after a dozen years). You have to be able to learn new stuff and be productive at it.
Pat Farrell wrote:What are you really asking here? .... Which one? That changes weekly.
That was my point. Client side technology changes all the time and it depends on what your project is, as you have said.
In my field, I see Silverlight and Flex as the wrong choice for many projects, but you can't convince people blinded by "sizzle" of that.
On one hand, you're saying that Servlets != sizzle, but that sizzle is where it's at, in terms of getting a job. Was I wrong?
On the other hand, you say that you want to hire smart people, irrespective of whether they have experience in sizzle.
Is "sizzle" important or not?
For me, I see through sizzle and fear listing it on my resume for the fact that there are people such as yourself that would rather not hire based on sizzle alone.
leo donahue wrote:That was my point. Client side technology changes all the time and it depends on what your project is, as you have said.
But to have any client-side experience is better than none.
If I'm looking for someone to work on a project using jQuery, someone with Prototype or Dojo experience is much more interesting than someone who has used nothing.
Same on the server side. Experience with any framework is better than none at all.
I rarely hire for the exact technology -- if there's a match, it's gravy -- but on the potential of the candidate as demonstrated by their experience and grasp of important concepts.
leo donahue wrote:For me, I see through sizzle and fear listing it on my resume for the fact that there are people such as yourself that would rather not hire based on sizzle alone.
I still fail to understand what you are asking.
Its not as if its hard to have two or more resumes, tailored for the target hiring company.
Some folks making hiring decisions demand a match with the keywords du jour. I won't work for them, but others may.
Some folks making hiring decisions demand the smartest persons available, and will teach them if they have shown the ability to learn lots of new things.
I might engage a consultant based on an exact match of the tools at hand, but that's not how I hire employees.