<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>note on Dan Lowe</title>
    <link>https://danlowe.me/tags/note/</link>
    <description>Recent content in note on Dan Lowe</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>dan@danlowe.me (Dan Lowe)</managingEditor>
    <webMaster>dan@danlowe.me (Dan Lowe)</webMaster>
    <lastBuildDate>Fri, 02 Mar 2018 19:28:56 -0500</lastBuildDate>
    
	<atom:link href="https://danlowe.me/tags/note/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Why Kotlin? An Introduction. (Part 1)</title>
      <link>https://danlowe.me/post/2018-03-02-kotlin-1/</link>
      <pubDate>Fri, 02 Mar 2018 19:28:56 -0500</pubDate>
      <author>dan@danlowe.me (Dan Lowe)</author>
      <guid>https://danlowe.me/post/2018-03-02-kotlin-1/</guid>
      <description>The Awakening When Kotlin was announced as a first class Android language at Google I/O in 2017, I like many Android developers, was skeptical. As an ardent user of Jetbrains products for a number of years now I haven&#39;t been oblivious to Kotlin, but I&#39;ve only recently begun to take Kotlin seriously. In fact, after developing CoinWatch in Kotlin, I don&#39;t know that I&#39;m going to start another Android project in Java (willingly) ever again.</description>
    </item>
    
    <item>
      <title>A quick note...</title>
      <link>https://danlowe.me/post/2018-02-28-a-quick-note/</link>
      <pubDate>Wed, 28 Feb 2018 12:41:46 -0500</pubDate>
      <author>dan@danlowe.me (Dan Lowe)</author>
      <guid>https://danlowe.me/post/2018-02-28-a-quick-note/</guid>
      <description>To precede my first &amp;ldquo;technical&amp;rdquo; post I&#39;d like to mention something that I intend to do with this blog&amp;hellip; get you reading the documentation for what you&#39;re doing. I&#39;ll try to provide as many links to actual/additional documentation as I can, but I&#39;d like to avoid recreating steps and documentation that already exists. This isn&#39;t because I want you the reader to spend countless hours understanding every minute detail of what you&#39;re using, it&#39;s because documentation changes.</description>
    </item>
    
  </channel>
</rss>