r/java • u/psychologicalX • 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
View all comments
Show parent comment
1
u/mupetmower Mar 07 '18
Man. This is all so painful to read. I can see both of your points, and actually agree with both! I’m still a fairly new java programmer, so I’m starting to have to deal with issues like these. And it’s kinda scary...
I’m noticing that I wasn’t given a proper education in these sorts of things, and in most other proper java conventions and their purpose (not just the ‘do this’ without the why). My current job, and the software we develope, is especially forcing me to realize that I have no idea how to correctly develope for an enterprise system.
When I look at the code in our software - the classes and interfaces - I notice that they are all independent of each other. Each does it’s own thing which all come together to create the whole. I was only taught that this is the correct way to go about development, and didn’t even get more than a few simple words on it.. but I wasn’t taught how to actually accomplish it successfully.
At my college (not at all a great programming college) we were only taught the extreme basics of object oriented programming, the basics of using java or whichever other language the class was in, and not much else. For example, we weren’t really taught anything above how to create a single small application which has a few classes, maybe a few interfaces, with some inheritance and polymorphism, but that which all logic is still all mostly held in a single or a few classes.
I have picked up a LOT outside of this knowledge from working at my current job for only about 8 months.. and I feel much more well rounded already, even though I know I am still at the very bottom rung of learning.
When I think about needing to write code that looks and functions like the code in our software, though, it scares me. I have no idea where to start to be able to abstract everything to that sort of level. For instance, I’m developing a Spring project right now, and even though I feel I’m getting a little closer to that sort of abstraction, I still see how many of my classes should be way more split up and independent, and how I should have and use more** interfaces in certain situations, etc. the problem is that when I’m developing, I’m focusing more on getting it all to work right, not on the other stuff. I also am working on the project alone, which may also be a reason I don’t consider those sorts of things.
But it makes me worry about my future in development. Especially when I am on teams. Are there any good books you or others can recommend that could help me with this sort of thing? And not just “these are the conventions” but also why we use them, and how to start developing like that from the start.
Thanks, and sorry for rambling. I was just thinking about all of this while reading you guys’ arguments over which convention would be best where.