014: Effective Java for Android developers : Item 1

We’ve mentioned the book “Effective Java” by Joshua Bloch quite a few times on previous episodes. At this point, everyone knows they should have read this book (quadruple times). But it’s a dense read and everyone could use a reading buddy. Also, what does Effective Java look like through the eyes of an Android developer?

In this second installment of our Fragment (a.k.a mini-episode), we thought we’ll do our listeners a favor and help with that reading. We introduce the very first of these venerable “Items”: Consider providing static factory methods instead of constructors.

Stay tuned for more items from our “Effective Java for Android developers” Fragment series.


Show Notes

Consider providing static factory methods instead of constructors


  1. You can control the name and thus give it much more meaningful names
  2. You are not required to create a “new” object each time they are invoked
  3. You can even return an object that’s a subtype of the return type (unlike constructors which only return class type)


  1. Classes without public or protected constructors cannot be subclassed
  2. Static factory methods are not readily distinguishable from other static methods


  1. “Consider” using static factory methods (not always)
  2. Use newInstance when creating Fragments [androiddesignpatterns.com]
  3. Use newIntent static factory method for creating intents inside the target activity.

Contact us:

012: Continous Integration and Collective Code Ownership

In this episode we’re trying something new. Everyone has requested more episodes of the podcast. In short, everyone wants a weekly show. So this week, we’re introducing what we call a mini-episode … or as we like to call them a “Fragment”. Fragment episodes will be shorter in length but still packed with goodness. They will range from ~7-25 minutes in length and will showcase either Kaushik, myself (Donn) or both of us.

In the first “Fragment” installment we’re going to talk about Continuous Integration (CI) and Collective Code Ownership (CCO). Donn talks about what CI is, why its important and how it benefits you and your team. He then dives right into CCO and how it can be facilitated through testing.

We hope you enjoy these new mini-episodes … aptly named … Fragments. :)


Show Notes

Continuous Integration solutions:

Continuous Delivery:


Donn Felker

Kaushik Gopal