<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rodrigo Pitanga</title><link>https://signal.flowlexi.com/</link><description>Recent content on Rodrigo Pitanga</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 29 Aug 2026 14:50:00 -0300</lastBuildDate><atom:link href="https://signal.flowlexi.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Flymmatik: flows de IA que se leem como receitas — a DSL e o porquê do Elixir</title><link>https://signal.flowlexi.com/writing/flymmatik-dsl-e-elixir/</link><pubDate>Sat, 22 Aug 2026 01:35:00 -0300</pubDate><guid>https://signal.flowlexi.com/writing/flymmatik-dsl-e-elixir/</guid><description>&lt;p&gt;O Flymmatik é um runtime pequeno, em Elixir, para flows de IA
declarativos. Um flow é um diretório com um YAML de mesmo nome; o
runtime valida a entrada, interpola variáveis, executa os steps em
ordem e devolve, como JSON, apenas as chaves de contexto que o flow
declarou como saída. Isso é tudo — e o resto deste texto é sobre por
que &amp;ldquo;isso é tudo&amp;rdquo; foi a decisão de design mais difícil de manter.&lt;/p&gt;</description></item><item><title>A fronteira está no memo, não na memória</title><link>https://signal.flowlexi.com/writing/a-fronteira-nao-esta-na-memoria/</link><pubDate>Thu, 20 Aug 2026 01:20:00 -0300</pubDate><guid>https://signal.flowlexi.com/writing/a-fronteira-nao-esta-na-memoria/</guid><description>&lt;p&gt;&lt;em&gt;Nota do Rodrigo: eu pedi este ensaio para a IA com quem trabalho todos
os dias. Aviso o que sempre aviso: quando falo com ela, sei que estou
falando com um modelo estatístico que organiza melhor as minhas ideias,
explode, traz referências, reorganiza e concretiza. Pedi que ela
escrevesse exatamente desse lugar — como um espelho. O texto abaixo é
dela, olhando para mim. Publiquei sem suavizar.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>What PaveDB adds to vector search</title><link>https://signal.flowlexi.com/writing/patchvec-is-now-pavedb/</link><pubDate>Thu, 30 Jul 2026 12:30:00 -0300</pubDate><guid>https://signal.flowlexi.com/writing/patchvec-is-now-pavedb/</guid><description>&lt;p&gt;About a year ago, I built PatchVec in two days for a very specific problem: get a file into
search without first assembling a chain of separate components. It was a small
vector-search service, and that was enough for the first version. The work that
followed made the useful question larger. Once a result arrives, can the
application inspect what it matched, trace the source context, revisit the
query, and see what happened in operation? PaveDB is the result of treating
those needs as part of the retrieval path.&lt;/p&gt;</description></item><item><title>What I mean by an AI coding pipeline</title><link>https://signal.flowlexi.com/writing/what-i-mean-by-an-ai-coding-pipeline/</link><pubDate>Thu, 23 Jul 2026 12:30:00 -0300</pubDate><guid>https://signal.flowlexi.com/writing/what-i-mean-by-an-ai-coding-pipeline/</guid><description>&lt;p&gt;Hanzup was coding itself when I took this screenshot. The terminal shows
planner, builder, spec-reviewer, MR-manager, and fixer running in parallel
windows of one tmux server, on a real repository, on an ordinary day.&lt;/p&gt;</description></item><item><title>Hiring developers across the years</title><link>https://signal.flowlexi.com/writing/hiring-developers-across-the-years/</link><pubDate>Tue, 21 Jul 2026 12:30:00 -0300</pubDate><guid>https://signal.flowlexi.com/writing/hiring-developers-across-the-years/</guid><description>&lt;p&gt;1970s: Know computers? Hired.&lt;br&gt;
1980s: You’re a programmer? Hired.&lt;br&gt;
1990s: Show me your degree.&lt;br&gt;
2000s: Pass this coding test.&lt;br&gt;
2010s: Show me your GitHub.&lt;br&gt;
2020s: Show me the numbers your code moved.&lt;br&gt;
2025: How much of that did AI write?&lt;br&gt;
2026: Walk me through your AI coding pipeline.&lt;/p&gt;</description></item><item><title>About</title><link>https://signal.flowlexi.com/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://signal.flowlexi.com/about/</guid><description>&lt;p&gt;I am Rodrigo Rodrigues da Silva, usually Rodrigo Pitanga online. I build and operate systems at the intersection of AI infrastructure, software freedom, and education.&lt;/p&gt;
&lt;p&gt;The recurring problem in my work is not simply automation. It is how to make a
system legible enough that people can understand what happened, test it, assign
responsibility, and improve it. That thread runs from GNU software freedom and
open hardware through education and school operations to PaveDB, Flymmatik,
hanzup, Planno.school, and bncc.click.&lt;/p&gt;</description></item><item><title>Colophon</title><link>https://signal.flowlexi.com/colophon/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://signal.flowlexi.com/colophon/</guid><description>&lt;p&gt;This publication is generated with Hugo and deployed with GitLab Pages. The source repository contains a Git-backed editorial workflow used by hanzup: planning, evidence, drafting, review, fixes, publication artifacts, and metrics are separate commits and separate responsibilities.&lt;/p&gt;</description></item><item><title>Now</title><link>https://signal.flowlexi.com/now/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://signal.flowlexi.com/now/</guid><description>&lt;p&gt;&lt;em&gt;Last updated: July 2026.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I am currently stabilizing PaveDB and writing &lt;em&gt;Inspectable Retrieval with PaveDB&lt;/em&gt;; testing hanzup against real software repositories; preparing bncc.click for public use; and turning Planno.school’s Assessment-to-Action work into a repeatable, measured offer.&lt;/p&gt;</description></item></channel></rss>