<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Software Engineer on Adam Koszek - Personal Website</title>
    <link>https://www.koszek.com/tags/software-engineer/</link>
    <description>Recent content in Software Engineer on Adam Koszek - Personal Website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>adam@koszek.com (Adam Koszek)</managingEditor>
    <webMaster>adam@koszek.com (Adam Koszek)</webMaster>
    <lastBuildDate>Tue, 17 Jan 2017 00:00:00 +0000</lastBuildDate><atom:link href="https://www.koszek.com/tags/software-engineer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reading 101 for software engineers</title>
      <link>https://www.koszek.com/blog/2017/01/17/reading-for-software-engineers/</link>
      <pubDate>Tue, 17 Jan 2017 00:00:00 +0000</pubDate>
      <author>adam@koszek.com (Adam Koszek)</author>
      <guid>https://www.koszek.com/blog/2017/01/17/reading-for-software-engineers/</guid>
      <description>&lt;p&gt;I would argue that without reading, you&amp;rsquo;re wasting a lot of time.
&amp;ldquo;Good people borrow, and great steal&amp;rdquo;. I know few software engineers, who
don&amp;rsquo;t read and yet still write amazing software. But there are very few of them.
I bet you&amp;rsquo;re not one of them, actually.
And most of their time, they do waste &lt;em&gt;some&lt;/em&gt; time too.
Very few of us solve unique problems. You&amp;rsquo;re probably not the lucky guy either.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
