You will be much better off looking for a developer with strong problem solving skills than someone who's experience fits some laundry list you have. You are very unlikely to end up with a quality developer that way.See the discussion below on sites that help you fabricate, er enhance your resume to fit these kinds of lists to see why this is...

> Thank you very much for your suggestions. I seem to have> corrected the memory consumption issue, and I'm afraid the> solution was quite simple: 1) re-use 1 printStream object> throughout the code, and more importantly 2) null out my> query result objects after I am finished with each. 2)> freed up a ton of memory. > > Thanks again....One...

> PLEASE USE THE JAVA TAGS AND PROPER INDENTITION (SHOWN ON> YOUR RIGHT-HAND SIDE WHEN POSTING.> > Depending on how many times you are looping, try using a> StringBuffer for concatenation as opposed to a String with> the + operator.> > E.g.> > instead of:> > > Str str = "\"" + someString +"\"" + anotherString; > > > You do:> > > StringBuffer...

> I'm beginning to wonder if the sum total pain caused by> the box-and-arrow crowd has outweighed the occasional> usefulness of UML.Off-topic but speaking of boxes and arrows, I've been seeing diagrams like this more and more lately:http://www.w3.org/TR/ws-arch/#gsomDoes anyone think this is a useful type of diagram? I mean, does anyone look at...

> found at:> > http://www.infoq.com/news/2008/07/Only1> > "...in-depth studies of 20 companies found a 50% complete> failure rate, while another 30% were considered neither> successful nor wholly failed... Many of them had deployed> multiple successful projects, but most of those projects> were focused on just one integration problem. It was...

> The promise of the "next big thing" is essential for> sales. The whole SOA idea got somewhat sucked up by sales> and marketing and mixed with promises SOA can never> deliver on.Absolutely. This is the real problem with SOA. And it's a cycle that we seem to repeat again and again. What's unfortunate is that some really good ideas get lost in...

> James, could you elaborate on this?I'll try. > I've been having trouble understanding what the signal> might be because there really is so much noise. As Robert> pointed out, a lot of the hype about SOA involves> "repurposing" old investments = saved $$$ In my personal experience, reusing existing resources in ways that they were not designed...

If you drop picture-based models and ignore tooling for a moment, what difference, if any is there between MDA and traditional OOD?

> I'm up to my knees in vendor poo. Make no mistake: SOA,> like Web 2.0, is vendor poo. Vendors encourage the> CEO/CIO crowd to conclude that all that Legacy Code can be> "repurposed" through SOA; no re-engineering required, just> wrap it all up in our SOABlanket. CORBA went the same> way. The difference in advertised granularity is merely a>...

> Having now blood on it's fingers, SOA is likely to turn> from a hyped buzzword into a bugaboo like J2EE. ;-)> It's time for the industry to find a new acronym and swipe> SOA under the carpet to its fellows DCE, CORBA, DCOM, RMI> and the ones I have forgotten...You say this as if the technologies are the problem. The problem is with an...

> SOA, like CORBA before it, promises the Fortune X00> CEO/CIO that s/he can "repurpose" 35 year old COBOL batch> programs into a slick looking web app that the users will> just love because it allows them to continue to execute 35> year old batch business processes with a mouse. Promises of this kind of magical silver bullet are not new. There...

In all my blah-blah-blahing I neglected to point to a java based desktop app that I work on:Simbrain - http://www.simbrain.net/I have nothing to do with the current version but I am very involved in work on version 3.

> The title didn't say it was irrelevant, it asked if anyone> cared. And lots of people have responded that they do, and> have described what they are doing. So it's been very> informative.> > I personally think that desktop Java has better> opportunities with a UI system like Flex that is better at> creating UIs, while at the same time...

> The screen shots look really good. Would you mind hinting> how you got there from plain Swing?It might help if you made it clear who you are responding to.

> > > I think people overlook SWT. > > > > I was really excited about SWT until I actually tried> it.> > I hate APIs that rely on huge numbers of uncategorized> > d integer constants...> > That, in itself, is not a good reason for rejecting SWT.> It's just a development detail that you can live with.> . The primary reason for accepting or...