<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Android on José Caldera</title>
    <link>https://josecaldera.dev/categories/android/</link>
    <description>Recent content in Android on José Caldera</description>
    <generator>Hugo -- 0.125.7</generator>
    <language>en</language>
    <lastBuildDate>Mon, 15 Jun 2020 19:40:26 -0400</lastBuildDate>
    <atom:link href="https://josecaldera.dev/categories/android/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Gradle: Taming the Beast</title>
      <link>https://josecaldera.dev/posts/2020/06/gradle-taming-beast/</link>
      <pubDate>Mon, 15 Jun 2020 19:40:26 -0400</pubDate>
      <guid>https://josecaldera.dev/posts/2020/06/gradle-taming-beast/</guid>
      <description>When we start our Android programming journey we just want to build new and awesome stuffs, beautiful and robust apps. We get to a point where we start to learn about design patterns, architecture and best practices, but often we dedicate less time to learn about Gradle. For me, this was one of my duty points in my career as an Android Developer. Well&amp;hellip; not anymore, and if you&amp;rsquo;re in the same situation, I hope this starts to change now.</description>
    </item>
  </channel>
</rss>
