<?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>Algorithms on Abhishek Shukla</title><link>https://abhishekshukla.dev/tags/algorithms/</link><description>Recent content in Algorithms on Abhishek Shukla</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 05 Jul 2026 11:00:00 +0530</lastBuildDate><atom:link href="https://abhishekshukla.dev/tags/algorithms/index.xml" rel="self" type="application/rss+xml"/><item><title>Sorting Algorithms in Production: When, Why, and Time Complexity</title><link>https://abhishekshukla.dev/about/swift-tim-sorting/</link><pubDate>Sun, 05 Jul 2026 11:00:00 +0530</pubDate><guid>https://abhishekshukla.dev/about/swift-tim-sorting/</guid><description>&lt;p&gt;With over a decade in software engineering, you quickly realize that sorting isn&amp;rsquo;t just a hurdle for technical interviews—it is a fundamental system design decision. Choosing the wrong sorting algorithm can lead to memory spikes, UI frame drops, and battery drain, especially on mobile devices.&lt;/p&gt;
&lt;p&gt;Most modern languages (including Swift) abstract sorting behind a simple &lt;code&gt;.sort()&lt;/code&gt; method. However, understanding the underlying mechanisms is critical when building custom data pipelines, handling massive data sets, or optimizing for specific input distributions.&lt;/p&gt;</description></item></channel></rss>