Learning Java
Images are sometimes not shown due to bandwidth/network limitations. Refreshing the page usually helps.
You are currently reading a thread in /g/ - Technology
You are currently reading a thread in /g/ - Technology
I've had 1,5 semester of Java programming at Uni, but I never learned how to solve real problems with it. We covered basic stuff such as oop, standard libraries and concurrency, and I have developed a simple 2d game in libgdx as an assaignment.
What kind of stuff should I learn to get a decent job in Java/Scala after I graduate next summer?
this thread has been pruned or deleted
You should practice with some books. There's Elements Of Programming Interviews, it's a good book
never realized how shitty that logo looks
To get a job in Java you need:
> Java EE
> Hibernate
> Spring MVC
> Lots of theoretical knowledge
> Know design patterns
> MySQL/NoSQL
Then you can apply for a job. Also, useful would be:
> Knowing HTTP/TCP/IP/DNS and how it works
> HTML/JS/CSS
> jQuery/AngularJS/React etc.
As it goes for books, Thinking in java is a must read.
Good luck!
>>55510279
This is decent. I'd suggest starting with Spring Boot and JPA with Hibernate. Most Java jobs require some knowledge of either Java EE or Spring. Then you can look into Netty, RxJava etc.
Spring Boot makes it pretty easy to get started with Spring. Wildfly Swarm is similar but for Java EE.
>>55509504
>Java
>Uni
What kind of shitty university starts with Java? In my uni (a shitty one aswell, but apparently not as much) I have 2 semesters of procedural in Pascal/C, then 2 more of OO with C++, where we learn to solve countless problems, they don't even teach you the fucking language, its like "here learn the language from this book, we will teach you problem solving only"
And AFTER all of that you can take a Programming Lab with Java, which I'm not looking forward to tbqh.
>inb4 1990+26 Pascal
For learning purposes as a first programming course is an excellent language.
>>55509698
This board is safe for work.
>>55510279
For an entry-level job you don't need half of that shit, if you know it fine, but otherwise you learn it in the job.
For me was like:
Interviewer: You know PHP and SQL? We'll make you a small test.
Me: Yes, no problem.
>He takes a look at the test, I skipped stuff he will ask me below
Interviewer: Do you know anything about *list of frameworks* *github* *mvc* *etc*.
Me: No
Interviewer: No matter, we'll teach you, can you start tomorrow?
If it was for a semi-senior position then yes, you need to know that shit, but having experience you probably do anyway.
