Emacs...hmmm. I'm contemplating mentioning a two letter acronym that starts with V and ends with I. But Smokey told me not to play with fire, and if it came from a talking bear it must be good advice.
Regardless of which IDE you use, make sure that it's got decent integration with ant. Ant is part of the jakarta project and allows you to write build scripts in XML. Having your own scripts that can update and commit to cvs, run junit tests, generate javadoc, deploy components to application servers, etc., allows you to be much more productive, regardless of the IDE you choose. I think you'll find ant fits nicely with the other recomendations you've got so far. And if your projects rely on Ant scripts, they'll port nicely to another IDE if you decide to switch.
I don't know if I am quite that cynical. In this case, two labs a sharing the coronavirus mapping freely so that peer review can take place. Companies that want to make a quick buck aren't so quick to share. What strikes me as a bit odd is why they would bother when other researchers are only able to identify the presence of coronavirus in 40% of SARS patients. Admittedly, this might be because the virus doesn't hold up well in the lab, making it difficult to identify even when present. But it's got a bad smell about it.
I don't think I've ever been broad-sided by a bad hiring decision. When I've made mistakes, it has always been because I was in a hurry to find staff. My strategy is to try to put the interviewee at ease and then find out what they like about being a developer. Then I listen. If the hour goes by quickly and I feel the candidate is enthusiastic about writing code, and critical about the work they have done previously, I put in a recommendation to hire. If I have any doubts, if the interview was just OK, I pass. If you feel you have to resort to gimmicks, you probably haven't found the right candidate yet.
Slashdot Mirror
My guess is that the Metadata he's talking about is Sun absorbing the xdoclet project into the base language.
Emacs...hmmm. I'm contemplating mentioning a two letter acronym that starts with V and ends with I. But Smokey told me not to play with fire, and if it came from a talking bear it must be good advice. Regardless of which IDE you use, make sure that it's got decent integration with ant. Ant is part of the jakarta project and allows you to write build scripts in XML. Having your own scripts that can update and commit to cvs, run junit tests, generate javadoc, deploy components to application servers, etc., allows you to be much more productive, regardless of the IDE you choose. I think you'll find ant fits nicely with the other recomendations you've got so far. And if your projects rely on Ant scripts, they'll port nicely to another IDE if you decide to switch.
I don't know if I am quite that cynical. In this case, two labs a sharing the coronavirus mapping freely so that peer review can take place. Companies that want to make a quick buck aren't so quick to share. What strikes me as a bit odd is why they would bother when other researchers are only able to identify the presence of coronavirus in 40% of SARS patients. Admittedly, this might be because the virus doesn't hold up well in the lab, making it difficult to identify even when present. But it's got a bad smell about it.
I don't think I've ever been broad-sided by a bad hiring decision. When I've made mistakes, it has always been because I was in a hurry to find staff. My strategy is to try to put the interviewee at ease and then find out what they like about being a developer. Then I listen. If the hour goes by quickly and I feel the candidate is enthusiastic about writing code, and critical about the work they have done previously, I put in a recommendation to hire. If I have any doubts, if the interview was just OK, I pass. If you feel you have to resort to gimmicks, you probably haven't found the right candidate yet.