Following a coding style guide, could be your own or of the organization you work for.
Also, making sure it's easy to read the code, there by tracking down bugs would be easy. I say tracking down because, I know bugs are meant to be there in any code, at least when coded by a developer like me, it's better to have a simpler code that performs little slower than a very robust code that is very fast and difficult to understand in case of any bugs. Because in my experience, bad variable names cause more issues than a bad code does.
Also trying to make the code align with latest standards and design patterns.