It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.
John Petitto jpetitto
garybernhardt
/ types.markdown
Last active
May 22, 2024 10:02
jpetitto
/ gist:f01fa09af58189f335b5
Created
April 30, 2015 19:24
Jake Wharton's Tips for Becoming a Better Android Developer
-
Don't blindly accept that Google's approach to Android development is always the right way. Judge for yourself what the right approach is (often times it is Google's approach) based on your requirements and solution.
-
Be comfortable with examining the Android source code. It's not magic, there's always an answer. Helps you solve problems that would otherwise show up on Stackoverflow.
-
Be multi-discipline. Android can be your focus, but develop for other platforms and use other languages.
-
Master the tools. Make it work for you.
-
Be resourceful. Know when and why a library is the right choice over writing your own solution.
prakhar1989
/ richhickey.md
Last active
November 8, 2023 17:19
— forked from stijlist/gist:bb932fb93e22fe6260b2
richhickey.md
Rich Hickey • 3 years ago
Sorry, I have to disagree with the entire premise here.
A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.
Mastery comes from a combination of at least several of the following: