Important things to keep it mind before a Code Review in Java
I have just created a mid-sized web-application using Java, a custom MVC framework, javascript. My code will be reviewed before it's put in the productions servers (internal use).

The primary objective of building this app was to solve a small problem for internal use and understand the custom made MVC framework used by my employer. So, my app has gone through *MANY* iterations, feature changes and additions.

So, bottom line, the code is very very dirty and this is my first "product level" Java app.

What are your suggestions, what are some basic checks/refractoring I should do before the code review?

I am thinking about:

1. Java best practices (conventions)

2. Make the code simple to understand for the developer who will maintain it. (won't be me)

3. I noticed, I have created some unnecessary objects and used hashmaps/arraylists where could have easily used some other Data structure and achieved the solution. So, is that worth changing?
Important things to keep it mind before a Code Review in Java
===

I have just created a mid-sized web-application using Java, a custom MVC framework, javascript. My code will be reviewed before it's put in the productions servers (internal use).

The primary objective of building this app was to solve a small problem for internal use and understand the custom made MVC framework used by my employer. So, my app has gone through *MANY* iterations, feature changes and additions.

So, bottom line, the code is very very dirty and this is my first "product level" Java app.

What are your suggestions, what are some basic checks/refractoring I should do before the code review?

I am thinking about:

1. Java best practices (conventions)

2. Make the code simple to understand for the developer who will maintain it. (won't be me)

3. I noticed, I have created some unnecessary objects and used hashmaps/arraylists where could have easily used some other Data structure and achieved the solution. So, is that worth changing?