<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>English on Guilherme Miranda</title><link>https://guilhermealbm.com/languages/english/</link><description>Recent content in English on Guilherme Miranda</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Jul 2026 08:56:33 +0100</lastBuildDate><atom:link href="https://guilhermealbm.com/languages/english/index.xml" rel="self" type="application/rss+xml"/><item><title>Reviving my old Kindle</title><link>https://guilhermealbm.com/posts/reviving-my-old-kindle/</link><pubDate>Wed, 11 Mar 2026 00:00:00 +0000</pubDate><guid>https://guilhermealbm.com/posts/reviving-my-old-kindle/</guid><description>&lt;h4 id="andor-a-small-project-that-reminded-me-how-i-learned-to-build-things"&gt;
 and/or: A small project that reminded me how I learned to build things
 &lt;a class="heading-link" href="#andor-a-small-project-that-reminded-me-how-i-learned-to-build-things"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h4&gt;
&lt;p&gt;I bought this Kindle back in 2016. It worked perfectly for years, until I got a newer one and the old device slowly became useless. I even tried giving each of them a different role, using the old one on public transport and the new one at home, but in practice I always ended up reaching for the new one.&lt;/p&gt;</description></item><item><title>Compose Previews as the Source of Truth</title><link>https://guilhermealbm.com/posts/compose-previews-as-the-source-of-truth/</link><pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate><guid>https://guilhermealbm.com/posts/compose-previews-as-the-source-of-truth/</guid><description>&lt;h4 id="andor-less-setup-less-repetition-better-ide-workflow"&gt;
 and/or: less setup, less repetition, better IDE workflow
 &lt;a class="heading-link" href="#andor-less-setup-less-repetition-better-ide-workflow"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h4&gt;
&lt;p&gt;Over the last few years, I’ve felt Android testing get a lot better, both in tooling and in how teams talk about it. Unit tests have always been the default conversation, mostly because the Java ecosystem has had that figured out. But integration tests and screenshot tests never got the same love. They were annoying to set up, slower, flaky in weird ways, and very easy to skip because the payoff didn’t always feel worth the fight.&lt;/p&gt;</description></item><item><title>Why Focus in Compose Is About Structure, Not Modifiers</title><link>https://guilhermealbm.com/posts/why-focus-in-compose-is-about-structure-not-modifiers/</link><pubDate>Sun, 25 Jan 2026 00:00:00 +0000</pubDate><guid>https://guilhermealbm.com/posts/why-focus-in-compose-is-about-structure-not-modifiers/</guid><description>&lt;h4 id="andor-the-most-underrated-interaction-mechanism-on-android-is-becoming-important"&gt;
 and/or: the most underrated interaction mechanism on Android is becoming important
 &lt;a class="heading-link" href="#andor-the-most-underrated-interaction-mechanism-on-android-is-becoming-important"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h4&gt;
&lt;p&gt;About one and a half years ago, when I started to work focused (no pun intended!) on Android TV, I tried to anticipate what would change in my daily work. Other than a very different form factor and input type, I didn&amp;rsquo;t expect many surprises. And, in a way, I was right.&lt;/p&gt;</description></item></channel></rss>