First of all, thank you all for your answers.
To summarize your answers: You say, one need to offer good working
conditions and high salary to attract good programmers. And you say,
including a test in an advertisement would not increase the quality of
the candidates, right?
In my opinion, the
I think Rod Johnson might have a vested interest in saying such a
thing.
Personally, I see nothing wrong with using/investigating EJB3/3.1.
It's majorly improved over the 2.x stuff.
I believe the real issue is: by default most people have gone to
Spring and think DI is the bee's knees. It's not
On Tue, Mar 31, 2009 at 02:25:15PM -0700, Tim Büthe wrote:
At our company, we are looking for good Java programmers, that the one
and only requirement and that's written in our job advertisement.
Since we need more people to handle all the work that's coming up,
within this and the next year,
I completely agree with this line of thought. Get them to write code. If
they balk, then you know not to go further.
I ask people to shuffle the contents of an array. I give you an array of
objects and I want them back in some random order. Essentially shuffling
cards. I have gotten log n^2
I'm interested in knowing more about JSR 305 too.
It looks like the code is hosted on Google Code here:
http://code.google.com/p/jsr-305/source/checkout
The code has a pom.xml file, so it appears to be buildable with
Maven. That's good news for me, since my projects use Maven, but even
better
Being an EJB 3.0 user (and previous Spring user), I still think Spring has
the upper hand in terms of architecting an application. EJB 3.1 is closing
this gap, but it's more a matter of how soon can it do so vs. how many
people are jumping ship.
Right now EJB 3.0 is a box. IF your app fits in
the minimal overhead of setting up Spring (and with annotations it
really is just a few things) is worth it since even small apps become
bigger apps. Retrofitting later would be a pain
R
On Thu, Apr 2, 2009 at 2:18 PM, Rob Wilson - BabyDuke JUG
netp...@gmail.com wrote:
An interesting
Josh
On Thu, Apr 2, 2009 at 10:00 AM, Josh Suereth joshua.suer...@gmail.com wrote:
Being an EJB 3.0 user (and previous Spring user), I still think Spring has
the upper hand in terms of architecting an application. EJB 3.1 is closing
this gap, but it's more a matter of how soon can it do so
On Thu, Apr 2, 2009 at 10:14 AM, Rakesh rakesh.mailgro...@gmail.com wrote:
the minimal overhead of setting up Spring (and with annotations it
really is just a few things) is worth it since even small apps become
bigger apps. Retrofitting later would be a pain
Agree. Spring is not
I use EJB3 along with the JBoss Seam framework and it suits all of my needs
very well. I agree that it is a bit bloated for smaller apps, but it is
easy to configure, powerful, and Seam includes an arsenal of front end JSF
widgets bundled with the RichFaces project. Don't get me wrong, Spring
On Thu, Apr 2, 2009 at 4:36 PM, Josh Juneau juneau...@gmail.com wrote:
I use EJB3 along with the JBoss Seam framework and it suits all of my needs
very well. I agree that it is a bit bloated for smaller apps, but it is
easy to configure, powerful, and Seam includes an arsenal of front end JSF
On Thu, Apr 2, 2009 at 10:36 AM, Josh Juneau juneau...@gmail.com wrote:
I use EJB3 along with the JBoss Seam framework and it suits all of my needs
very well. I agree that it is a bit bloated for smaller apps, but it is
easy to configure, powerful, and Seam includes an arsenal of front end
TBH It's mostly because the shop is more comfortable with EJB. I think
we're still in it's sweet spot but only because every time we venture out
of the sweet spot, it hits us with a large, blunt hammer. Like I stated
before, EJB + Seam is almost nice, however we went a different route for our
The mac doesn't have a registry because of an ingenious system that is
IMO much superior to either linux or windows:
active disk watch.
Anytime any mac application shows up anywhere on disk, the OS will
quickly read out the app's info file and check which files it can
handle. From that point
Salary is one option, but now you're excluding truly competent people
who really so far haven't fetched that kind of salary (for example
because they've been involved with startups so far, or are fresh out
of college), and they don't really know you're looking for folks just
like them.
A second
All,
I think that this is a fantastic discussion.I wanted to throw in my two
cents:
I think that if you require applications to submit a sample application
before
and interview, you will scare away the good developers. In my experience,
most good developers in my experience switch jobs
That's not my experience at all. Talented developers welcome the chance to
demonstrate their skill. The only people who are offended by the idea of a
(basic, simple) programming challenge in the interview process are, in my
experience, prima donna programmers (What? You're questioning my coding
While it's always nice to see some code from a potential employee or
contractor, I think the person writing the code should also be valued - if
you like the code or not. Giving them appropriate feedback about what they
turned in would be a good start. No answer or I did not like your exception
On Thu, Apr 2, 2009 at 8:25 PM, Ruben Reusser rube...@gmail.com wrote:
While it's always nice to see some code from a potential employee or
contractor, I think the person writing the code should also be valued - if
you like the code or not. Giving them appropriate feedback about what they
And to add to that. It's not the people that can't sort an array that
does the most damage to your code. It's the people that can do it with
a horrible mess of unreadable and unmaintainable code.
I have seen people capable of fantastic algorithms and wizardly
knowledge of computer science theory
Marcelo,
It sounds like what you are really asking is why would people use EJBs
over Spring. This question is easy to answer, my last two employers
forbid the developers from using Spring (one company limited open
source software and the other had ideological problems with Spring).
I haven't
On Thu, Apr 2, 2009 at 9:52 PM, Ryan Waterer aguitadel...@gmail.com wrote:
Do you know why your previous company, or any other for that effect
would want to limit open source software?
A company that I've worked at in the past had this belief that if they
didn't pay for the product,
then it
A couple of years ago I was interviewed for a .NET workshop. Ultimately, I
didn't end up working there for logistical reasons, but I was offered the
position. One thing I liked about their process was that they involved their
engineers, not just the managers and team leads, and one of their
Viktor,
Isn't that the truth!
I can't believe the murder that some third party solutions get away with.
On Thu, Apr 2, 2009 at 1:55 PM, Viktor Klang viktor.kl...@gmail.com wrote:
On Thu, Apr 2, 2009 at 9:52 PM, Ryan Waterer aguitadel...@gmail.comwrote:
Do you know why your previous
On Thu, Apr 2, 2009 at 3:55 PM, Viktor Klang viktor.kl...@gmail.com wrote:
On Thu, Apr 2, 2009 at 9:52 PM, Ryan Waterer aguitadel...@gmail.com wrote:
Do you know why your previous company, or any other for that effect
would want to limit open source software?
A company that I've worked at
On Apr 1, 10:25 am, Vince O'Sullivan vjosulli...@gmail.com wrote:
The problem you have applies to all recruitment and is probably
insoluble. You are looking for sub-set of exceptional programmers in
a pool of all abilities. So is everyone else. If demonstrable
techniques existed to
Check out this special announcement from the Java Posse.
The company i work for didn't necessarily think open source was crap,
they were more afraid of being sued.
On Apr 2, 1:52 pm, Ryan Waterer aguitadel...@gmail.com wrote:
Do you know why your previous company, or any other for that effect
would want to limit open source software?
A company
On Apr 1, 8:19 pm, Yogurt Earl yogurte...@gmail.com wrote:
Check out this special announcement from the Java Posse.
http://javaposse.com/?search_string=%53%70%65%63%69%61%6c%20%41%6e%6e...
Is that a subtle way of pointing out a XSS bug?
--~--~-~--~~~---~--~~
So far in this thread, no one has mentioned vendor independence as a
pro for EJB3. Why do people not care about this? Is the general
feeling that this is a myth? With EJB3 and JEE, I can move freely
from Websphere to JBoss to Glassfish, etc. This seems like a really
big deal. With Spring, I
30 matches
Mail list logo
