<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Articles on Will Codes</title><link>https://willcodes.com/en/articles/</link><description>Recent content in Articles on Will Codes</description><generator>Hugo</generator><language>en-US</language><atom:link href="https://willcodes.com/en/articles/index.xml" rel="self" type="application/rss+xml"/><item><title>App Sticker: designing loyalty that connects the physical and digital worlds</title><link>https://willcodes.com/en/articles/app-sticker-digital-loyalty-platform/</link><pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate><guid>https://willcodes.com/en/articles/app-sticker-digital-loyalty-platform/</guid><description>&lt;p&gt;Loyalty programs often start as a paper card and end as a collection of operational exceptions. &lt;a href="https://app-sticker.com/"&gt;&lt;strong&gt;App Sticker&lt;/strong&gt;&lt;/a&gt;, part of the EatSticker platform, starts from a different idea: make progress visible, enjoyable, and straightforward for both the person visiting a venue and the business operating it.&lt;/p&gt;&#10;&lt;p&gt;Instead of abstract points, people collect stickers in digital albums. A visit can begin with a QR code; every album has rules, progress, and a reward. It sounds lightweight, but it raises a concrete engineering question: how do you pair an instant mobile experience with business rules, authorization, and operations that need to be dependable?&lt;/p&gt;</description></item><item><title>Building 1 Dracma: a privacy-first lost-and-found platform</title><link>https://willcodes.com/en/articles/building-1-dracma-private-lost-and-found/</link><pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate><guid>https://willcodes.com/en/articles/building-1-dracma-private-lost-and-found/</guid><description>&lt;p&gt;&lt;a href="https://1dracma.com"&gt;1 Dracma&lt;/a&gt; started with a simple question: why does finding a lost item still depend so heavily on disconnected messages, isolated spreadsheets, and photos with no context?&lt;/p&gt;&#10;&lt;p&gt;The answer is not simply “there is no catalog.” Lost and found involves people in anxious moments, teams that need to operate quickly, and information that should not be public by default. The challenge was to turn that problem into a simple experience for visitors without oversimplifying the work and responsibility of the team managing a space.&lt;/p&gt;</description></item><item><title>The Future of Code Review: Straining Gnats Without Swallowing Camels</title><link>https://willcodes.com/en/articles/the-future-of-code-review-straining-gnats-without-swallowing-camels/</link><pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate><guid>https://willcodes.com/en/articles/the-future-of-code-review-straining-gnats-without-swallowing-camels/</guid><description>&lt;p&gt;I have been thinking a lot about how code review may change as agentic programming becomes a normal part of software development.&lt;/p&gt;&#10;&lt;p&gt;I do not have a definitive answer—and I am wary of anyone who claims to. We are still at the beginning of this transition, and we will probably make many mistakes before we understand which practices truly work, which need adaptation, and which simply stop making sense.&lt;/p&gt;&#10;&lt;p&gt;What I want to share here is a thesis. It comes from practical experience, from ideas I have accumulated over years of reviewing code, and from a recent realization: perhaps AI does not need to replace the reviewer to profoundly transform how we review software.&lt;/p&gt;</description></item><item><title>Welcome to Will Codes</title><link>https://willcodes.com/en/articles/welcome/</link><pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate><guid>https://willcodes.com/en/articles/welcome/</guid><description>&lt;p&gt;This is a place to share what I learn while building software: technical decisions, tools, projects, and the details that often disappear between one delivery and the next.&lt;/p&gt;&#10;&lt;p&gt;Posts are published in Portuguese and English so they can be useful to a broader community without losing their original context.&lt;/p&gt;</description></item></channel></rss>