lots of people have this dirty secret. lots of well-seasoned programmers to be certain. I find when writing in scripting languages such as ruby against framew

lots of people have this dirty secret. lots of well-seasoned programmers to be certain. I find when writing in scripting languages such as ruby against frameworks that are in constant flux, I have little choice but to write tests against key things like user registration, activation, authentication. I wrote a webapp in erlang 4 years ago. I felt the code "was" the tests since my erlang code was concrete and well guarded. I never had any surprises between test and production. This is not to bash the value of scripting languages. Its a "pay now or pay later" problem. So what about Java? Its static typed so I should get the same benefits as I did with erlang right (btw, erlang is not typed)? My experience tells me: 1 - ruby - "pay later" 2 - erlang - "pay now" 3 - java - "pay now and pay later"