028: Tips and tricks we picked from 2015

Feast yourselves to a grand bonanza of tips and tricks with this episode! Donn and Kaushik talk about the tips and tricks they’ve picked up over the course of 2015.

Download

Show Notes

Contact

027: Talking Realm with Christian Melchior

Realm pro and overall genius Christian Melchior joins us in this episode to talk about all things Realm.

Download

Show Notes

Contact

026: LetMeExplainYou AndroidDev like a pro

In this episode Donn and Kaushik chat with the one and only Israel Ferrer Camacho (@rallat). They discuss a talk Israel gave sometime back on “Android development like a pro”, exchanging war stories on patterns like MVP, MVVP clean architecture etc.

Download

Show Notes

Awesome Picks:

Rallat:

Donn:

Kaushik:

Contact

025: Effective Java for Android developers : Item 7

In this mini Fragment, we introduce Joshua’s seventh Item and a momentous end to the first chapter: Avoid finalizers

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

Download

Show Notes

Avoid finalizers

  • If you don’t know what they are, ignorance is bliss. If you know what they are, avoid them!
  • Finalizers in Java != destructors in C++ (C++ counterparts to constructors).
  • In C++ destructors
    • you reclaim resources here (Java has GC)
    • you also reclaim non-memory resources (use the try-finally block in Java)
  • (unpredicatable amt of time between object becoming unreachable and finalizer being executed) Never do anything time critical in finalizer!
    • System.gc + System.runFinalization increase chances – no guarantee
    • System.runFinalizersOnExit + Runtime.runFinalizersOnExit are the ones that do – but they are fatally flawed
  • Java 7 has try with resources, which is also interesting and auto-closeables. [Android] devs can only dream of these.
  • If an uncaught exception is thrown in a finalizer, it is ignored, and the finalization abruptly terminates.
  • Severe performance penalty for using finalizers – (one e.g.) time to create and destroy simple object goes from 5.6ns -> 2400ns
  • Only valid use: as a safety net or to terminate noncritical native resources.
  • [Android] you’re probably better off using Android’s lifecycle methods.

Contact

024: Effective Java for Android developers : Item 6

Joshua’s sixth Item: Eliminate obsolete object references, in a distinctively croaky voice.

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

Download

Show Notes

Eliminate obsolete object references

Supplemental reading (for the diligent ones that follow shownotes)

Contact