> I was a professional Java programmer for three years
3 years is about the amount of time it took me to get a false sense of security in my understanding of a language, imo. After 3 years i thought I knew Java. After 3 years I thought I knew Ruby. I was wrong.
BTW- if I were to receive a question on my application asking how to read stdin and write stdout, that would be a bad sign.
> So yes, I enjoyed programming in Java, and being relieved of the responsibility for producing a quality product.
Many quality products I use have been written in Java.
> It was pleasant to not have to worry about whether I was doing a good job, or whether I might be writing something hard to understand or to maintain.
Though, I understand the intended meaning of "Java is too verbose", You can write code in Java that is easier to maintain. Java is not an excuse for poorly written code.
> The code was ridiculously verbose, of course, but that was not my fault. It was all out of my hands.
You get paid to write maintainable code that does what is intended. It was never "out of your hands".
I no longer like Java as much, but I don't think Java ever was a reason to sit back and let bad code happen.
3 years is about the amount of time it took me to get a false sense of security in my understanding of a language, imo. After 3 years i thought I knew Java. After 3 years I thought I knew Ruby. I was wrong.
BTW- if I were to receive a question on my application asking how to read stdin and write stdout, that would be a bad sign.
> So yes, I enjoyed programming in Java, and being relieved of the responsibility for producing a quality product.
Many quality products I use have been written in Java.
> It was pleasant to not have to worry about whether I was doing a good job, or whether I might be writing something hard to understand or to maintain.
Though, I understand the intended meaning of "Java is too verbose", You can write code in Java that is easier to maintain. Java is not an excuse for poorly written code.
> The code was ridiculously verbose, of course, but that was not my fault. It was all out of my hands.
You get paid to write maintainable code that does what is intended. It was never "out of your hands".
I no longer like Java as much, but I don't think Java ever was a reason to sit back and let bad code happen.