Packages in OOP are quite important for encapsulation.
It's good that you don't use default package (the one without name). Intellij folks did a nice thing by replacing it with com.company.
Next step would be to have a true package, one tied to you AND the project you would be doing.
So, folks at github probably code in packages com.github.project - if they code in Java, for I hear they do it in Ruby.
And, while we're on packages... why have everything public? Hint: think what is the default encapsulation specifier.
Packages in OOP are quite important for encapsulation.
It's good that you don't use default package (the one without name). Intellij folks did a nice thing by replacing it with
com.company.Next step would be to have a true package, one tied to you AND the project you would be doing.
So, folks at github probably code in packages
com.github.project- if they code in Java, for I hear they do it in Ruby.And, while we're on packages... why have everything
public? Hint: think what is the default encapsulation specifier.