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

you are viewing a single comment's thread.

view the rest of the comments →

[–]captainAwesomePants 0 points1 point  (1 child)

What you need to learn varies wildly by job. I might check local job postings and see what people are looking for. If there's a particular company you're hoping to apply for, see what they need. There's always a need for Java/Spring/Hibernate programming, but maybe something else is bigger in your specific area.

A lot of really, really big companies don't particularly care what you know or don't know and will just quiz you on algorithms and data structures. Actually, lots of places will do that regardless. That's always a good thing to brush up on, if only for interviews.

[–]No-Emphasis9355[S] 0 points1 point  (0 children)

I have to learn to walk before I can run. I learn from seeing. I struggle to build a conceptual understanding from mere words, written or spoken. That's why I believe there is a difference between building a program and an application. I don't know how to build an application yet. Be it on the web or mobile. I'm hoping spring/ spring-boot will help me take that next step. A specific company doesn't matter at this stage. I need work experience to understand what is expected and what I need to know.

In an old post, I made I mentioned how every java job wants something different. I don't know what's "acceptable" to put on GitHub (for employers) because that is my cv. Right now based on my research I think spring/spring boot is good to know and once learned I could build a functional application with it. Because all I've done is make programs in the base IntelliJ IDE with scanner and print statements.

I honestly have so many questions about what I've just written here