r/java • • Aug 11 '15

Top 10 Useful, Yet Paranoid Java Programming Techniques

http://blog.jooq.org/2015/08/11/top-10-useful-yet-paranoid-java-programming-techniques/
181 Upvotes

76 comments sorted by

View all comments

Show parent comments

1

u/[deleted] Aug 13 '15 edited Aug 13 '15

[removed] — view removed comment

1

u/PaulRivers10 Aug 13 '15

I'm not sure how personal attacks and assumptions are relevant, but I apologize for having offended you.

Well, fair enough, I probably went to far there for the forum. I have a huge grudge on my shoulder after having to quite a job after suffering through a year of idiots pushing the latest fad onto everyone else, spending a lot of time bickering over it, taking no responsibility for it then everyone else getting blamed for not being able to get things done.

I eventually had to quit. I got a new job with far more pleasant "focussed on what's actually working" people and it's way better, but it brings back nightmares (I really should have quit earlier).

I eventually figured out that what happened was, in the beginning people had lots of ideas. Smart or average people who tried them out found that some of the ideas worked well, some of them sounded good but didn't work well, some of them sounded good but in practice were terrible.

The ones left are mostly the ones in the last two groups, ideas that sounded good but people who used them found they didn't work very well. These same people I worked with would adopt these ideas because they were "new" and push them onto everyone else.

To be fair - I don't know what your work is like. Perhaps you work on code dramatically different than I do, so there is some sort of merit for what you work on. But I know for what I work on it's not helping solve any real problems. When most of your app is "take data submitted from internet form, put it into the database", people reassigning things to a var is a non-issue 99.9% of the time.

Like I've mentioned in previous posts, we've seen wins in both development and maintenance time. The largest bottleneck is never the time that it takes to type the code into the editor, but the time that it takes to truly understand what a system is doing (or what a new system should be doing), which is why things like descriptive variable names, comments, and keywords such as "final" exist.

I can't say with certainty that you don't work on a system that is so different than mine that perhaps there's some sort of advantage for what you're working on.

If you're working on CRUD web apps it seems to me to be a total waste of time, trying to solve an issue that doesn't exist. I mean on my projects I've watched people eat several weeks of work that didn't benefit us, then tell everyone it was hugely helpful and time saving.

Could be my system is different than yours, and my experience watching that happen is unrelated to what you're working on.

Just because a practice is popular does not necessitate that it is wrong. It appears that you have a strong personal style that works for you. That's great! I have a strong personal style that works for me. I'm sure that as I approach the mindset of ten years of experience such as someone like yourself, this style will have changed. At the very least, I'll make an attempt to understand and apply any popular fads that come along, to see if there is anything worthwhile to incorporate and use.

That's the opposite of what I said though. Popular doesn't necessitate that it's right or wrong, but I think people have tried this approach many times before and it has never caught on (if anything I said that popular made it right) because it sounds good in theory but becomes a real pain in practice.

What I feel I know for sure is that it's a terrible approach for CRUD web apps - most of your app is simply moving data between the browser and the db. Making it difficult for frameworks to set the properties or your data objects, and making it difficult for frameworks to set data from the database adds a lot more work. Since you rarely reassign anything anyways it's also not solving any kind of common problem. For web CRUD apps it's like making extensive plans for snowfall if you live in Brazil.

If you do development for 10 years, there will be times you still won't agree with other, but you'll have seen a lot of fads that had terrible results go through.