<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Notes — Maxim Beregov</title><link>https://beregov.me/notes/</link><description>Notes by Maxim Beregov: systems, teams, a home lab, a workshop.</description><language>en</language><lastBuildDate>Tue, 29 Sep 2026 03:30:00 +0300</lastBuildDate><atom:link href="https://beregov.me/notes/index.xml" rel="self" type="application/rss+xml"/><item><title>How this site came together</title><link>https://beregov.me/notes/how-this-site-was-made/</link><pubDate>Tue, 29 Sep 2026 03:30:00 +0300</pubDate><guid>https://beregov.me/notes/how-this-site-was-made/</guid><description>&lt;p&gt;I built this site together with AI in one long session. The most interesting&#10;part wasn&amp;rsquo;t the code but how the idea of what the site should be kept&#10;changing.&lt;/p&gt;&#10;&lt;h2 id="a-brand-book-made-for-me--but-not-for-this"&gt;A brand book made for me — but not for this&lt;/h2&gt;&#10;&lt;p&gt;Some time ago I had a brand book made: neon green, a space tunnel, a pixel&#10;font, headings in small caps. The first version of the site followed it to the&#10;letter. It came out neat and recognisable — and I liked it less than the&#10;plain layout before it.&lt;/p&gt;</description></item><item><title>README for people, AGENTS.md for agents</title><link>https://beregov.me/notes/readme-and-agents/</link><pubDate>Tue, 29 Sep 2026 02:00:00 +0300</pubDate><guid>https://beregov.me/notes/readme-and-agents/</guid><description>&lt;p&gt;Every repository of mine — from a Go library to a wrapper around someone&#10;else&amp;rsquo;s image — has four files: &lt;code&gt;README.md&lt;/code&gt;, &lt;code&gt;CONTRIBUTING.md&lt;/code&gt;, &lt;code&gt;CHANGELOG.md&lt;/code&gt;&#10;and &lt;code&gt;AGENTS.md&lt;/code&gt;. All four are required, with no exceptions by repository type.&lt;/p&gt;&#10;&lt;p&gt;There is one main rule: &lt;strong&gt;README, CONTRIBUTING and CHANGELOG are written by a&#10;person for a person. AGENTS.md is written by an agent for an agent. They don&amp;rsquo;t&#10;mix in either direction.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;h2 id="why-one-text-wont-do"&gt;Why one text won&amp;rsquo;t do&lt;/h2&gt;&#10;&lt;p&gt;A document addressed to both readers serves neither. The person is put off by&#10;machine density: lists of commands, invariants, prohibitions with no&#10;explanation. The executor is put off by everything else: introductions,&#10;reasons, invitations to &amp;ldquo;read this to get the idea&amp;rdquo;. In the end each reads&#10;half and misses what matters.&lt;/p&gt;</description></item><item><title>Write the lesson down now, not at the end</title><link>https://beregov.me/notes/capture-lessons-now/</link><pubDate>Mon, 28 Sep 2026 19:00:00 +0300</pubDate><guid>https://beregov.me/notes/capture-lessons-now/</guid><description>&lt;p&gt;I used to put notes off until later: finish the task, then write down what I&#10;learned. Then &amp;ldquo;later&amp;rdquo; came, and half of it was gone. Especially the most&#10;valuable part: why we chose this option and not the one next to it.&lt;/p&gt;&#10;&lt;p&gt;Now the rule is different: &lt;strong&gt;a decision, a lesson, a procedure or an important&#10;fact appears — I write it down right away&lt;/strong&gt;, as a short note in a shared inbox&#10;folder, and carry on working.&lt;/p&gt;</description></item></channel></rss>