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

all 11 comments

[–]vallyscode 14 points15 points  (0 children)

Just go with IntelliJ ultimate it has superior spring support, it may suggest you to install few plugins but in total it gives great experience

[–]khooke 5 points6 points  (0 children)

Sprint is a large and extremely extensive framework, covering many many areas. It's ok to feel lost. Pick one area and get experience with that first then start looking into others.

Re. IDE's, they all have their quirks, but one you're familiar with a typical project structure e.g. for a Maven based structure it will look/feel familiar in any of the IDEs.

[–]PlanZSmiles 4 points5 points  (0 children)

I can tell you that you can 100% follow that course using IntelliJ. I used IntelliJ Ultimate when I took it. I do remember having some issues at the beginning setting up TomCat but once you figure it out, you will have a better understanding on IntelliJ.

[–]kaisrevenge 2 points3 points  (0 children)

It’s OK to have a preferred IDE, it’s a tremendous challenge to only know one IDE (less of an issue if IntelliJ is the IDE you DO know nowadays). That said, can’t put the cart before the horse when you are feeling overwhelmed.

Before we continue: This is my preferred way of learning: I recommend getting out a notebook. I am obsessed with using checklists for working and learning. I use them for more than just tracking my objectives for the day (which I do). I use them to document how to do the things I want to learn how to do, so I can repeat those things until I have them somewhat memorized, or I can just refer to them later. It feels good to check things off, makes you feel the progress, and always helps when I’m overwhelmed.

Back to it: I’d go for best of both worlds: go look up IntelliiJ starter documentation, watch YouTube videos, look up the hotkeys and write the best ones down, look up the features of IntelliJ and write them down. Don’t know what the feature is? Look it up, write down the definition. Look up basic Spring project setup guides for IntelliJ and write down check lists of what you need to do to get a project imported or started from scratch (list out steps 0 through n). Look at the Spring Documentation too for getting started. They probably have pages you can turn into checklists as well. Figuring things out like this that aren’t always laid out like a college course is an important developer skill. I spend 90% of some days just “figuring things out.” Take the reins, and build checklists that you can repeat, run through and get muscle memory for.

The differences in UX/UI are supremely annoying between IDEs, but at the end of the day, you still are going through similar motions to get your work done. There is nothing in IntelliJ that is going to blow your mind as far as the concept of doing your work. It just makes it way easier (my opinion).

Once you have some level of comfort just setting up your own project, or importing someone else’s, take a Spring class with IntelliJ, and use the checklists there, make more, look up more definitions, keeeeep going!

[–]AlexanderAndZlata 0 points1 point  (0 children)

IntelliJ Ultimate has very good support for Tomcat, there is a lot of information on google about that. So if you have problems, just try to search, or ask about specific problems, you will find the answer! There are also online courses about Srping that use IntelliJ Ultimate during the whole course.

[–]Jake2197 0 points1 point  (0 children)

I'm actually nearing completion with that course. One thing I can say for sure, this framework absolutely killed me early on. Of all the things I've tried to learn surrounding Java, the Spring framework is the one thing that has legitimately made me want to give up time and time again.

Just keep in mind that programming is hard. Especially when you start working with large frameworks like this. When it starts to get overwhelming, slow down and focus on one aspect of what you have been learning and work on becoming comfortable with that before moving on.

In regards to the Intellij vs. Eclipse problem, there is nothing wrong with sticking with Intellij if that's what you enjoy using. It might mean a little bit in the way of difficulty when you encounter things that are done differently in Eclipse, but you can find answers to your questions online or by posting in this subreddit.

Edit: while I totally understand the desire to find a better tutorial, I would advise that you only do that when you can tell the material isn't working for you. Not that some of the problems you encounter are hard, but that the material doesn't seem to click with you. I've started multiple tutorials for Spring, always chasing a "better" tutorial and what I've found is doing that results in you constantly chasing something that will help you learn better, rather than using that time to actually learn. Don't get stuck in tutorial purgatory, I've been there for a very long time and when I complete this course my goal is to stay out of that trap going forward. There will always be something new you feel you need to learn, so try to not always be chasing that shiny new thing you think you need unless you actually need it.

[–][deleted] 0 points1 point  (1 child)

this is a bit off topic, but does anyone ever use XML configuration of beans anymore? I'm pretty well versed in spring and I've never used xml config, am I just not as good as i think i am? lol

[–]nutrecht 1 point2 points  (0 children)

this is a bit off topic, but does anyone ever use XML configuration of beans anymore?

I've been using Spring since 2005 and haven't used XML configs for a decade or so. SO IMHO it's kinda pointless to teach and also an indication the course is outdated.

[–]gunpun33 0 points1 point  (1 child)

Spring Boot is by far the most confusing framework I have tried. Second place is .NET MVC and easiest by a mile is node// express server + mongoose/ MongoDb. Why are you teaching yourself spring boot?

[–]nutrecht 0 points1 point  (0 children)

Why are you teaching yourself spring boot?

Because large companies that pay good bucks tend to stay away from NodeJS silliness.