<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Toolchain on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/toolchain/</link><description>Recent content in Toolchain on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Thu, 26 Mar 2026 09:00:00 +0800</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/toolchain/rss.xml" rel="self" type="application/rss+xml"/><item><title>Standard Library, Testing, and Toolchain: A Panoramic View of Go Engineering Practices</title><link>https://blog.mickeyzzc.tech/en/posts/programming/go-stdlib-testing-toolchain/</link><pubDate>Thu, 26 Mar 2026 09:00:00 +0800</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/programming/go-stdlib-testing-toolchain/</guid><description>&lt;p&gt;After three articles of our journey—why choose Go, basic syntax and concurrency, interfaces and generics—we&amp;rsquo;ve reached the finale of the Go chapter, time to connect the engineering practices.&lt;/p&gt;
&lt;p&gt;Go&amp;rsquo;s engineering capacity also shows up in its standard library, testing framework, and toolchain. They make up the daily working environment for Go developers and underpin rapid construction of reliable, maintainable software.&lt;/p&gt;</description></item></channel></rss>