<?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>book-review on Senior Software Engineer Learns Functional Programming</title><link>https://llcawthorne.github.io/tags/book-review/</link><description>Recent content in book-review on Senior Software Engineer Learns Functional Programming</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 11 Aug 2026 18:00:00 -0400</lastBuildDate><atom:link href="https://llcawthorne.github.io/tags/book-review/index.xml" rel="self" type="application/rss+xml"/><item><title>Head First Go</title><link>https://llcawthorne.github.io/posts/head-first-go/</link><pubDate>Tue, 11 Aug 2026 18:00:00 -0400</pubDate><guid>https://llcawthorne.github.io/posts/head-first-go/</guid><description>&lt;p&gt;&lt;img alt="Head First Go cover" loading="lazy" src="https://llcawthorne.github.io/posts/head-first-go/images/cover.jpg"&gt;&lt;/p&gt;
&lt;p&gt;Overall, it&amp;rsquo;s what I expect from a Head First book. It was a perfectly
serviceable introduction to the Go programming language. Although it&amp;rsquo;s a Head
First book, I feel like it treated me like an experienced programmer and
didn&amp;rsquo;t waste a lot of time explaining how an &lt;code&gt;if&lt;/code&gt; expression worked. Unlike
&lt;em&gt;Head First Kotlin&lt;/em&gt; which never got to a lot of things that it had to toss
into &lt;em&gt;Ten Brief Topics in the Appendix&lt;/em&gt;, it felt like it covered all the main
topics that needed to be covered to understand Go. It even includes coverage
of automated testing and a couple of chapters on web apps.&lt;/p&gt;</description></item></channel></rss>