<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Articles on JinerX blog</title><link>https://jinerx.github.io/posts/</link><description>Recent content in Articles on JinerX blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 Jędrzej Sajnóg</copyright><lastBuildDate>Wed, 04 Mar 2026 17:54:13 +0100</lastBuildDate><atom:link href="https://jinerx.github.io/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Algorithm Complexity Basics</title><link>https://jinerx.github.io/posts/algorithm-complexity-basics/</link><pubDate>Wed, 04 Mar 2026 17:54:13 +0100</pubDate><guid>https://jinerx.github.io/posts/algorithm-complexity-basics/</guid><description>&lt;p&gt;Here we&amp;rsquo;re going to consider the basics of complexity analysis - a critical part of algorithm analysis.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Motivation
 &lt;div id="motivation" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#motivation" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;When running algorithms we can see that some programs end almost immediately and some take a long time. Complexity analysis aims to formalize this notion and give us tools to predict how long a program is going to run. It does so by looking at how much does the time for a program to terminate increase based on the increase in the size of the input. We do it by creating functions (mathematical) based on the algorithms which take in as input the size and return the &amp;ldquo;time&amp;rdquo;.&lt;/p&gt;</description></item></channel></rss>