<?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>opinions on Senior Software Engineer Learns Functional Programming</title><link>https://llcawthorne.github.io/tags/opinions/</link><description>Recent content in opinions on Senior Software Engineer Learns Functional Programming</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 12 Sep 2026 18:00:00 -0400</lastBuildDate><atom:link href="https://llcawthorne.github.io/tags/opinions/index.xml" rel="self" type="application/rss+xml"/><item><title>Go Language Opinions</title><link>https://llcawthorne.github.io/posts/go-language-opinions/</link><pubDate>Sat, 12 Sep 2026 18:00:00 -0400</pubDate><guid>https://llcawthorne.github.io/posts/go-language-opinions/</guid><description>&lt;p&gt;Go&amp;rsquo;s tooling is what stuck with me the most. gofmt is flawless, even on case
statements, no matter how hard I try to trick it, it always formats the file
correctly. Cross-compilation with GOOS/GOARCH is excellent, shipping a
single self-contained binary is genuinely nice to hand off, and the command
line tooling is great too. I like that the implementation stays transparent
instead of hiding behind framework magic, and I prefer simple structs with
methods over deep inheritance hierarchies. &lt;em&gt;Head First Go&lt;/em&gt; gave me real
confidence with the language, and &lt;em&gt;Powerful Command-Line Applications in Go&lt;/em&gt;
taught me a lot about building command-line apps, even in languages other
than Go, like how easy it is to write a markdown previewer when the standard
library gives you so much for free, and to always check out a new language&amp;rsquo;s
argument-parsing frameworks early. Even &lt;code&gt;//&lt;/code&gt; comments felt natural to me.&lt;/p&gt;</description></item></channel></rss>