<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Felipe Antolinez's Weblog: blogging</title><link href="https://antolinez.ch/" rel="alternate"/><link href="https://antolinez.ch/tags/blogging.atom" rel="self"/><id>https://antolinez.ch/</id><updated>2026-02-27T07:39:07.457006+00:00</updated><author><name>Felipe Antolinez</name></author><entry><title>Quoting Bill Gurley</title><link href="https://antolinez.ch/2026/Feb/27/gurley-writing-hones-thinking/#atom-tag" rel="alternate"/><published>2026-02-27T07:39:07.457006+00:00</published><updated>2026-02-27T07:39:07.457006+00:00</updated><id>https://antolinez.ch/2026/Feb/27/gurley-writing-hones-thinking/#atom-tag</id><summary type="html">
    &lt;blockquote cite="https://stratechery.com/2026/an-interview-with-bill-gurley-about-runnin-down-a-dream"&gt;&lt;p&gt;I think for anybody in any field, if they &lt;strong&gt;write about the edge of what's happening in their field&lt;/strong&gt;, [...] &lt;strong&gt;it really hones your thinking&lt;/strong&gt;, because when you write something down and you do it all the time, there's this &lt;strong&gt;inner desire to not be intellectually inconsistent and so you hold yourself actually to understanding things&lt;/strong&gt;. Going back to that word nuance, you really get into the nuance because you really want it to hold together once you put something down on paper and there are plenty of people outside of ourselves that have studied this writ large, but it's very well understood that &lt;strong&gt;writing is a great way to understand things to take it to a higher level&lt;/strong&gt;.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="https://stratechery.com/2026/an-interview-with-bill-gurley-about-runnin-down-a-dream"&gt;Bill Gurley&lt;/a&gt;, Stratechery interview about Gurley's book &lt;em&gt;Runnin' Down a Dream&lt;/em&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://antolinez.ch/tags/stratechery"&gt;stratechery&lt;/a&gt;, &lt;a href="https://antolinez.ch/tags/blogging"&gt;blogging&lt;/a&gt;, &lt;a href="https://antolinez.ch/tags/writing"&gt;writing&lt;/a&gt;&lt;/p&gt;



</summary><category term="stratechery"/><category term="blogging"/><category term="writing"/></entry><entry><title>My Own Little Corner of the Internet</title><link href="https://antolinez.ch/2026/Feb/22/my-own-little-corner-of-the-internet/#atom-tag" rel="alternate"/><published>2026-02-22T13:30:00+00:00</published><updated>2026-02-22T13:30:00+00:00</updated><id>https://antolinez.ch/2026/Feb/22/my-own-little-corner-of-the-internet/#atom-tag</id><summary type="html">
    &lt;p&gt;An internal initiative at work encouraging everyone to post on LinkedIn turned into me posting regularly, and some of those posts attracted quite a bit of attention and profile views. This made me realize that I didn't really have a place where interested people could learn more about me. My LinkedIn profile was my most public page on the internet and I wanted somewhere else for people to go, something more under my control. Creating my "own little corner of the internet" has been a goal of mine for a long time, and this is what pushed me over the edge to finally do it.&lt;/p&gt;

&lt;p&gt;A big inspiration has always been &lt;a href="https://simonwillison.net/"&gt;Simon Willison's blog&lt;/a&gt;, which I've been following for years. To me, his blog is the single best signal-to-noise filter in the fast-moving AI world. So in early January 2026, I decided to fork &lt;a href="https://github.com/simonw/simonwillisonblog"&gt;his code&lt;/a&gt;, which he made freely available on GitHub under an Apache 2.0 license, and adapt it for my own needs using Claude Code.&lt;/p&gt;

&lt;h3&gt;Starting a Blog in 2026&lt;/h3&gt;

&lt;p&gt;Writing helps me sharpen my thoughts and gain clarity. As long as ideas just exist in my head, it's easy to overlook inconsistencies and walk around with the impression that they're powerful and coherent. Writing them down makes it much easier to iterate, spot gaps in my logic, and see the broader implications of my thoughts. I've done this privately for years, but I wanted to start sharing as well, both internally at the company and externally.&lt;/p&gt;

&lt;p&gt;One of my frequent use cases is sharing a blog post, a podcast, or a section of a book with colleagues or friends. I rarely want to just share a link; I also want to share some thoughts of mine that go along with it. These "blogmarks", as Simon Willison calls them, are the perfect format for that.&lt;/p&gt;

&lt;p&gt;Starting a blog in 2026 feels almost retro, but social media feels too performative for me. Writing for my personal blog has a much lower barrier than writing for something where my posts are pushed into people's feeds. To share more proactively at work, I created an internal Slack channel and subscribed my blog's RSS feed to it, so colleagues who are interested can follow along.&lt;/p&gt;

&lt;p&gt;I consider myself a builder, not a writer, and I have no intention to pursue public writing professionally. I currently work as Head of AI at &lt;a href="https://rensystems.com"&gt;Ren Systems&lt;/a&gt;, and I'm perfectly happy with my job. But writing on the side makes me better at my job, not just when coding but especially for the less tangible parts of the work: thinking clearly about where our product is going and how we work together as a team.&lt;/p&gt;

&lt;p&gt;Some older posts on this blog are backfilled from books I've read and notes I had collected. I created them mostly while developing and testing the site, but the focus going forward is on new content.&lt;/p&gt;

&lt;h3&gt;The Site&lt;/h3&gt;

&lt;p&gt;This site is based on a fork of &lt;a href="https://simonwillison.net/"&gt;Simon Willison's blog&lt;/a&gt;, which he &lt;a href="https://github.com/simonw/simonwillisonblog"&gt;open-sourced on GitHub&lt;/a&gt; under the Apache 2.0 license. It is hosted on &lt;a href="https://railway.com/"&gt;Railway&lt;/a&gt; in the EU and stores content in &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL&lt;/a&gt;. DNS and CDN are provided by &lt;a href="https://www.cloudflare.com/"&gt;Cloudflare&lt;/a&gt;, and images are hosted on &lt;a href="https://cloudinary.com/"&gt;Cloudinary&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;With AI coding tools, starting a project like this is way easier than it was even a few years ago. I did not have to write a single line of code myself to build it, but without having a good understanding of the full stack from HTML, Python, Postgres, and deployment, this certainly wouldn't have been possible.&lt;/p&gt;

&lt;p&gt;Compared to Simon's site, I'm not using some of his post types, like the &lt;a href="https://simonwillison.net/2026/Feb/20/beats/#atom-everything"&gt;new "beat" items&lt;/a&gt; such as TILs, vibe-coded tools, or release notes for his repositories. Instead, I added a &lt;a href="https://antolinez.ch/books/"&gt;books section&lt;/a&gt; where I document what I've read or am currently reading, along with my notes. Individual blog posts can link to a specific book, and each book page collects all related posts in reverse chronological order.&lt;/p&gt;

&lt;p&gt;I also adapted the layout to something less retro that fits me better. As inspiration for the feed layout, I used the Swiss online-only news site &lt;a href="https://www.republik.ch/feed"&gt;Republik&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I'm not perfectly happy with the site yet, but I wanted to release it anyway. Otherwise, it would never see the light of day and remain a partly finished project, like so many things now that AI coding tools have made it so easy to start. I'll keep iterating on the layout and functionality over time. After all, I'm learning and changing, and so should my personal corner of the internet!&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://antolinez.ch/tags/blogging"&gt;blogging&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="blogging"/></entry></feed>