<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Go on Maximilien Rothier Bautzer</title><link>https://maxbautzer.me/tags/go/</link><description>Recent content in Go on Maximilien Rothier Bautzer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 11 May 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://maxbautzer.me/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>Safe coding</title><link>https://maxbautzer.me/post/safe-coding/</link><pubDate>Tue, 11 May 2021 00:00:00 +0000</pubDate><guid>https://maxbautzer.me/post/safe-coding/</guid><description>&lt;p&gt;Testing is pretty uncontroversial these days, most people involved in software engineering will at least pay lip service to the idea that code should always be tested.&lt;/p&gt;&#10;&lt;p&gt;Although all tests are equal, some are more equal than others. Over the years I&amp;rsquo;ve come to think that the best tests share the same overarching design philosophy. I think working in a well tested codebase is truly an eye opening experience, it is radically different from working in the (more common) &amp;ldquo;hacked together with duct tape and prayers&amp;rdquo; kind of projects.&lt;/p&gt;</description></item></channel></rss>