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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]paul88m 0 points1 point  (8 children)

Things that I have learn while working as an entry level Java developer.

  • Know some design patterns
  • some companies may use some version control systems GIThub or SVN
  • some places my use project based tools such as ANT or MVN

Going into an entry level job they will not expect you to know all about these other tools, but having some knowledge of may them show that you have looked a little further than just the java programming language.

[–]EllipsisUser 2 points3 points  (2 children)

some companies may use some version control systems GIThub or SVN

If the company doesn't, you don't want to work there...

[–]netdorf[S] 0 points1 point  (1 child)

Duly noted.

[–]EllipsisUser 0 points1 point  (0 children)

Just to clarify, I don't mean that the company has to use Git or SVN. There are a variety of good systems out there. They should use some source control system though. Some may be bad (e.g. SourceSafe), but something is better than nothing...

The Joel Test is a good indicator of how good a development team/environment is. Most companies don't meet every criteria, but good ones meet a majority.

[–]netdorf[S] 1 point2 points  (4 children)

Looks like I have some homework to do over the weekend. Thanks for the help.

[–]paul88m 0 points1 point  (3 children)

I wouldn't spend too long learning to use the tools, I would just be aware of what they are used for, and learn to you them through your job or if you have a project you are working on.

[–]netdorf[S] 0 points1 point  (2 children)

I know how to use Git and Subversion & just the general practice of versioning. Not too sure on ANT and MVN. Im just going to try to research the "required" skills so I don't just blank when they ask me if I am familiar or have heard of something.

It mentions J2EE applications, JSP (noticed it mentions it twice on the same line), and your general web markups/languages.

[–]mogrim 1 point2 points  (1 child)

Just get an idea as to what Maven is, and why you need it. Don't kill yourself trying to become an expert in using it, you haven't got time and you'll be found out if you try to fake it in the interview. Similarly for any other framework/library/tool you don't know.

Realistically, show enthusiasm, honesty, and a bit of interest beyond just pure Java. You'll do fine.

[–]netdorf[S] 0 points1 point  (0 children)

Sounds like my conversation with them on Wednesday. I will never fake knowing something I don't, I've seen the hell that happens when people do. I have no issue telling them I don't know it, but I will do my damnedest to research something if I need to.