Skip to main content

Sorting Algorithms – Quick Reference for Interviews

Sorting is a fundamental operation in computer science and Understanding the basic sorting algorithms is essential for both interviews and real-world programming tasks. I am sharing the notes that I have taken in my learning curve.

1. Selection Sort

Selection Sort repeatedly finds the minimum element from the unsorted part and puts it at the beginning.

Steps:

  1. Loop through the array.
  2. For each index, find the smallest element in the rest of the array.
  3. Swap it with the current index.

Time Complexity: O(n²)

Example:

[29, 10, 14, 37, 13]

→ [10, 29, 14, 37, 13]

→ [10, 13, 14, 37, 29]

→ [10, 13, 14, 37, 29]

→ [10, 13, 14, 29, 37]


2. Insertion Sort

Insertion Sort builds the sorted array one element at a time by inserting each element into its correct position.

Steps:

  1. Start from index 1.
  2. Compare current element with the left-side elements.
  3. Shift elements to the right and insert at the correct position.

Time Complexity: O(n²)

Example:

[8, 4, 1, 3]

→ [4, 8, 1, 3]

→ [1, 4, 8, 3]

→ [1, 3, 4, 8]


3. Bubble Sort

Bubble Sort repeatedly steps through the list, compares adjacent elements, and swaps them if they are in the wrong order.

Steps:

  1. Compare each pair of adjacent items.
  2. Swap them if needed.
  3. Repeat until no swaps are needed.

Time Complexity: O(n²)

Example:

[5, 3, 8, 4]

→ [3, 5, 4, 8]

→ [3, 4, 5, 8]


4. Quick Sort

Quick Sort is a divide-and-conquer algorithm. It selects a pivot, partitions the array, and recursively sorts the subarrays.

Steps:

  1. Choose a pivot.
  2. Partition the array into left (less than pivot) and right (greater).
  3. Recursively apply the same logic.

Time Complexity: 

  Average: O(n log n)

  Worst: O(n²) (when poorly partitioned)

Example:

[9, 3, 7, 1]

Pivot = 3 → [1] + [3] + [9, 7]

→ [1, 3] + quickSort([9, 7]) → [1, 3, 7, 9]


5. Merge Sort

Merge Sort is a stable divide-and-conquer algorithm that divides the array in half, sorts each half, and merges them.

Steps:

  1. Divide the array into halves.
  2. Sort each half recursively.
  3. Merge the sorted halves.

Time Complexity: O(n log n)

Example:

[6, 2, 4, 1]

→ [6, 2], [4, 1]

→ [2, 6], [1, 4]

→ merge → [1, 2, 4, 6] 

Popular posts from this blog

Animating label text update - choosing a better way

Recently I published a countdown app .  At one point of development - I have to show a timer on a UILabel which ticks on each seconds. As usual I started  setting text to a label object - self .timerLabel.text = someString Easy piece of cake right !?   But wait ... it won't take much user attention when timer ticks on every seconds. So I decided to make use of a simple animation while label gets text update. I found there are dozens of ways to animate a label. In this short article, I listed 3 best way you can animate text on a label. ( Spoiler Alert 👀- I decided to go with 3rd option)  1. Fade In - Fade out animation : CATransition class has got transition type `fade`. With timing function of CATransition - I was able to see the below result. let animation: CATransition = CATransition () animation.timingFunction = CAMediaTimingFunction (name: CAMediaTimingFunctionName .easeInEaseOut) animation.type = CATransitionType .fade animation.subtype = C...

Implementing autocompletion OTP field in iOS

Long waiting is over. !!  iOS 12 brings Autofill for OTP text field which is close to Android provided a decade back. Previously in iOS we used to toggle between OTP text screen and message inbox.  Which was hard to remember and time consuming resulting a bad user experience. Personally, I have been asked from the client/customer couple of times to implement autocompletion for OTP field and took me a lot of time to convey that it is not possible in iOS. Why Autofill was not possible previously?  We all know that Apple gives at most care for user privacy. When we see iOS architecture, each individual app is like a separate island. There is no inter-app bridge between apps (exception for Keychain and URLSchemes APIs which gives very limited scope). Thus we cannot read message content from inbox. Where to start Autofilling? First of all, the target SMS need to have the OTP Code with prefix string "Code" or "Passcode"on its message content. Beware of OTP c...

Prevent Navigationbar or Tabbar overlapping Subview - solved for Card view

Recently, I started with a Card view added as a subview of UIView in a view-controller. When a view controller created along subviews, it tends to use entire screen bounds and also slips behind Tab bar or Navigation bar. In my current situation, it's second case. Casually new iOS developers will write a patch by additional value for coordinate y and subtracting bar height from its size. A lot of them posted in SO threads too : How to prevent UINavigationBar from covering top of view? View got hidden below UINavigationBar iOS 7 Navigation Bar covers some part of view at Top So, how I got solved ? self.edgesForExtendedLayout = [] This  will avoid all subviews in a view controller get behind any bars. Read full apple  documentation on here. Full Source code below :  //Simple view controller where its view layed-out as a card. class WidgetCardViewController : UIViewController { var containerView = UIView () //MARK:- View Controller Life Cyc...

UICollectionViewCell shows with wrong size on First time - Solved

We commonly use Collection view where its cell size calculated run time. The flow layout delegate is responsible to return individual cell sizes. BUT in most of the cases, delegate method `collectionView: layout sizeForItem:` expects cell size too early. Before generating actual cell size. extension YourViewController : UICollectionViewDelegateFlowLayout { func collectionView ( _ collectionView: UICollectionView, layout collectionViewLayout: UICollectionViewLayout, sizeForItemAt indexPath: IndexPath) -> CGSize { return CGSize (width: externalWidth, height: externalHeight) } } For instance, if a cell size depends on external view and its frame is not yet ready - results with wrong (or outdated) cell size. Typically happens for the first time view controller laid out all views. You can find similar queries in StackOverflow community : Collection view sizeForItemNotWorking UICollectionViewCell content wrong size on first load How to refresh UICollec...

Cached Async Image in SwiftUI

 SwiftUI’s AsyncImage is handy, but every time your view appears, it refetches the image—leading to flicker, delays, and unnecessary network use. What if you could fetch once, then reuse instantly? That's exactly what the Cached Async Image  delivers: a memory-powered caching layer that keeps SwiftUI image loading smooth, snappy, and resilient. First a simple in-memory cache without disk persistence. This will be thread-safe and auto-purges under memory pressure. A Singleton wrapping NSCache for URL → UIImage caching as follows : final class ImageCache {   static let shared = ImageCache()   private init() {}   private let cache = NSCache<NSURL, UIImage>()   func image(for url: URL) -> UIImage? {     cache.object(forKey: url as NSURL)   }   func insertImage(_ image: UIImage?, for url: URL) {     guard let image else { return }     cache.setObject(image, forKey: url as NSURL)   }   func clearAll() { ...