r/javahelp • • Mar 13 '19

Codeless Mastering Skills Beyond Java as a Professional Software Engineer

Hello all, I am seeking some guidance, and help from colleagues. I consider myself a junior software engineer with proficient enterprise level Java skills. However, though I continue to learn deeper topics about Java, I want to master the entire "process". What I mean by that is mastering topics such as Maven dependencies, Jenkins builds, etc. In other words, I want to be able to build an enterprise level Java application from scratch, even if it is just a hello world. What resources can I turn to, aside from the tool documentations, that will even just as much as outline this process? What did you do as a software engineer to better understand this overall process, any advice is welcome. Thank you.

26 Upvotes

20 comments sorted by

31

u/wsppan Mar 13 '19

Here's what you need to learn (biased but there are choices for each):

  1. Git

  2. Junit

  3. Maven

  4. Mokito

  5. Log4j

  6. Jenkins

  7. Spring Boot/MVC/Data/REST

5

u/TheEndlsNear Mar 13 '19

☝️This

2

u/mambeu Mar 13 '19

Good list but I’d add Gradle too.

5

u/Mpittkin Mar 13 '19

Why? OP mentioned Maven specifically and I don’t think wants to learn every option for each layer in the stack...

1

u/code_dev Mar 13 '19

Thank you for the feedback. So if this provided list I am pretty comfortable with everything except Maven, Mockito, and Jenkins. I guess that area of the software development process is what I was trying to express.

1

u/Mpittkin Mar 15 '19

Okay, well Maven is more used than Gradle so I’d start with that, but Gradle has its advantages too, so in the future it’s something you may want to explore (especially if you want to get into Android development). Start with a few tutorials and then just build some simple projects to explore things like resource management, filtering, integration tests, etc.

Mockito is just a tool used to simplify writing unit tests, so focus on JUnit for starters and then move on to using Mockito in those. You won’t get too far before seeing the value of Mockito. Unit tests are crucial, and they’re also the easiest and fastest to write and run, so definitely start with those.

Once you’re comfortable with those tools, you can move on to using Jenkins for CI/CD. Get a project going on Github (you can create private repos for free now). Then run through cloning it and building on the command line with maven, as this is essentially what Jenkins is going to do.

Install Jenkins locally and, using the documentation and whatever recently published tutorials you like, work through connecting to the repo using an auth token, and setting up a simple project and job to pull and build (with tests) every time a pull request is merged into master.

Then you can move on to things like web projects, integration tests with Arquillian, and on to full continuous deployment whereupon Jenkins will, on a successful build, deploy automatically to an application server.

Thennnnn you can move on to containerizing with Docker, microservices, databasing, and a million other things. You could literally do this for years and not come close to learning everything. You could spend months and months on Maven alone if you want to go deep. So you’ll need to make some decisions on what you like the feel of, what you want to pursue and learn more deeply, and then turn into a career. There’s a lot to choose from so choose stuff that you like, balanced of course with the demand for that skill. I wouldn’t recommend anyone just throwing themselves completely into learning Flash at the expense of all else, no matter how much they love it.

Anyway I hope that helps, and good luck. :)

3

u/wolfanyd Mar 13 '19

The process will really depend on the situation, but there's nothing particularly enterprisey about a single java application. At the enterprise level, you'll often find things like asynchronous messaging and integration frameworks that allow multiple applications, databases, systems, etc to coordinate as an enterprise system. Rather than thinking about application code, try thinking in terms of data flow between the sub-systems.

The best way to learn this type of thing is to work in a large-ish organization and start asking a lot of questions when you're around the lead devs/architects. That said, messaging frameworks like JMS, Kafka, Spring Integration, Camel, etc are great to know. Write a couple of simple applications and have them communicate by sending messages to one another through a message queue sitting between them.

1

u/code_dev Mar 13 '19

Thank you, I will definitely look into some of these technologies I am not very familiar with.

3

u/ironymouse Mar 13 '19

Much of building an application isn't associated with writing and compiling code. You might instead look at how requirements are tracked, how designs are produced and reviewed, how tests are written and how defects are managed and all might serve you better and more quickly than some knowledge about Jenkins.

That said in a team that is more both feet first there is an argument that the things I have listed may be seen as less important.

3

u/[deleted] Mar 13 '19

You want to outline the process for building not just enterprise level product but any professional project? Start learning about design patterns, separation of concerns, architecture, database design, source control. The list is endless and that's just a few things, but they're vitally important.

3

u/[deleted] Mar 13 '19

Linux /UNIX. An often overlooked aspect, this is many times going to be the environment your system runs in.

Solid OS fundamentals will help you understand the big picture and be of great use if something goes wrong. Learn Bash for writing/debugging start scripts and sifting through log files etc efficiently.

2

u/lokem Mar 13 '19

I'd say Linux/Unix skills in general has helped me tremendously.

1

u/TheEndlsNear Mar 13 '19

I’m in the same boat! I’ve been thrown into an enterprise app and I’ve basically just had to learn as I go.. learning to test your code as best as possible has helped me the most. Get super comfortable with JUnit and integration testing!

1

u/lank81 Apr 04 '19

It seems that you want to cover DevOps to some degree. I'd look at the DevOps handbook https://www.amazon.com/DevOps-Handbook-World-Class-Reliability-Organizations/dp/1942788002/ref=sr_1_10?keywords=DevSecOps+Handbook&qid=1554391709&s=gateway&sr=8-10

, along with covering the technologies that @wsppan touched on.

0

u/[deleted] Mar 13 '19

[deleted]

1

u/code_dev Mar 13 '19

Great feedback thank you. i am currently working hands on with Maven, and Jenkins on my project and felt pretty lost with the builds, and snapshots, dependencies, etc but I feel like I am beginning to understand it more...

0

u/[deleted] Mar 13 '19

[deleted]

3

u/[deleted] Mar 13 '19

He's asking about complimentary skills, additional technology to add to his stack, and (potentially) the soft skills required to be a professional developer.

Any monkey can bang keys adhering to syntax, but all of the above mentioned things and more are required to be regarded as a professional.

1

u/code_dev Mar 13 '19

Yes! and I apologize I accidentally skip replied your comment... but please refer to my rant above

2

u/code_dev Mar 13 '19

What im trying to communicate when I say "master the entire process" is being able to, for example, start a new job at a completely different company and if they ask me to build a system from the bottom up, I wouldn't really know where to start... I am proficient in Java and Spring MVC. I have a good grip on databases, but a year or two ago I would have no idea I needed Log4j, or Jenkins, or Maven or JFrog Artifactory or Chef. I feel like I am in very good standing when I am given an already standing project and I am asked to add components or microservices, or fix bugs but... to start one from scratch, from deciding technologies/dependencies to building the app an exporting it at enterprise level, I am still kind of lost.
I apologize if this still isnt very clear, I have the idea in my head, but I am having some trouble conveying it clearly...Hopefully this explanation makes more sense.

1

u/matt08220ify Mar 13 '19

It did! Thank you, I was just curious. The other reply failed to elucidate your question to any extent. But now I see that you're expanding on skills and technologies related to java which goes far beyond an IDE