<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Backend on Danilo Falcão da Silva</title><link>https://falcao.org/tags/backend/</link><description>Recent content in Backend on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 28 May 2026 18:49:26 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/backend/index.xml" rel="self" type="application/rss+xml"/><item><title>How Come Golang Is So Awesome</title><link>https://falcao.org/posts/how-come-golang-is-so-awesome/</link><pubDate>Thu, 28 May 2026 18:49:26 -0300</pubDate><guid>https://falcao.org/posts/how-come-golang-is-so-awesome/</guid><description>&lt;p>I do not use Go for everything, and I want to be honest about that.&lt;/p>
&lt;p>My stack has a hierarchy. Shell handles most of what I do. Python takes over when shell gets too complex. Go is what I reach for when I am explicitly optimizing for performance. That last tier is what this post is about — when performance is the goal, Go is awesome in a specific, practical way.&lt;/p></description></item></channel></rss>