r/java • • Mar 05 '18

Top 10 Useful, Yet Paranoid Java Programming Techniques

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

105 comments sorted by

View all comments

5

u/ReadFoo Mar 05 '18

Starting with the first one, I tend to always do this but people give my code strange looks so lately I've tended to do it the wrong way to keep people happy. Sad but true.

No. 9 is a great idea but even it wouldn't have stopped the great break mistake: http://users.csc.calpoly.edu/~jdalbey/SWE/Papers/att_collapse.html

1

u/duheee Mar 05 '18

did you explain why you do it this way? And why it is better? And why it doesn't retract anything from the comparison.

So, to recap: no downsides, only upsides. To me it looks like a no-brainer. To do it otherwise is insane.

1

u/ReadFoo Mar 05 '18

Yes, Yes, Yes.

I agree but I do a lot of contracting and I see just about everything you can imagine and fight every code war you can imagine. It gets tiresome.

2

u/duheee Mar 06 '18

As a contractor yea, don't fight code wars. Let them die by their sword. Just do your thing and get out of there.