All right, so let's do a quick summary on what we have just learned.
We know that we want to clean the code as often as possible when we finish our feature, when we are
done with some classes, with an update, or we just want to comment on fault.
It doesn't really matter when.
Just have to do it consistently.
So we want to reform the code and remove unused imports from our code.
And we can do this with the shortcuts that I have told you about it.
It's really easy.
And basically the idea does this for you automatically.
You also have to be on the lookout for logs or commented code that really makes no sense for your code
anymore, maybe rather than when you are debugging or actually implementing the feature and you want
to remove those because other developers, when they might jump into the code, they won't understand
their meaning and they they will basically lose time with those.
You also have to be on the lookout for any classes, methods or variables that have poor naming that
were either from the beginning named like that, or maybe you refactor the code, you extracted some
stuff and they're naming kind of lost any kind of meaning.
You want you want to be on the lookout for this just to make sure that your variables are always suggestive
in their naming.
And this basically helps a lot any other developer that jumps into the code so he can understand better
what's happening.
You also want to be on the lookout for your auditing methods within classes.
I always have this tendency to create private methods wherever I can just to make the code work, the
feature work.
And then I also go and reorder the methods just to make sure that they are in the correct order.
So we have over other methods, public methods, private methods, and so just have to make sure that
they are consistent because they will actually help other developers understand better what's going
on in the classes because they are going to be get used to a pattern and that pattern and kind of impose
yourself.
We are going to talk a bit more about this in a special lesson.
But the overall picture of this lesson is to create a habit out of cleaning your code to make sure that
you do this every time you feel the need to.
And this will drastically improve the quality of your code.
It will make it much cleaner and with very little investment, maybe a couple of minutes a day, you
can really improve the quality of your code and your projects.
And this will help you.
It will make the code much, much cleaner.