Thomas K.

I get only advertisement content from this link. duh.

Should be as well on the list:

• testing / continuos integration available (even for a "frontend only" project)
• make sure the functional requirements explicit mention what environment should be supported (IE 6 any one? iphone is SO common it is "obvious" it has to be supported?)
• Know all deadlines upfront, what did the agency commit to to their clients, did they include buffers? (you will know when the pressure raises upfront)

After all a helpful article, I hope many contract developers will learn from it.

I wonder why GUIs should be better just because you pay for them...

Site does not exist, voting down. ,

There are even wrong points in the article: Java is ALWAYS call by value. It happens that the value is the reference-value, but is does not change the behaviour! It is even easier to explain than to confuse people with supposedly inconsistent behaviour. http://www.javaworld.com/javaworld/javaqa/2000-05/03-qa-0526-pass.html

The site had some capacity problems, this caused some "forbidden" messages. Sorry for the inconvenience, the problem should be solved soon!

10 ways to keyword-stuff an article (keywordstuff article in ten ways by stuffing keywords into article)

So, assuming I am doing an opensource project, even when I am buying I cannot bundle the Spring release with my project.

So it's no use for me buying the enterprise support. I will use the "latest and greatest" to get a fixpoint for the version number. I discover bugs - does SpringSource want me to submit it, or do they want customers to buy support tickets? (This may result in many bugreports for already fixed stuff!)

The other possibility is to use the svn commit revision as a fixpoint - sounds terrible for me, and like "we couldn't care less about the community." It's just about maximizing money.