r/javahelp • u/Ashamed_Specialist • Apr 29 '19
Java internship but not ready?
My internship starts in a few weeks and I'll be working with Java most likely, but I don't know what else I'll be using. I've done a little bit of coding in Java (syntax stuff like hash tables, loops, some recursion, the 101's, etc), but nothing really else. What should I learn in the next few weeks so I can hit the ground running and maximize my initial velocity? I don't want to lag behind too much because I heard it goes by fast and I want to do really well
15
u/wsppan Apr 29 '19 edited Apr 29 '19
A IDE. I would find out what the majority of developers use and ramp up on it. Most likely Eclipse or Idea. Learn how to use the debugger.
A version control tool. Find out what they use and learn it. Most likely Git.
Unit test. Find out what they use and learn it. Most likely JUnit. Ask about Mock frameworks and learn that as well.
10
Apr 29 '19
Learn how to use IntelliJ it is your friend...also fuck eclipse
1
u/FrenchFigaro Software Engineer May 02 '19
Not a really viable advice if the standard in your team is Eclipse
7
u/slowfly1st Apr 29 '19
Since it's only a few weeks and you will use Java primarily, probably look primarily at the Java API's / components:
https://docs.oracle.com/javase/8/docs/index.html
(honestly can't find this overview page for newer versions java)
Collections-API is a good start (Map, List, Collection and so on and their implementations), I/O (read and write files), Concurrency/Multithreading (also understand the concepts), JDBC (connect to a database, read and write data). Date/Time-API. Probably networking.
Also learn all the language features. E.g. that there are three different kind of comments, know "all the keywords" (what's volatile and transient? I always mix them up ...), or what is try-with-resource?
If you're decent with java, you'll have,... let's say "one problem less"
Learn OOP/OOD: Read and understand those concepts is a good start: SOLID, Loose coupling, High cohesion, Information Hiding. Those concepts we do apply, so we can reuse parts of our code (so it's not duplicated), improve maintainability, interchangeability (like changing the front end technology to display the website without redoing the whole software), and so on. Not sure if that's too early for you, in the sense, that you are still learning the language and learning another "thing" is too much.
Databases are already mentioned (many applications use a relational database as 'backend'): Setup a database (e.g. postgreSQL or mysql, both are free), learn how to create tables (columns, datatypes, primary keys, [indices, constraints]), crud operations (create, read, update, delete data), how to restrict selection of data (where clause), how "to join tables", functions (max(), avg(), count()). Imo the basic concepts of 'relational databases' and how you get/change data is quite easy compared to learning a programming language.
Read Clean Code. (Probably too early for you, but I leave it here)
Probably have a look at HTML/CSS/JS. I really like w3schools, but mostly as a reference, because I don't know these by heart. Not sure if you have enough time, but try to learn some of the components of html and learn how to style them. It's actually quite easy compared to Java. If there's enough time, to learn some JavaScript may be helpful, too.
... and now combine everything :P - no, seriously: "Ship" a product - even if it's something small and irrelevant. To break down a problem into smaller problems and combine everything we know to solve those problems with the most elegant solution is what we do day in day out. And get your code reviews (e.g. here on reddit, the stackexchange-network has a good code review network, too). Because there's always a better and more elegant solution. If no one tells you, your code sucks (... or can be improved) and why, you keep writing bad code - or at least you won't improve as fast.
8
Apr 29 '19
Best thing to-do is go in with the attitude to learn; find stuff you don't know, ask and learn. make sure you've got resources handy to be able to look things up when you need it.
3
2
u/OffbeatDrizzle Apr 29 '19
Fire up an IDE and write a little program to get yourself going. There is nothing better than learning by doing.
2
u/tanenbaum Apr 30 '19
WRITE CODE. Go to leetcode.com, sort the algorithmic problems by difficulty and try to solve as many easy ones as you can. When you've solved one or get stuck, take a look at the solutions and the discuss to see how the problem can be solved.
2
u/thenameunforgettable Apr 30 '19
Build pipelines. By that I mean that most engineering projects are about transforming data - mapping and reducing. I don't mean Hadoop. I mean you'll have a data set and you'll want to create a summary of that data. The best way to do this in Java is by using the InputStreams and OutputStreams. Build them together to work in conjunction, and it becomes easy to stream large amounts of data through your system.
Look at Google Guava. It's a really helpful library with a lot of little things that do some heavy lifting.
Try to never create threads directly. Use a thread pool. The number of threads you use should usually be equal to the number of cores on the machine if you're CPU bound. If you're network bound, create a pool and a thread safe queue. Put the work you need to do into the queue and have the threads poll the queue. Alternatively use Netty but it's super hard to write a high quality async network client.
0
u/erjiin Apr 29 '19
Your version control tool, probably spring if you use it. Hibernate/jpa. Focus on the tools imho. Don't put too much pressure on you, listen what will be explained by your colleagues and it will be fine!
3
u/OffbeatDrizzle Apr 29 '19
Spring isn't a version control? Unless you mean inversion of control which would come under dependency injection. Were you thinking of git?
2
u/erjiin Apr 29 '19
Wrong formulation sorry, I wanted to say a version control tool (git, svn, the one he will use) AND spring :)
2
u/squishy404 Apr 30 '19
Spring got me on my first internship. I never knew it existed, then boom a framework that was never mentioned in college that is absolutely vital to development in the real world. Really confused the hell out of me for awhile. I couldn't live without it now though.
3
u/Ashamed_Specialist Apr 30 '19
Thanks everyone for the advice.. crunch time :)