<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on My Blog</title><link>https://blog.uptick.be/posts/</link><description>Recent content in Posts on My Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 04 Nov 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://blog.uptick.be/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>How this blog is built, checked and deployed</title><link>https://blog.uptick.be/posts/how-this-blog-is-built/</link><pubDate>Wed, 04 Nov 2026 09:00:00 +0000</pubDate><guid>https://blog.uptick.be/posts/how-this-blog-is-built/</guid><description>&lt;p&gt;This blog is a pile of Markdown files, a tiny theme and a handful of shell scripts. Publishing a post means pushing to &lt;code&gt;main&lt;/code&gt;. About a minute later it is live. This is how the pieces fit together, and what went wrong on the way.&lt;/p&gt;</description></item><item><title>Why static sites still make sense</title><link>https://blog.uptick.be/posts/why-static-sites-still-make-sense/</link><pubDate>Fri, 30 Oct 2026 08:30:00 +0000</pubDate><guid>https://blog.uptick.be/posts/why-static-sites-still-make-sense/</guid><description>&lt;p&gt;A blog does not need a database. Almost every page is the same for every visitor, so generating it once is cheaper than generating it on every request.&lt;/p&gt;</description></item><item><title>A Markdown cheat sheet for blog posts</title><link>https://blog.uptick.be/posts/markdown-cheat-sheet/</link><pubDate>Tue, 27 Oct 2026 18:00:00 +0000</pubDate><guid>https://blog.uptick.be/posts/markdown-cheat-sheet/</guid><description>&lt;p&gt;Markdown covers nearly everything a blog post needs. This is the part I actually use.&lt;/p&gt;</description></item><item><title>Five habits for a blog that survives</title><link>https://blog.uptick.be/posts/habits-for-a-blog-that-survives/</link><pubDate>Sat, 24 Oct 2026 07:45:00 +0000</pubDate><guid>https://blog.uptick.be/posts/habits-for-a-blog-that-survives/</guid><description>&lt;p&gt;Most personal blogs do not die from a lack of ideas. They die from friction. These are the habits that keep the friction low.&lt;/p&gt;</description></item><item><title>Pin your versions</title><link>https://blog.uptick.be/posts/pin-your-versions/</link><pubDate>Wed, 21 Oct 2026 19:10:00 +0000</pubDate><guid>https://blog.uptick.be/posts/pin-your-versions/</guid><description>&lt;p&gt;&amp;ldquo;It works on my machine&amp;rdquo; has a close relative: &amp;ldquo;it worked last month.&amp;rdquo; The usual cause is a tool that updated itself.&lt;/p&gt;</description></item><item><title>Reading logs without panic</title><link>https://blog.uptick.be/posts/reading-logs-without-panic/</link><pubDate>Sun, 18 Oct 2026 10:15:00 +0000</pubDate><guid>https://blog.uptick.be/posts/reading-logs-without-panic/</guid><description>&lt;p&gt;When a pipeline turns red, the instinct is to change something. The better first move is to read the log from the bottom.&lt;/p&gt;</description></item><item><title>The humble 404 page</title><link>https://blog.uptick.be/posts/the-humble-404-page/</link><pubDate>Thu, 15 Oct 2026 12:00:00 +0000</pubDate><guid>https://blog.uptick.be/posts/the-humble-404-page/</guid><description>&lt;p&gt;Every site has one, and almost nobody designs it. A missing page is a normal event, not an error worth hiding.&lt;/p&gt;</description></item><item><title>No analytics, no problem</title><link>https://blog.uptick.be/posts/no-analytics-no-problem/</link><pubDate>Mon, 12 Oct 2026 20:00:00 +0000</pubDate><guid>https://blog.uptick.be/posts/no-analytics-no-problem/</guid><description>&lt;p&gt;This site has no tracking script. It does not know how many people read it, where they came from or how long they stayed.&lt;/p&gt;</description></item><item><title>In praise of boring infrastructure</title><link>https://blog.uptick.be/posts/boring-infrastructure/</link><pubDate>Fri, 09 Oct 2026 08:00:00 +0000</pubDate><guid>https://blog.uptick.be/posts/boring-infrastructure/</guid><description>&lt;p&gt;The best infrastructure is the kind you forget about. A blog should survive months of neglect and still be there when you come back.&lt;/p&gt;</description></item><item><title>Rolling back safely</title><link>https://blog.uptick.be/posts/rolling-back-safely/</link><pubDate>Tue, 06 Oct 2026 17:30:00 +0000</pubDate><guid>https://blog.uptick.be/posts/rolling-back-safely/</guid><description>&lt;p&gt;Sooner or later a change goes live that should not have. What matters then is how fast you can undo it, and whether undoing it is safe.&lt;/p&gt;</description></item><item><title>Small scripts, big leverage</title><link>https://blog.uptick.be/posts/small-scripts-big-leverage/</link><pubDate>Sat, 03 Oct 2026 09:20:00 +0000</pubDate><guid>https://blog.uptick.be/posts/small-scripts-big-leverage/</guid><description>&lt;p&gt;The most valuable files in this repository are about forty lines long. They are shell scripts, and they hold all the logic that matters.&lt;/p&gt;</description></item><item><title>What to write about when you think you have nothing</title><link>https://blog.uptick.be/posts/what-to-write-about/</link><pubDate>Thu, 01 Oct 2026 11:00:00 +0000</pubDate><guid>https://blog.uptick.be/posts/what-to-write-about/</guid><description>&lt;p&gt;Almost everyone who starts a blog stalls on the same question: what is there to say? The answer is usually closer than it looks.&lt;/p&gt;</description></item><item><title>Hello, world</title><link>https://blog.uptick.be/posts/hello-world/</link><pubDate>Wed, 01 Jan 2025 12:00:00 +0000</pubDate><guid>https://blog.uptick.be/posts/hello-world/</guid><description>&lt;p&gt;This is a placeholder post. Replace it with your first real article.&lt;/p&gt;</description></item></channel></rss>