Image for post
Image for post

One of my colleagues recently mentioned that they saw a presentation that says:

If you are an Android developer and you do not use WeakReferences, you have a problem.

I personally think that, not only that is a wrong argument but it is also totally misleading. WeakReference should be the last resort to fix a memory leak.

Then today, I came across the post in Google Developers Experts publication by Enrique López Mañas

It is very good article that summarize how references work in Java with examples.

The article does not say that we have to use WeakReference but it also does not give any alternative. I felt like I must give alternatives to show that it is not a must to use WeakReference.

I’ve been thinking about this for a long time. When you type a wrong task name in gradle, the stderr output tells you about it and gives an alternative candidate.

When this happens, I always type fuck and all I see is:

Image for post
Image for post

Well, no more. Finally I decided to write a custom rule for it.

Here you go:

Once you install the rule, it saves your life over and over.

Image for post
Image for post

To see how to install it, please read the README file.

Update: With the release of Google Play Services 8.3, the need for the Storage permission is completely dropped. You can safely remove the permission completely now. Here is the official documentation:

If you’re targeting version 8.3 or later of the Google Play services SDK, you no longer need theWRITE_EXTERNAL_STORAGE permission to use the Google Maps Android API.

For a long time, Google Maps Android SDK requires us to have WRITE_EXTERNAL_STORAGE permission. …


Tahsin Dane

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store