Joined April 2012
·
Achievements
232 Karma
11,268 Total ProTip Views
Charity
Fork and commit to someone's open source project in need
Komodo Dragon 3
Have at least three original repos where Java is the dominant language
Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos
Forked
Have a project valued enough to be forked by someone else
Komodo Dragon
Have at least one original repo where Java is the dominant language
Epidexipteryx 3
Have at least three original repo where C++ is the dominant language
Epidexipteryx
Have at least one original repo where C++ is the dominant language
My only thoughts about android guidelines:
Dividing all the packages for activities/services/fragments/etc may be okay at the beginning but when your application is growing more and more I would rather go for "package by feature" instead of "package by layer". Naming packages like "users" or "posts" makes your app more modular. This makes you able to track (for example) circular dependencies between modules. Additionally, removing some functionality from the app is a lot easier when all the classes related to that specific feature are condensed in one package. Otherwise it's (too) easy to forget about some single fragment/helper/something that is not needed anymore.
Anyway, it's rather hard to disagree with anything else, especially the java-in-general guidelines so great thanks to you guys. :-)