<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Franz</title><link>https://franzego.github.io/</link><description>Recent content on Franz</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://franzego.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Const In C++</title><link>https://franzego.github.io/posts/const-in-cpp/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://franzego.github.io/posts/const-in-cpp/</guid><description>&lt;h1 id="the-const-keyword"&gt;The Const Keyword&lt;/h1&gt;
&lt;p&gt;For the longest time, I simply used the const keyword because it was a blanket command to use it. All tutorials and blog advised to use it. They all gave their explanations. I did not understand most of it. I just knew to use const when passing variables of certain types into a function - a const reference to be precise.&lt;/p&gt;
&lt;p&gt;A few days ago while writing C++ for a little sqlite clone I was writing, it clicked! It just made sense.&lt;/p&gt;</description></item><item><title>Log Structured Merge Trees</title><link>https://franzego.github.io/posts/log-structured-merge-trees/</link><pubDate>Fri, 29 May 2026 01:47:21 +0100</pubDate><guid>https://franzego.github.io/posts/log-structured-merge-trees/</guid><description>&lt;h1 id="building-an-lsm-tree-in-go-understanding-the-moving-parts"&gt;Building an LSM Tree in Go: Understanding the Moving Parts&lt;/h1&gt;
&lt;p&gt;&lt;img alt="LSM Tree Simple Illustration" loading="lazy" src="https://franzego.github.io/posts/log-structured-merge-trees/lsm_tree.png"&gt;&lt;/p&gt;
&lt;p&gt;Log-Structured Merge (LSM) Trees have become ubiquitous in today&amp;rsquo;s database world. The name has become almost synonymous with modern storage engines. LSM trees sit behind databases like Cassandra, CockroachDB, RocksDB, LevelDB, and Pebble.&lt;/p&gt;
&lt;p&gt;One thing these systems have in common is their use in write-heavy workloads. The goal of an LSM is to ingest writes at a large scale, as quickly as possible. It sacrifices some read speed for this, because nothing is ever free. Even then, some optimizations can make that tradeoff manageable.&lt;/p&gt;</description></item><item><title>Hello, World: Building a Go-Powered Blog from Scratch</title><link>https://franzego.github.io/posts/hugo-project-setup/</link><pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate><guid>https://franzego.github.io/posts/hugo-project-setup/</guid><description>&lt;p&gt;Trying to set up a personal blog is not quite as straightforward. There was no one stop guide for setting up one using github pages. I had to google a lot, make mistakes and grill gemini for answers. It was not so technical or difficult but after solving the issue, I decided to document the steps i followed for my future self and anyone who ends up in the same position as I was.&lt;/p&gt;</description></item></channel></rss>