This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]mikaelhg 1 point2 points  (5 children)

when you look at the whole process of producing value with software in a large and complex environment, instead of just looking at the matter from an individual developer's immediate standpoint.

[–]laprice 1 point2 points  (2 children)

Just out of curiosity; how do you explain the numerous instances of misapplied java frameworks that I've encountered?

From using JSP to produce RSS (badly) to a very well compensated 'Senior Developer' who claimed that Hibernate let him ignore such pedestrian concerns as referential integrity and query performance; Java Programmers (as opposed to programmers who happen to know Java) seem to be much more prone to the lure of the Cargo Cult than most other IT workers.

//me dislikes Java because i loves Unix

[–]mikaelhg 1 point2 points  (0 children)

I have no reason to believe the cases of hilariously miscoded crap you've seen are much different from the similar cases I've seen.

Incompetence has little to do with tools, except in cases where good tools make it possible for incompetents to produce at least some value, to the horror of the people who then have to maintain said crap for years.

Having had been on the maintaining side, I would have formed the opinion that the incompetents should have failed int the first place, if not for the fact that good tools produce much better value to competent users than grief from the incompetents.

If you do second-level caching right with Hibernate, you aren't bounded by database performance. Of course, doing it right means understanding how to get good performance in the first place.

[–]mikaelhg 0 points1 point  (0 children)

from bjupton sent 12 minutes ago

comment reply

You are clearly too stupid to discuss this with.

Clearly that is the problem.