<?xml version="1.0" encoding="utf-8" ?>
<rss
  version="2.0"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:atom="http://www.w3.org/2005/Atom"
>
    <channel>
        <title>Caleb's Blog</title>
        <link>https://caleb.is-a.dev/blog</link>
        <description
    >Posts about all kinds of cool stuff I came across</description>
        <lastBuildDate>Sat, 14 Nov 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>Caleb</copyright>
        <atom:link
      href="https://caleb.is-a.dev/blog/feed.xml"
      rel="self"
      type="application/rss+xml"
    />
        <item>
            <title><![CDATA[88x31 Buttons]]></title>
            <link>https://caleb.is-a.dev/blog/88x31-buttons</link>
            <guid
        isPermaLink="false"
      >https://caleb.is-a.dev/blog/88x31-buttons</guid>
            <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
            <description
      ><![CDATA[A tiny piece of 90s web culture]]></description>
            <content:encoded
      ><![CDATA[<p><img src="/img/88x31-buttons.png" alt="88x31 Buttons"/></p><p>Hello there, on today&#x27;s post, we&#x27;re going to be going through a small culture of the web, 88x31 buttons, one of the best things the old web has left behind. I learned about them from my friend, <a href="https://codeberg.org/louiszn">Louis</a>.</p>
<h1>So, What Are 88x31 Buttons?</h1>
<p>88x31 buttons (often called web badges or stickers) are small, rectangular (88px by 31px) buttons that are used to link to other pages, promote your favorite software, or express your interests. Most of the time, they are placed in the footers or sidebars of personal websites, often static images or animated GIFs.</p>
<h1>How They Even Became a Thing</h1>
<p>In 1995, <a href="https://en.wikipedia.org/wiki/Netscape">Netscape</a> put out a small rectangular badge for its &quot;Netscape Now!&quot; campaign, and anyone who wanted to show support (or just get the badge) slapped it on their page, and every site that did just became a free ad billboard for Netscape.</p>
<p>Right after, <a href="https://en.wikipedia.org/wiki/Microsoft">Microsoft</a> answered with a badge reading &quot;Best viewed in Internet Explorer&quot; one year later (1996). And funnily, Netscape had its own &quot;Best viewed in Netscape&quot; version as well.</p>
<p>This all was <a href="https://en.wikipedia.org/wiki/Browser_wars">the browser wars</a> if you didn&#x27;t know, and personal homepages were the battlefield. Other companies, hosts and tools also joined in, and 88x31 became the default size for every web badge. And later on, <a href="https://www.iab.com/wp-content/uploads/2015/10/IAB_Display_Mobile_Creative_Guidelines_HTML5_2015.pdf">88x31 buttons were officially classified as a Micro Bar ad unit by IAB</a>.</p>
<h1>Why They Faded Out (and Came Back, Somewhat)</h1>
<p>By the mid 2000s, these web badges started fading out, because personal sites were losing ground for social media, <a href="https://caleb.is-a.dev/blog/rss-feeds">RSS Feeds</a>, publishing and newsletter sites.</p>
<p>And starting in the late 2010s, people tired of algorithm based social media grew more, and platforms like <a href="https://neocities.org/browse?tag=88x31">Neocities</a> provided people a place to build the handmade personal websites like the ones from the old web. Buttons came back with them, but now with a different purpose.</p>
<p><a href="https://neocities.org/">Neocities</a></p>
<h1>How to Add One to Your Site</h1>
<p>First, search for 88x31 button to add. Then on your website footer, add something like this (mine as example):</p>
<pre><code class="language-html">&lt;a href=&quot;https://caleb.is-a.dev/&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;
  &lt;img
    src=&quot;https://caleb.is-a.dev/88x31.jpg&quot;
    alt=&quot;Pumkin pie&quot;
    title=&quot;Pumkin pie&quot;
    width=&quot;88&quot;
    height=&quot;31&quot;
  /&gt;
&lt;/a&gt;
</code></pre>
<p>Which basically adds a small 88x31 button on your footer:</p>
<a href="https://caleb.is-a.dev/" target="_blank" rel="noopener" class="undecorated w-fit">
<img src="https://caleb.is-a.dev/88x31.jpg" alt="Pumkin pie" title="Pumkin pie" width="88" height="31" data-strict="true"/>
</a>
<p>To lay out a bunch of them, a flex row should be simple enough:</p>
<pre><code class="language-css">.buttons {
  display: flex;
  flex-wrap: wrap; /* responsiveness */
  gap: 4px; /* or whatever value you&#x27;d like */
}
</code></pre>
<h1>What to Put On Your Row</h1>
<p>No rules, but most people go with some kinds of mix between:</p>
<ul>
<li>Friends&#x27; websites</li>
<li>Fans website</li>
<li>Their favorite technologies, tools, or platforms</li>
<li>Maybe their favorite games, or whatever they&#x27;re into</li>
</ul>
<h1>Make Your Own</h1>
<p>If you want your friends to link to you on their personal sites, you need a button as well. Here are two options:</p>
<h2>1. Search for an image online</h2>
<p><a href="https://www.google.com/search?q=88x31+button+collection">Search for a button collections on google</a> to find one (you might need to resize/crop it to be 88x31). You can find some cool badges on websites like:</p>
<ul>
<li><a href="https://yesterweb.org/graphics/buttons">yesterweb.org</a> - button collection</li>
<li><a href="https://jamesg.blog/buttons">jamesg.blog</a> - button collection</li>
<li><a href="https://neocities.org/browse?tag=88x31">neocities.org</a> - collection of websites with buttons</li>
<li><a href="https://cooltext.com/">cooltext.com</a> - custom text buttons</li>
</ul>
<a href="https://cooltext.com/" target="_blank" rel="noopener" class="undecorated w-fit">
<img src="https://caleb.is-a.dev/img/yeehaw.png" alt="Yee haw!" title="Yee haw!" width="88" height="31" data-strict="true"/>
</a>
<h2>2. Draw one from scratch</h2>
<p>Make or draw one in any image editor.</p>
<h2>Then?</h2>
<p>Name your button to a name that&#x27;s easy to remember, like <code>badge.png</code> or <code>88x31.png</code>, and put it somewhere stable because other friends will be pointing at it.</p>
<h1>Self Hosting vs Hotlinking</h1>
<p>Two ways to show a friend&#x27;s button (behaving differently):</p>
<p><strong>Hotlinking</strong>: means your <code>&lt;img&gt;</code> points to their badge image URL. If they remake their button and keep the same file name and type (say <code>88x31.png</code> is replaced by a new <code>88x31.png</code>), the change will happen on your website as well. But if their site goes down, or they rename their file name (or extension), your button breaks. If they swap the image for something weird, it shows up on your page as well, so that means you&#x27;re trusting your friend on this one.</p>
<p><strong>Self Hosting</strong>: means you download the image and serve it yourself. It&#x27;s stable and safe, but you have to update it by hand whenever they change theirs.</p>
<p>I usually like to hotlink friends and self host other stuff. Pick whatever you&#x27;re comfy with.</p>
<h1>Go Make One</h1>
<p>Go make or find a button, add a few to your personal site footer, and if you want, send me yours so I can add it to mine ;]</p>
<p>See you in the next post!</p>
<h1>Sources</h1>
<ul>
<li>“88x31 Buttons/Badges.” <em>Vale</em>, <a href="https://vale.rocks/portfolio/88x31-buttons-badges">vale.rocks/portfolio/88x31-buttons-badges</a>.</li>
<li>&quot;88x31.&quot; <em>IndieWeb</em>, <a href="https://indieweb.org/88x31">indieweb.org/88x31</a></li>
<li>&quot;Browser Wars.&quot; <em>Wikipedia</em>, <a href="https://en.wikipedia.org/wiki/Browser_wars">en.wikipedia.org/wiki/Browser_wars</a></li>
<li>&quot;Web Badge.&quot; <em>Wikipedia</em>, <a href="https://en.wikipedia.org/wiki/Web_badge">en.wikipedia.org/wiki/Web_badge</a></li>
</ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RSS Feeds]]></title>
            <link>https://caleb.is-a.dev/blog/rss-feeds</link>
            <guid
        isPermaLink="false"
      >https://caleb.is-a.dev/blog/rss-feeds</guid>
            <pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate>
            <description
      ><![CDATA[What RSS is, how it works, and which readers to use to follow your favorite blogs]]></description>
            <content:encoded
      ><![CDATA[<p><img src="https://images.unsplash.com/photo-1638428355507-89456d0fafd5?q=80&amp;w=1632&amp;auto=format&amp;fit=crop&amp;ixlib=rb-4.1.0&amp;ixid=NHwxMjA3fDA%3D" alt="RSS Feeds"/></p><p>Hiya, on this blog post, we&#x27;re going to be covering what RSS feeds are, how they work, how to use them, some popular RSS readers (aggregator apps), and pros &amp; cons of using RSS feeds.</p>
<h1>So, What are RSS Feeds?</h1>
<p>According to Wikipedia, RSS (RDF Site Summary, Rich Site Summary or Really Simple Syndication) is a web feed that allows users and applications to access updates to websites in a standardized, computer-readable format, created in March 1999 by engineers at <a href="https://en.wikipedia.org/wiki/Netscape">Netscape</a>.</p>
<p><a href="https://en.wikipedia.org/wiki/RSS">RSS</a></p>
<p>Basically, RSS is a way to subscribe to changes that happen to websites, such as blogs, podcasts, news, any type of frequently updated content (most of the time). For example, you subscribe to channels on YouTube so that you don&#x27;t miss any videos uploaded by your favorite channels. But how do you subscribe to changes to a website? Manually checking every website consumes a lot of time, emails get cluttered, and other options don&#x27;t always work well. To these issues, RSS was the answer. Thanks to RSS readers, <mark class="secondary">all of the new posts are automatically gathered in our dashboard waiting for us to open them and read.</mark></p>
<h1>How Do RSS Feeds Work?</h1>
<p>An RSS feed is just an XML file that lives on the website&#x27;s server.</p>
<pre><code class="language-xml">&lt;rss version=&quot;2.0&quot; xmlns:content=&quot;http://purl.org/rss/1.0/modules/content/&quot;&gt;
  &lt;channel&gt;
    &lt;language&gt;en&lt;/language&gt;
    &lt;title&gt;My Blog&lt;/title&gt;
    &lt;link&gt;https://caleb.is-a.dev/blog&lt;/link&gt;
    &lt;description&gt;Posts about things i like&lt;/description&gt;
    &lt;item&gt;
      &lt;title&gt;RSS Still Works&lt;/title&gt;
      &lt;link&gt;https://caleb.is-a.dev/blog/rss-feeds&lt;/link&gt;
      &lt;pubDate&gt;Tue, 10 Nov 2026 00:00:00 GMT&lt;/pubDate&gt;
      &lt;description&gt;What RSS Feeds are, why to use them, how they work, how to use them, popular readers, and pros/cons of using RSS feeds&lt;/description&gt;
      &lt;content:encoded&gt;Heya everyone, ...&lt;/content:encoded&gt;
    &lt;/item&gt;
    &lt;item&gt;
      ...
    &lt;/item&gt;
  &lt;/channel&gt;
&lt;/rss&gt;
</code></pre>
<p>Every time your fav blogger publishes a new post, a new <code>&lt;item&gt;</code> gets added, often with automated scripts. Then your reader checks that file every so often, compares it to what it has already recorded, and shows you the new items. So, you might be wondering, what is an RSS reader?</p>
<h1>RSS Readers</h1>
<p>RSS readers (or aggregator apps) are platforms that collect updates from your favorite blogs, news sites, podcasts, and other sites into a single and organized inbox without algorithmic feeds or anything. The two most popular RSS readers are <a href="https://feedly.com/">Feedly</a> and <a href="https://www.inoreader.com/">Inoreader</a>.</p>
<p><img src="https://caleb.is-a.dev/img/feedly.png" alt="Feedly RSS Reader"/></p>
<p>Both Feedly and Inoreader have features to follow a resource (subscribe to a website) via an RSS link, categorize different resources under different folders, track what you&#x27;ve read and haven&#x27;t read, options to save (read later), AI powered feed, and more.</p>
<p><img src="https://caleb.is-a.dev/img/feedly-feed.png" alt="Feedly Feed UI"/></p>
<p><img src="https://caleb.is-a.dev/img/inoreader-feed.png" alt="Inoreader Feed UI"/></p>
<p>You can find more about the comparision between Feedly and Inoreader <a href="https://daily.dev/blog/feedly-vs-inoreader-for-developers/">here</a>.</p>
<p><a href="https://daily.dev/blog/feedly-vs-inoreader-for-developers/">Feedly vs Inoreader for developers in 2026</a></p>
<h1>How to Subscribe to a Website via RSS</h1>
<ol>
<li>Go to your favorite blogger&#x27;s blog page.</li>
<li>Look for an orange icon that looks like a wifi signal, the icon commonly used for RSS (<img src="https://cdn3.emoji.gg/emojis/680306-rss.png" alt="rss" width="20" height="20"/>), or any link that says to subscribe through RSS. If you don&#x27;t find any, many modern readers (like Feedly) also let you paste a normal page URL and find the feed for you.</li>
<li>Go to your reader and enter in the RSS link you want to subscribe to.</li>
<li>Voilà, your reader automatically pulls any new content to save you time!</li>
</ol>
<h1>Pros and Cons of Using RSS Feeds</h1>
<h2>Pros</h2>
<ul>
<li><strong>You are the one to choose resources to follow</strong> - You receive content <strong>strictly</strong> from the sources you choose, free from social media feeds, distractions, or targeted ads (though ads might depend on the platform that you&#x27;re using).</li>
<li><strong>Time saver</strong> - RSS readers save us time by gathering all updates in a single place to browse, saving you the time that you waste by checking sites one by one.</li>
<li><strong>Privacy</strong> - You don&#x27;t have to hand over your email to a blog website just because you liked the content they post (a hosted reader still sees what you read though, so self host a reader if that matters to you).</li>
<li><strong>Offline reading</strong> - Many reader apps cache posts so you can read anywhere.</li>
</ul>
<h2>Cons</h2>
<ul>
<li><strong>Information flood</strong> - Subscribing to too many active sites can flood your reader with hundreds of daily unread posts, making it hard to keep up with everything.</li>
<li><strong>Limited content</strong> - Some sites choose to show only a truncated version of the real post content to force you to click a link to read the full article.</li>
<li><strong>No interactivity</strong> - Feeds are mostly text and images, so no animations or interactive embeds or cards or anything.</li>
<li><strong>Lack of adoption</strong> - Not everyone uses RSS feeds, many modern web platforms don&#x27;t even support RSS (often requires subscribing through email), and only a very small slice of the internet users use RSS as well.</li>
<li><strong>Very limited analytics for publishers</strong> - Publishers don&#x27;t see who subscribed to their RSS, most of the time, usually just subscriber count, making it harder to track analytics about the subscribed readers.</li>
</ul>
<h1>How I Use Them</h1>
<p>I use <a href="https://feedly.com/">Feedly</a> to follow the blogs I like, split into two folders:</p>
<ul>
<li><strong>Dev Blogs:</strong> individual developer&#x27;s writings, like <a href="https://blog.pragmaticengineer.com/">The Pragmatic Engineer</a> and <a href="https://cassidoo.co/tag/technical/">Cassidy Williams</a>.</li>
<li><strong>Company Blogs:</strong> blogs from companies, like <a href="https://www.canva.dev/blog/engineering/">Canva Engineering Blog</a> and <a href="https://discord.com/category/engineering">Discord Blog</a>.</li>
</ul>
<div class="markdown-alert markdown-alert-tip">
<div class="markdown-alert-title">Tip</div>
<p>If you like the things I post and want to include me in your subscriptions, here&#x27;s <a href="https://caleb.is-a.dev/blog/rss.xml">my RSS feed</a> <img src="https://cdn3.emoji.gg/emojis/6928-pandahug.png" alt="hug" width="20" height="20"/></p>
</div>
<h1>Conclusion</h1>
<p>RSS is just a way to subscribe to that websites you like. An RSS reader checks those feeds for you and gathers every new post in one place, so you skip the manual checking every day. Some popular RSS readers to start with are Feedly and Inoreader. You can start small with 5 to 10 subscribed sources (feeds), and see if it works well for you.</p>
<p>Some advantages of using RSS feeds are: no algorithmic feeds, saves you lots of time, helps you stay more anonymous with still getting all of the new content right in your dashboard, and enables you to read posts while being offline. And some trade-offs of using RSS feeds are: information overload if you subscribe to way too many active sites, some sites choosing to show a truncated version of the full article, lack of adoption of RSS feeds in most modern sites, and publishers getting very limited metrics of their audience.</p>
<p>Well, this was a short overview of RSS feeds, see you in the next post!</p>
<h1>Sources</h1>
<ul>
<li>&quot;How Do RSS Feeds Work?&quot; <em>RSS.com</em>, 6 May. 2026, <a href="https://rss.com/blog/how-do-rss-feeds-work/">rss.com/blog/how-do-rss-feeds-work/</a></li>
<li>Nguyen, Kevin. “Feedly vs Inoreader for developers in 2026.” <em>daily.dev</em>, 1 Nov. 2026, <a href="https://daily.dev/blog/feedly-vs-inoreader-for-developers/">daily.dev/blog/feedly-vs-inoreader-for-developers/</a>.</li>
<li>&quot;RSS.&quot; <em>Wikipedia</em>, <a href="https://en.wikipedia.org/wiki/RSS">en.wikipedia.org/wiki/RSS</a></li>
</ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node.js Clustering]]></title>
            <link>https://caleb.is-a.dev/blog/nodejs-clustering</link>
            <guid
        isPermaLink="false"
      >https://caleb.is-a.dev/blog/nodejs-clustering</guid>
            <pubDate>Sun, 04 Oct 2026 00:00:00 GMT</pubDate>
            <description
      ><![CDATA[Learn how to use every CPU core in your Node.js server with the cluster Node.js module]]></description>
            <content:encoded
      ><![CDATA[<p><img src="https://images.unsplash.com/photo-1627398242454-45a1465c2479?q=80&amp;w=1374&amp;auto=format&amp;fit=crop&amp;ixlib=rb-4.1.0&amp;ixid=NHwxMjA3fDA%3D" alt="Node.js Clustering"/></p><p>Imagine the <code>/api/login</code> endpoint you made, of a Node.js backend, got hit with lots of login requests. Each one looks up the user by email, verifies the password against a legacy <code>bcrypt</code> hash, re-hashes it with <code>Argon2id</code>, verifies an MFA code, then issues a JWT. If you use a pure JavaScript implementation like <code>bcryptjs</code>, all of that hashing runs on the main (master) thread. The server has, let&#x27;s say, 4 CPU cores, but Node.js runs your JavaScript code on a single thread, so it can only use one core for all of these requests. When it&#x27;s under heavy load, <mark class="secondary">the server either drops or delays requests</mark>, and clustering fixes this by running one worker per core.</p>
<p>According to the <a href="https://nodejs.org/api/cluster.html">Node.js docs</a>, clusters of Node.js processes can be used to run multiple instances of Node.js that distribute workloads among their application threads. It basically allows you to create many workers that share the same port, using all (or some) of the available CPU cores. The <code>cluster</code> module has been part of Node.js since v0.8, and is stable in current versions.</p>
<p><a href="https://nodejs.org/docs/latest-v24.x/api/cluster.html">Cluster</a></p>
<h1>Why Use Clustering</h1>
<p>Node.js runs your JavaScript code on a single thread, so one process can only use one CPU core. On an 4 cored server, that leaves 3 cores sitting on the couch eating chips while one is fighting for its life <img src="https://cdn3.emoji.gg/emojis/175472-pepelaugh.gif" alt="giggle" width="20" height="20"/>. <mark>Clustering can be used to ensure all CPU cores are used to distribute work across all workers.</mark></p>
<h1>When To Use Clustering</h1>
<p>When you have alot of incoming HTTP requests that require heavy computation. It helps with distributing the load to independant workers, making the response time faster with less errors. Note that it won&#x27;t help that much if your app mostly waits on databases or APIs, since Node.js already handles those things well on a single thread.</p>
<p>Let&#x27;s test that out, shall we?</p>
<h1>Tests</h1>
<div class="markdown-alert markdown-alert-info">
<div class="markdown-alert-title">Info</div>
<p>The test below uses <a href="https://hono.dev">the hono web framework</a>. You can go with <a href="http://expressjs.com/">express</a> or whatever you&#x27;re comfortable with.</p>
</div>
<h2>Without Clustering</h2>
<p><code>index.ts</code>:</p>
<pre><code class="language-ts">import { serve } from &quot;@hono/node-server&quot;;
import { Hono } from &quot;hono&quot;;

const app = new Hono();

app.get(&quot;/&quot;, (c) =&gt; {
  let num = 0;

  // simulate a heavy computation
  for (let i = 0; i &lt; 50_000_000; i++) {
    num++;
  }

  return c.json({ message: `Iterated ${num} times.` });
});

serve(
  {
    fetch: app.fetch,
    port: 3000,
  },
  () =&gt; console.log(`Server is running on http://localhost:3000`),
);
</code></pre>
<p>Then run <code>npx tsx ./index.ts</code>. On a new terminal window, run <code>npx loadtest -n 1000 -c 500 -k http://localhost:3000</code>.</p>
<pre><code>Server is running on http://localhost:3000
</code></pre>
<p><strong>Loadtest Result:</strong></p>
<pre><code>Target URL:          http://localhost:3000
Max requests:        1000
Concurrent clients:  1000
Running on cores:    2
Agent:               keepalive

Completed requests:  1000
Total errors:        381
Total time:          30.354 s
Mean latency:        20986.8 ms
Effective rps:       33

Percentage of requests served within a certain time
  50%      23800 ms
  90%      30194 ms
  95%      30208 ms
  99%      30219 ms
 100%      30220 ms (longest request)

   -1:   381 errors
</code></pre>
<div class="markdown-alert markdown-alert-tip">
<div class="markdown-alert-title">Tip</div>
<p><code>loadtest</code> ran on 2 cores here and each core gets the full <code>-c</code> value, so <code>-c 500</code> means 1000 concurrent clients in total.</p>
</div>
<h2>With Clustering</h2>
<p><code>index.ts</code> stays the same, <code>cluster.ts</code>:</p>
<pre><code class="language-ts">import cluster from &quot;cluster&quot;;
import { cpus } from &quot;os&quot;;
import { join } from &quot;path&quot;;
import { cwd } from &quot;process&quot;;

// how many cpu cores we have
const cores = cpus().length;

cluster.setupPrimary({
  exec: join(cwd(), &quot;index.ts&quot;), // our index.ts
});

for (let i = 0; i &lt; cores; i++) {
  // forking = new worker
  cluster.fork();
}

// if a worker crashes for some reason..... just spawn another one
cluster.on(&quot;exit&quot;, () =&gt; cluster.fork());
</code></pre>
<p>Then this time, run <code>npx tsx ./cluster.ts</code>, and do the same loadtest in a new terminal.</p>
<pre><code>Server is running on http://localhost:3000
Server is running on http://localhost:3000
Server is running on http://localhost:3000
Server is running on http://localhost:3000
</code></pre>
<p><strong>Loadtest Result:</strong></p>
<pre><code>Target URL:          http://localhost:3000
Max requests:        1000
Concurrent clients:  1000
Running on cores:    2
Agent:               keepalive

Completed requests:  1000
Total errors:        0
Total time:          26.792 s
Mean latency:        13402.4 ms
Effective rps:       37

Percentage of requests served within a certain time
  50%      13356 ms
  90%      24098 ms
  95%      25419 ms
  99%      26391 ms
 100%      26603 ms (longest request)
</code></pre>
<h2>Summary</h2>
<table><thead><tr><th>Metric</th><th>Without Clustering</th><th>With Clustering</th><th>Benefit of Clustering</th></tr></thead><tbody><tr><td>Total Timeouts</td><td>381 (38.1%)</td><td>0 (0%)</td><td>-100% timeouts</td></tr><tr><td>Successful RPS</td><td>20 req/s</td><td>37 req/s</td><td>~1.8x higher throughput</td></tr><tr><td>Duration</td><td>30.35 s</td><td>26.79 s</td><td>11.7% faster completion</td></tr><tr><td>Mean Latency</td><td>20,986.8 ms (~21.0 s)</td><td>13,402.4 ms (~13.4 s)</td><td>~36% reduction in avg wait</td></tr><tr><td>50th Percentile (p50)</td><td>23,800 ms</td><td>13,356 ms</td><td>43.9% faster median response</td></tr><tr><td>90th Percentile (p90)</td><td>30,194 ms</td><td>24,098 ms</td><td>20.2% faster for tail requests</td></tr><tr><td>95th Percentile (p95)</td><td>30,208 ms</td><td>25,419 ms</td><td>15.9% faster</td></tr><tr><td>99th Percentile (p99)</td><td>30,219 ms</td><td>26,391 ms</td><td>12.7% faster</td></tr><tr><td>Max Latency (p100)</td><td>30,220 ms</td><td>26,603 ms</td><td>~3.6 seconds lower peak latency</td></tr></tbody></table>
<h1>Better Clustering With PM2</h1>
<p>Instead of manually running clustering, production can better handle using the <a href="http://npmjs.com/package/pm2">pm2 npm package</a>. &quot;PM2 is a production process manager for Node.js/Bun applications with a built-in load balancer. It allows you to keep applications alive forever, to reload them without downtime and to facilitate common system admin tasks&quot; (PM2). It&#x27;s as easy as:</p>
<pre><code class="language-sh">pm2 start index.js -i max
</code></pre>
<div class="markdown-alert markdown-alert-note">
<div class="markdown-alert-title">Note</div>
<p>Without <code>-i &lt;processes&gt;</code>, PM2 runs a single process and doesn&#x27;t cluster anything.</p>
</div>
<h1>Conclusion</h1>
<p>Node.js runs your JavaScript on a single thread, so on a multi-core server most of your CPU sits idle while one core handles everything. Clustering fixes that by summoning workers per core, all sharing the same port, with the master process handling the workers and spawning another one on crash.</p>
<p>In our tests, the same machine and the same app code went from timing out on 381 of 1000 requests to timing out on none, with about 36% lower mean latency, just by adding a small <code>cluster.ts</code> file.</p>
<div class="markdown-alert markdown-alert-info">
<div class="markdown-alert-title">Info</div>
<p>Since workers don&#x27;t share memory, anything kept in memory (sessions, caches, rate limits) needs to move outside to something shared like Redis or a db first.</p>
</div>
<p>For production, you can just skip the <code>cluster.ts</code> file and use PM2 (<code>pm2 start index.js -i max</code>). You get clustering, crash recovery, and some other additional features out of the box.</p>
<h1>Sources</h1>
<ul>
<li>&quot;Cluster.&quot; <em>Node.js</em>, <a href="https://nodejs.org/api/cluster.html">nodejs.org/api/cluster.html</a>.</li>
<li>Loban, Volodymyr. &quot;Clustering in Node.js.&quot; <em>Medium</em>, 22 Sep. 2024, <a href="https://medium.com/@vloban/clustering-in-node-js-4e0bf17b7f0b">medium.com/@vloban/clustering-in-node-js-4e0bf17b7f0b</a>.</li>
<li>Nahid, Shams. &quot;Clustering in Node.js: Look for the Limitations.&quot; <em>Medium</em>, 27 Sep. 2022, <a href="https://shams-nahid.medium.com/clustering-in-node-js-look-for-the-limitations-e6ff7f846a3c">shams-nahid.medium.com/clustering-in-node-js-look-for-the-limitations-e6ff7f846a3c</a>.</li>
<li>&quot;PM2.&quot; <em>npm</em>, <a href="https://www.npmjs.com/package/pm2">www.npmjs.com/package/pm2</a>.</li>
<li>&quot;Scaling Your Node.js App Using the &#x27;Cluster&#x27; Module.&quot; <em>YouTube</em>, uploaded by Software Developer Diaries, 26 Feb. 2023, <a href="https://youtu.be/6lHvks6R6cI">youtu.be/6lHvks6R6cI</a>.</li>
</ul>]]></content:encoded>
        </item>
        <item>
            <title
      ><![CDATA[GitHub Repositories You’ll Wish You Found Sooner]]></title>
            <link>https://caleb.is-a.dev/blog/amazing-github-repos</link>
            <guid
        isPermaLink="false"
      >https://caleb.is-a.dev/blog/amazing-github-repos</guid>
            <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
            <description
      ><![CDATA[15 GitHub repos that have more value than most other paid courses combined]]></description>
            <content:encoded
      ><![CDATA[<p><img src="https://pbs.twimg.com/media/HKTgsFaXYAE-BVH?format=jpg&amp;name=large" alt="GitHub Repositories You’ll Wish You Found Sooner"/></p><p><a href="https://www.youtube.com/watch?v=cgOPg5cCr2g">Watch a video on YouTube</a></p>
<p>GitHub has lots of other things to offer than just storing code. Among the gazillions of public repos available on GitHub, these ones have more value than you might expect. This is a collection of great resources, books, roadmap, research papers, blogs, free and open-source software, recommended websites for programmers, ML resources, and much more!</p>
<h1>1. <a href="https://github.com/sindresorhus/awesome">Awesome Lists</a> by <a href="https://github.com/sindresorhus">Sindre Sorhus</a></h1>
<p><a href="https://github.com/sindresorhus/awesome">sindresorhus/awesome</a> is basically a huge collection of useful stuff for developers. It contains links to hundreds of carefully picked resources covering programming languages, tools, learning materials, software, and much much more. Think of it as a giant index of interesting things on the internet, all organized in one GitHub repository.</p>
<p><a href="https://github.com/sindresorhus/awesome">Awesome</a></p>
<h1>2. <a href="https://github.com/thealgorithms">The Algorithms</a> by <a href="https://github.com/thealgorithms">The Algorithms</a></h1>
<p><a href="https://github.com/thealgorithms">The Algorithms</a> is a collection of open-source repositories that implement algorithms and data structures in different programming languages. It’s a great place to browse through real implementations, understand how algorithms work, and see how the same ideas are written across different languages.</p>
<p><a href="https://github.com/thealgorithms">The Algorithms</a></p>
<h1>3. <a href="https://github.com/codecrafters-io/build-your-own-x">Build Your Own X</a> by <a href="https://github.com/codecrafters-io">CodeCrafters</a></h1>
<p><a href="https://github.com/codecrafters-io/build-your-own-x">codecrafters-io/build-your-own-x</a> is a collection of guides that show you how to build things from scratch. It covers projects like databases, operating systems, programming languages, web servers, and other software, making it a great place to learn by actually building your favorite tools and technologies yourself.</p>
<p><a href="https://github.com/codecrafters-io/build-your-own-x">Build Your Own X</a></p>
<h1>4. <a href="https://github.com/ripienaar/free-for-dev">Free For Dev</a> by <a href="https://github.com/ripienaar">@ripienaar</a></h1>
<p><a href="https://github.com/ripienaar/free-for-dev">ripienaar/free-for-dev</a> is a huge list of free services and resources for developers. It covers everything from hosting and databases to APIs, monitoring, testing, and other tools, making it a handy place to look when you need something without spending money.</p>
<p><a href="https://github.com/ripienaar/free-for-dev">Free For Dev</a></p>
<h1>5. <a href="https://github.com/EbookFoundation/free-programming-books">Free Programming Books</a> by <a href="https://github.com/EbookFoundation">Free Ebook Foundation</a></h1>
<p><a href="https://github.com/EbookFoundation/free-programming-books">EbookFoundation/free-programming-books</a> is a massive collection of free programming books and learning resources. It covers a wide range of programming languages and topics, making it an easy place to find something to learn without having to pay for a course or book.</p>
<p><a href="https://github.com/EbookFoundation/free-programming-books">Free Programming Books</a></p>
<h1>6. <a href="https://github.com/nilbuild/developer-roadmap">roadmap.sh</a> by <a href="https://github.com/nilbuild">Kamran Ahmed</a></h1>
<p><a href="https://github.com/nilbuild/developer-roadmap">nilbuild/developer-roadmap</a> is a collection of roadmaps, guides, and educational content that help you figure out what to learn and in what order, with interactive visual roadmaps. It covers everything from frontend and backend development to DevOps, AI, databases, and more, making it useful when you’re not sure what to learn next.</p>
<p><a href="https://github.com/nilbuild/developer-roadmap">roadmap.sh</a></p>
<h1>7. <a href="https://github.com/ossu/computer-science">Computer Science</a> by <a href="https://github.com/ossu">Open Source Society University</a></h1>
<p><a href="https://github.com/ossu/computer-science">ossu/computer-science</a> is a complete, self-guided computer science curriculum made from free online courses and resources. It covers topics like programming, algorithms, computer systems, and theory, giving you a structured way to learn computer science on your own.</p>
<p><a href="https://github.com/ossu/computer-science">Computer Science</a></p>
<h1>8. <a href="https://github.com/kilimchoi/engineering-blogs">Engineering Blogs</a> by <a href="https://github.com/kilimchoi">Kilim Choi</a></h1>
<p><a href="https://github.com/kilimchoi/engineering-blogs">kilimchoi/engineering-blogs</a> is a collection of engineering blogs from companies and developers around the world. It’s a great place to discover how real teams build, scale, and solve problems, while learning from their experiences along the way.</p>
<p><a href="https://github.com/kilimchoi/engineering-blogs">Engineering Blogs</a></p>
<h1>9. <a href="https://github.com/donnemartin/system-design-primer">The System Design Primer</a> by <a href="https://github.com/donnemartin">Donne Martin</a></h1>
<p><a href="https://github.com/donnemartin/system-design-primer">donnemartin/system-design-primer</a> is a collection of resources for learning system design and understanding how large-scale systems work. It covers topics like scalability, databases, caching, networking, and architecture, making it a useful resource for anyone wanting to get better at designing real-world systems.</p>
<p><a href="https://github.com/donnemartin/system-design-primer">The System Design Primer</a></p>
<h1>10. <a href="https://github.com/public-apis/public-apis">Public APIs</a> by <a href="https://github.com/public-apis">@public-apis</a></h1>
<p><a href="https://github.com/public-apis/public-apis">public-apis/public-apis</a> is a huge collection of public APIs that you can use in your own projects. It covers all kinds of things, from games and weather to finance, animals, and more, making it a great place to find an API when you need one.</p>
<p><a href="https://github.com/public-apis/public-apis">Public APIs</a></p>
<h1>11. <a href="https://github.com/btw-so/open-source-alternatives">Open Source Alternatives</a> by <a href="https://github.com/btw-so">@btw-so</a></h1>
<p><a href="https://github.com/btw-so/open-source-alternatives">btw-so/open-source-alternatives</a> is a collection of open-source alternatives to popular software and services. It helps you discover free and open-source tools that can replace many of the apps and services you already use.</p>
<p><a href="https://github.com/btw-so/open-source-alternatives">Open Source Alternatives</a></p>
<h1>12. <a href="https://github.com/papers-we-love/papers-we-love">Papers We Love</a> by <a href="https://github.com/papers-we-love">@papers-we-love</a></h1>
<p><a href="https://github.com/papers-we-love/papers-we-love">papers-we-love/papers-we-love</a> is a collection of interesting computer science research papers, organized by topic. It’s a great place to discover papers about things like programming, algorithms, machine learning, security, and many other areas of computing.</p>
<p><a href="https://github.com/papers-we-love/papers-we-love">Papers We Love</a></p>
<h1>13. <a href="https://github.com/sdmg15/Best-websites-a-programmer-should-visit">Best Websites A Programmer Should Visit</a> by <a href="https://github.com/sdmg15">Sonkeng</a></h1>
<div class="markdown-alert markdown-alert-info">
<div class="markdown-alert-title">Info</div>
<p>This repository was archived by the owner on Nov 1, 2025. It is now read-only.</p>
</div>
<p><a href="https://github.com/sdmg15/Best-websites-a-programmer-should-visit">sdmg15/Best-websites-a-programmer-should-visit</a> is a collection of useful websites for programmers. It covers everything from learning and coding to finding tools, resources, jobs, and communities, making it a handy list to explore when you’re looking for something useful.</p>
<p><a href="https://github.com/sdmg15/Best-websites-a-programmer-should-visit">Best Websites A Programmer Should Visit</a></p>
<h1>14. <a href="https://github.com/rasbt/LLMs-from-scratch">LLMs From Scratch</a> by <a href="https://github.com/rasbt">Sebastian Raschka</a></h1>
<p><a href="https://github.com/rasbt/LLMs-from-scratch">rasbt/LLMs-from-scratch</a> is a hands-on guide to building large language models from scratch. It walks through the main ideas behind LLMs step by step, helping you understand what’s happening under the hood instead of just using them as a black box.</p>
<p><a href="https://github.com/rasbt/LLMs-from-scratch">LLMs From Scratch</a></p>
<h1>15. <a href="https://github.com/eriklindernoren/ML-From-Scratch">ML From Scratch</a> by <a href="https://github.com/eriklindernoren">Erik Linder-Norén</a></h1>
<p><a href="https://github.com/eriklindernoren/ML-From-Scratch">eriklindernoren/ML-From-Scratch</a> is a collection of machine learning algorithms implemented from scratch using Python. It lets you see how common ML techniques actually work under the hood, making it a great resource for learning the fundamentals without relying on ready-made libraries.</p>
<p><a href="https://github.com/eriklindernoren/ML-From-Scratch">ML From Scratch</a></p>
<h1>16. <a href="https://github.com/The-DevOps-Daily/devops-daily">DevOps Daily</a> by <a href="https://github.com/The-DevOps-Daily">The DevOps Daily</a></h1>
<p><a href="https://github.com/The-DevOps-Daily/devops-daily">The-DevOps-Daily/devops-daily</a> is an open-source platform for learning DevOps through articles, tutorials, guides, and hands-on exercises. It also features quizzes, interview questions, games, flashcards, and resources covering topics like Docker, Kubernetes, Linux, Terraform, and many more, making it a great resource for anyone looking to improve their DevOps skills.</p>
<p><a href="https://github.com/The-DevOps-Daily/devops-daily">DevOps Daily</a></p>
<h1>The End...</h1>
<p>Just a tiny fraction of what you can find on GitHub. There are dozens of repos filled with useful resources, interesting ideas, and things you probably didn’t even know existed. Hopefully, you found something worth bookmarking, exploring, or sharing, and maybe the next time you’re looking for something, you’ll check GitHub before opening another site <img src="https://cdn3.emoji.gg/emojis/175472-pepelaugh.gif" alt="giggle" width="20" height="20"/></p>
<div class="markdown-alert markdown-alert-tip">
<div class="markdown-alert-title">Tip</div>
<p>If you have a favorite resource that is missing from this list, feel free to add it by <a href="https://caleb.is-a.dev/r/portfolio/edit/main/content/blog/amazing-github-repos.md">editing the blog file</a> and submitting a pull request to the <code>main</code> branch.</p>
</div>
<h1>Sources</h1>
<ul>
<li>“16 Cool GitHub Repos You WILL Use (No Pressure).” <em>YouTube</em>, uploaded by The Coding Sloth, 23 Jun. 2025, <a href="https://youtu.be/cgOPg5cCr2g">youtu.be/cgOPg5cCr2g</a>.</li>
<li>Torres, Daniela. “The Best GitHub Repos for Learning to Code in 2026.” <em>daily.dev</em>, 26 Aug. 2026, <a href="https://daily.dev/blog/best-github-repos-for-learning-to-code/">daily.dev/blog/best-github-repos-for-learning-to-code</a>.</li>
</ul>]]></content:encoded>
        </item>
    </channel>
</rss>
