<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tools on Jakub Jarosz</title>
    <link>/tags/tools/</link>
    <description>Recent content in Tools on Jakub Jarosz</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 11 Mar 2025 06:00:27 +0100</lastBuildDate>
    <atom:link href="/tags/tools/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Benchmarking: What You Can&#39;t Miss in Go 1.24</title>
      <link>/code/benchmarking-what-you-cannot-miss-in-go-1.24/</link>
      <pubDate>Tue, 11 Mar 2025 06:00:27 +0100</pubDate>
      <guid>/code/benchmarking-what-you-cannot-miss-in-go-1.24/</guid>
      <description>&lt;p&gt;For us Go developers, writing less code means fewer opportunities to make mistakes. But how about achieving more by doing less? That sounds appealing. Isn&amp;rsquo;t it? And how about spending less time writing code to force the compiler not to optimise the benchmarking functions?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Essential Tools for Go Developers</title>
      <link>/code/essential-tools-for-go-developers/</link>
      <pubDate>Sat, 23 Nov 2024 09:31:27 +0100</pubDate>
      <guid>/code/essential-tools-for-go-developers/</guid>
      <description>&lt;p&gt;Before writing Go programs, you must set up your editor and install essential tools. A short list includes &lt;code&gt;staticcheck&lt;/code&gt;, &lt;code&gt;gosec&lt;/code&gt;, &lt;code&gt;govulncheck&lt;/code&gt;, and &lt;code&gt;gofumpt&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
