<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Guilherme Elias</title>
    <subtitle>Data scientist, product builder, and founder.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://geliasrd.com/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://geliasrd.com"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-05-15T00:00:00+00:00</updated>
    <id>https://geliasrd.com/atom.xml</id>
    <entry xml:lang="en">
        <title>Hello, project log</title>
        <published>2026-05-15T00:00:00+00:00</published>
        <updated>2026-05-15T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://geliasrd.com/projects/hello-project-log/"/>
        <id>https://geliasrd.com/projects/hello-project-log/</id>
        
        <content type="html" xml:base="https://geliasrd.com/projects/hello-project-log/">&lt;p&gt;This is the first post in &lt;code&gt;&#x2F;projects&#x2F;&lt;&#x2F;code&gt;. I started this space to document the
things I’m building — both at work (RuralTrace, FSData, consulting) and on my
own time (papers, experiments, side projects).&lt;&#x2F;p&gt;
&lt;h2 id=&quot;why-a-project-log&quot;&gt;Why a project log&lt;&#x2F;h2&gt;
&lt;p&gt;A few reasons converged:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;External memory.&lt;&#x2F;strong&gt; I find a bug, solve it, forget the solution, hit the
same bug six months later. Writing it down once costs less than rediscovering
it three times.&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;Sharper thinking.&lt;&#x2F;strong&gt; I notice gaps in my reasoning faster when I have to
explain something to a hypothetical reader than when I just keep it in my
head.&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;Public surface.&lt;&#x2F;strong&gt; It’s nice to have a single URL to point people at when
someone asks “what are you working on?”&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;h2 id=&quot;what-goes-here&quot;&gt;What goes here&lt;&#x2F;h2&gt;
&lt;p&gt;Roughly three categories:&lt;&#x2F;p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Project write-ups&lt;&#x2F;strong&gt; — technical decisions, architecture, what worked,
what didn’t. Honest post-mortems.&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;Field notes&lt;&#x2F;strong&gt; — short observations that aren’t worth a full post but
shouldn’t be lost. Things like “wrong way to set up a Polars pipeline”
or “interesting paper I read on time series clustering.”&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;Tools &amp;amp; dotfiles&lt;&#x2F;strong&gt; — when I configure something the right way after
getting it wrong six times, I write down the right way.&lt;&#x2F;li&gt;
&lt;&#x2F;ol&gt;
&lt;h2 id=&quot;markdown-features-this-template-supports&quot;&gt;Markdown features this template supports&lt;&#x2F;h2&gt;
&lt;p&gt;Inline &lt;code&gt;code&lt;&#x2F;code&gt; works as expected. So do code blocks:&lt;&#x2F;p&gt;
&lt;pre data-lang=&quot;python&quot; class=&quot;language-python &quot;&gt;&lt;code class=&quot;language-python&quot; data-lang=&quot;python&quot;&gt;# How I currently bootstrap a new Python project
uv init my-project
cd my-project
uv add polars duckdb pyarrow
&lt;&#x2F;code&gt;&lt;&#x2F;pre&gt;
&lt;p&gt;Bold and &lt;em&gt;italic&lt;&#x2F;em&gt;. &lt;a rel=&quot;noopener&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;geliasrd.com&quot;&gt;Links&lt;&#x2F;a&gt; open in a new tab when external.&lt;&#x2F;p&gt;
&lt;blockquote&gt;
&lt;p&gt;Block quotes for callouts and citations.&lt;&#x2F;p&gt;
&lt;&#x2F;blockquote&gt;
&lt;p&gt;Lists, both ordered and unordered, render with brutalist accents. Headings
(H2, H3) use the same Instrument Serif as the rest of the site.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;next-up&quot;&gt;Next up&lt;&#x2F;h2&gt;
&lt;p&gt;The first real post is going to be on how I structure data pipelines at
RuralTrace — specifically the decision to use DuckDB as the analytical layer
even when the source data lives in Postgres.&lt;&#x2F;p&gt;
</content>
        
    </entry>
</feed>
