jwasham/coding-interview-universityPublic

I originally created this as a short to-do list of study topics for becoming a software engineer, but it grew to the large list you see today. After going through this study plan, I got hired as a Software Development Engineer at Amazon! You probably won't have to study as much as I did. Anyway, everything you need is here.

I studied about 8-12 hours a day, for several months. This is my story: Why I studied full-time for 8 months for a Google interview

Please Note: You won't need to study as much as I did. I wasted a lot of time on things I didn't need to know. More info about that is below. I'll help you get there without wasting your precious time.

The items listed here will prepare you well for a technical interview at just about any software company, including the giants: Amazon, Facebook, Google, and Microsoft.

Best of luck to you!

This is my multi-month study plan for becoming a software engineer for a large company.

Required:

• A little experience with coding (variables, loops, methods/functions, etc)
• Patience
• Time

Note this is a study plan for software engineering, not frontend engineering or full-stack development. There are really super roadmaps and coursework for those career paths elsewhere (see https://roadmap.sh/ for more info).

There is a lot to learn in a university Computer Science program, but only knowing about 75% is good enough for an interview, so that's what I cover here. For a complete CS self-taught program, the resources for my study plan have been included in Kamran Ahmed's Computer Science Roadmap: https://roadmap.sh/computer-science

• What is it?
• Why use it?
• How to use it
• Don't feel you aren't smart enough
• A Note About Video Resources
• Choose a Programming Language
• Books for Data Structures and Algorithms
• Interview Prep Books
• Don't Make My Mistakes
• What you Won't See Covered
• The Daily Plan
• Coding Question Practice
• Coding Problems

• Algorithmic complexity / Big-O / Asymptotic analysis
• Data Structures
  • Arrays
  • Linked Lists
  • Stack
  • Queue
  • Hash table
• More Knowledge
  • Binary search
  • Bitwise operations
• Trees
  • Trees - Intro
  • Binary search trees: BSTs
  • Heap / Priority Queue / Binary Heap
  • balanced search trees (general concept, not details)
  • traversals: preorder, inorder, postorder, BFS, DFS
• Sorting
  • selection
  • insertion
  • heapsort
  • quicksort
  • mergesort
• Graphs
  • directed
  • undirected
  • adjacency matrix
  • adjacency list
  • traversals: BFS, DFS
• Even More Knowledge
  • Recursion
  • Dynamic Programming
  • Design Patterns
  • Combinatorics (n choose k) & Probability
  • NP, NP-Complete and Approximation Algorithms
  • How computers process a program
  • Caches
  • Processes and Threads
  • Testing
  • String searching & manipulations
  • Tries
  • Floating Point Numbers
  • Unicode
  • Endianness
  • Networking
• Final Review

• Update Your Resume
• Find a Job
• Interview Process & General Interview Prep
• Be thinking of for when the interview comes
• Have questions for the interviewer
• Once You've Got The Job

---------------- Everything below this point is optional ----------------

• Additional Books
• System Design, Scalability, Data Handling (if you have 4+ years experience)
• Additional Learning
  • Compilers
  • Emacs and vi(m)
  • Unix command line tools
  • Information theory
  • Parity & Hamming Code
  • Entropy
  • Cryptography
  • Compression
  • Computer Security
  • Garbage collection
  • Parallel Programming
  • Messaging, Serialization, and Queueing Systems
  • A*
  • Fast Fourier Transform
  • Bloom Filter
  • HyperLogLog
  • Locality-Sensitive Hashing
  • van Emde Boas Trees
  • Augmented Data Structures
  • Balanced search trees
    • AVL trees
    • Splay trees
    • Red/black trees
    • 2-3 search trees
    • 2-3-4 Trees (aka 2-4 trees)
    • N-ary (K-ary, M-ary) trees
    • B-Trees
  • k-D Trees
  • Skip lists
  • Network Flows
  • Disjoint Sets & Union Find
  • Math for Fast Processing
  • Treap
  • Linear Programming
  • Geometry, Convex hull
  • Discrete math
• Additional Detail on Some Subjects
• Video Series
• Computer Science Courses
• Papers

If you want to work as a software engineer for a large company, these are the things you have to know.

If you missed out on getting a degree in computer science, like I did, this will catch you up and save four years of your life.

When I started this project, I didn't know a stack from a heap, didn't know Big-O anything, or anything about trees, or how to traverse a graph. If I had to code a sorting algorithm, I can tell ya it would have been terrible. Every data structure I had ever used was built into the language, and I didn't know how they worked under the hood at all. I never had to manage memory unless a process I was running would give an "out of memory" error, and then I'd have to find a workaround. I used a few multidimensional arrays in my life and thousands of associative arrays, but I never created data structures from scratch.

It's a long plan. It may take you months. If you are familiar with a lot of this already it will take you a lot less time.

⬆ back to top

Everything below is an outline, and you should tackle the items in order from top to bottom.

I'm using GitHub's special markdown flavor, including tasks lists to track progress.

• More about GitHub-flavored markdown

On this page, click the Code button near the top, then click "Download ZIP". Unzip the file and you can work with the text files.

If you're open in a code editor that understands markdown, you'll see everything formatted nicely.

Create a new branch so you can check items like this, just put an x in the brackets: [x]

1. Fork the GitHub repo: https://github.com/jwasham/coding-interview-university by clicking on the Fork button.

   

2. Clone to your local repo:

   git clone https://github.com/<YOUR_GITHUB_USERNAME>/coding-interview-university.git
   cd coding-interview-university
   git remote add upstream https://github.com/jwasham/coding-interview-university.git
   git remote set-url --push upstream DISABLE  # so that you don't push your personal progress back to the original repo

3. Mark all boxes with X after you completed your changes:

   git commit -am "Marked personal progress"
   git pull upstream main  # keep your fork up-to-date with changes from the original repo
   
   git push # just pushes to your fork

⬆ back to top

• Successful software engineers are smart, but many have an insecurity that they aren't smart enough.
• The following videos may help you overcome this insecurity:
  • The myth of the Genius Programmer
  • It's Dangerous to Go Alone: Battling the Invisible Monsters in Tech

⬆ back to top

Some videos are available only by enrolling in a Coursera or EdX class. These are called MOOCs. Sometimes the classes are not in session so you have to wait a couple of months, so you have no access.

It would be great to replace the online course resources with free and always-available public sources, such as YouTube videos (preferably university lectures), so that you people can study these anytime, not just when a specific online course is in session.

⬆ back to top

You'll need to choose a programming language for the coding interviews you do, but you'll also need to find a language that you can use to study computer science concepts.

Preferably the language would be the same, so that you only need to be proficient in one.

When I did the study plan, I used 2 languages for most of it: C and Python

• C: Very low level. Allows you to deal with pointers and memory allocation/deallocation, so you feel the data structures and algorithms in your bones. In higher-level languages like Python or Java, these are hidden from you. In day-to-day work, that's terrific, but when you're learning how these low-level data structures are built, it's great to feel close to the metal.
  • C is everywhere. You'll see examples in books, lectures, videos, everywhere while you're studying.
  • The C Programming Language, 2nd Edition
    • This is a short book, but it will give you a great handle on the C language and if you practice it a little you'll quickly get proficient. Understanding C helps you understand how programs and memory work.
    • You don't need to go super deep in the book (or even finish it). Just get to where you're comfortable reading and writing in C.
• Python: Modern and very expressive, I learned it because it's just super useful and also allows me to write less code in an interview.

This is my preference. You do what you like, of course.

You may not need it, but here are some sites for learning a new language:

• Exercism
• Codewars
• HackerEarth
• Scaler Topics (Java, C++)
• Programiz PRO Community Challenges)

You can use a language you are comfortable in to do the coding part of the interview, but for large companies, these are solid choices:

• C++
• Java
• Python

You could also use these, but read around first. There may be caveats:

• JavaScript
• Ruby

Here is an article I wrote about choosing a language for the interview: Pick One Language for the Coding Interview. This is the original article my post was based on: Choosing a Programming Language for Interviews

You need to be very comfortable in the language and be knowledgeable.

Read more about choices:

• Choose the Right Language for Your Coding Interview

See language-specific resources here

⬆ back to top

This book will form your foundation for computer science.

Just choose one, in a language that you will be comfortable with. You'll be doing a lot of reading and coding.

• Coding Interview Patterns: Nail Your Next Coding Interview (Main Recommendation)
  • An insider’s perspective on what interviewers are truly looking for and why.
  • 101 real coding interview problems with detailed solutions.
  • Intuitive explanations that guide you through each problem as if you were solving it in a live interview.
  • 1000+ diagrams to illustrate key concepts and patterns.

• Algorithms in C, Parts 1-5 (Bundle), 3rd Edition
  • Fundamentals, Data Structures, Sorting, Searching, and Graph Algorithms

Your choice:

• Goodrich, Tamassia, Goldwasser
  • Data Structures and Algorithms in Java
• Sedgewick and Wayne:
  • Algorithms
  • Free Coursera course that covers the book (taught by the authors!):
    • Algorithms I
    • Algorithms II

Your choice:

• Goodrich, Tamassia, and Mount
  • Data Structures and Algorithms in C++, 2nd Edition
• Sedgewick and Wayne
  • Algorithms in C++, Parts 1-4: Fundamentals, Data Structure, Sorting, Searching
  • Algorithms in C++ Part 5: Graph Algorithms

⬆ back to top

Here are some recommended books to supplement your learning.

• Coding Interview Patterns: Nail Your Next Coding Interview

• Programming Interviews Exposed: Coding Your Way Through the Interview, 4th Edition

  • Answers in C++ and Java
  • This is a good warm-up for Cracking the Coding Interview
  • Not too difficult. Most problems may be easier than what you'll see in an interview (from what I've read)

• Cracking the Coding Interview, 6th Edition

  • answers in Java

Choose one:

• Elements of Programming Interviews (C++ version)
• Elements of Programming Interviews in Python
• Elements of Programming Interviews (Java version) - Companion Project - Method Stub and Test Cases for Every Problem in the Book

⬆ back to top

This list grew over many months, and yes, it got out of hand.

Here are some mistakes I made so you'll have a better experience. And you'll save months of time.

I watched hours of videos and took copious notes, and months later there was much I didn't remember. I spent 3 days going through my notes and making flashcards, so I could review. I didn't need all of that knowledge.

Please, read so you won't make my mistakes:

Retaining Computer Science Knowledge.

To solve the problem, I made a little flashcard site where I could add flashcards of 2 types: general and code. Each card has a different formatting. I made a mobile-first website, so I could review on my phone or tablet, wherever I am.

Make your own for free:

• Flashcards site repo

I DON'T RECOMMEND using my flashcards. There are too many and most of them are trivia that you don't need.

But if you don't want to listen to me, here you go:

• My flash cards database (1200 cards):
• My flash cards database (extreme - 1800 cards):

Keep in mind I went overboard and have cards covering everything from assembly language and Python trivia to machine learning and statistics. It's way too much for what's required.

Note on flashcards: The first time you recognize you know the answer, don't mark it as known. You have to see the same card and answer it several times correctly before you really know it. Repetition will put that knowledge deeper in your brain.

An alternative to using my flashcard site is Anki, which has been recommended to me numerous times. It uses a repetition system to help you remember. It's user-friendly, available on all platforms, and has a cloud sync system. It costs $25 on iOS but is free on other platforms.

My flashcard database in Anki format: https://ankiweb.net/shared/info/25173560 (thanks @xiewenya).

Some students have mentioned formatting issues with white space that can be fixed by doing the following: open the deck, edit the card, click cards, select the "styling" radio button, and add the member "white-space: pre;" to the card class.

THIS IS VERY IMPORTANT.

Start doing coding interview questions while you're learning data structures and algorithms.

You need to apply what you're learning to solve problems, or you'll forget. I made this mistake.

Once you've learned a topic, and feel somewhat comfortable with it, for example, linked lists:

1. Open one of the coding interview books (or coding problem websites, listed below)
2. Do 2 or 3 questions regarding linked lists.
3. Move on to the next learning topic.
4. Later, go back and do another 2 or 3 linked list problems.
5. Do this with each new topic you learn.

Keep doing problems while you're learning all this stuff, not after.

You're not being hired for knowledge, but how you apply the knowledge.

There are many resources for this, listed below. Keep going.

There are a lot of distractions that can take up valuable time. Focus and concentration are hard. Turn on some music without lyrics and you'll be able to focus pretty well.

⬆ back to top

These are prevalent technologies but not part of this study plan:

• Javascript
• HTML, CSS, and other front-end technologies
• SQL

⬆ back to top

This course goes over a lot of subjects. Each will probably take you a few days, or maybe even a week or more. It depends on your schedule.

Each day, take the next subject in the list, watch some videos about that subject, and then write an implementation of that data structure or algorithm in the language you chose for this course.

You can see my code here:

• C
• C++
• Python

You don't need to memorize every algorithm. You just need to be able to understand it enough to be able to write your own implementation.

⬆ back to top

Why is this here? I'm not ready to interview.

Then go back and read this.

Why you need to practice doing programming problems:

• Problem recognition, and where the right data structures and algorithms fit in
• Gathering requirements for the problem
• Talking your way through the problem like you will in the interview
• Coding on a whiteboard or paper, not a computer
• Coming up with time and space complexity for your solutions (see Big-O below)
• Testing your solutions

There is a great intro for methodical, communicative problem-solving in an interview. You'll get this from the programming interview books, too, but I found this outstanding: Algorithm design canvas

Write code on a whiteboard or paper, not a computer. Test with some sample inputs. Then type it and test it out on a computer.

If you don't have a whiteboard at home, pick up a large drawing pad from an art store. You can sit on the couch and practice. This is my "sofa whiteboard". I added the pen in the photo just for scale. If you use a pen, you'll wish you could erase. Gets messy quickly. I use a pencil and eraser.

Coding question practice is not about memorizing answers to programming problems.

⬆ back to top

Don't forget your key coding interview books here.

Solving Problems:

• How to Find a Solution
• How to Dissect a Topcoder Problem Statement

Coding Interview Question Videos:

• IDeserve (88 videos)
• Tushar Roy (5 playlists)
  • Super for walkthroughs of problem solutions
• Nick White - LeetCode Solutions (187 Videos)
  • Good explanations of the solution and the code
  • You can watch several in a short time
• FisherCoder - LeetCode Solutions

Challenge/Practice sites:

• LeetCode
  • My favorite coding problem site. It's worth the subscription money for the 1-2 months you'll likely be preparing.
  • See Nick White and FisherCoder Videos above for code walk-throughs.
• HackerRank
• TopCoder
• Codeforces
• Codility
• Geeks for Geeks
• AlgoExpert
  • Created by Google engineers, this is also an excellent resource to hone your skills.
• Project Euler
  • very math-focused, and not really suited for coding interviews

⬆ back to top

Alright, enough talk, let's learn!

But don't forget to do coding problems from above while you learn!

• Nothing to implement here, you're just watching videos and taking notes! Yay!
• There are a lot of videos here. Just watch enough until you understand it. You can always come back and review.
• Don't worry if you don't understand all the math behind it.
• You just need to understand how to express the complexity of an algorithm in terms of Big-O.
• Harvard CS50 - Asymptotic Notation (video)
• Big O Notations (general quick tutorial) (video)
• Big O Notation (and Omega and Theta) - best mathematical explanation (video)
• Skiena (video)
• UC Berkeley Big O (video)
• Amortized Analysis (video)
• TopCoder (includes recurrence relations and master theorem):
  • Computational Complexity: Section 1
  • Computational Complexity: Section 2
• Cheat sheet
• [Review] Analyzing Algorithms (playlist) in 18 minutes (video)

Well, that's about enough of that.

When you go through "Cracking the Coding Interview", there is a chapter on this, and at the end there is a quiz to see if you can identify the runtime complexity of different algorithms. It's a super review and test.

⬆ back to top

• Arrays

  • About Arrays:
    • Arrays CS50 Harvard University
    • Arrays (video)
    • UC Berkeley CS61B - Linear and Multi-Dim Arrays (video) (Start watching from 15m 32s)
    • Dynamic Arrays (video)
    • Jagged Arrays (video)
  • Implement a vector (mutable array with automatic resizing):
    • Practice coding using arrays and pointers, and pointer math to jump to an index instead of using indexing.
    • New raw data array with allocated memory
      • can allocate int array under the hood, just not use its features
      • start with 16, or if the starting number is greater, use power of 2 - 16, 32, 64, 128
    • size() - number of items
    • capacity() - number of items it can hold
    • is_empty()
    • at(index) - returns the item at a given index, blows up if index out of bounds
    • push(item)
    • insert(index, item) - inserts item at index, shifts that index's value and trailing elements to the right
    • prepend(item) - can use insert above at index 0
    • pop() - remove from end, return value
    • delete(index) - delete item at index, shifting all trailing elements left
    • remove(item) - looks for value and removes index holding it (even if in multiple places)
    • find(item) - looks for value and returns first index with that value, -1 if not found
    • resize(new_capacity) // private function
      • when you reach capacity, resize to double the size
      • when popping an item, if the size is 1/4 of capacity, resize to half
  • Time
    • O(1) to add/remove at end (amortized for allocations for more space), index, or update
    • O(n) to insert/remove elsewhere
  • Space
    • contiguous in memory, so proximity helps performance
    • space needed = (array capacity, which is >= n) * size of item, but even if 2n, still O(n)

• Linked Lists

  • Description:
    • Linked Lists CS50 Harvard University - this builds the intuition.
    • Singly Linked Lists (video)
    • CS 61B - Linked Lists 1 (video)
    • CS 61B - Linked Lists 2 (video)
    • [Review] Linked lists in 4 minutes (video)
  • C Code (video) - not the whole video, just portions about Node struct and memory allocation
  • Linked List vs Arrays:
    • Core Linked Lists Vs Arrays (video)
    • In The Real World Linked Lists Vs Arrays (video)
  • Why you should avoid linked lists (video)
  • Gotcha: you need pointer to pointer knowledge: (for when you pass a pointer to a function that may change the address where that pointer points) This page is just to get a grasp on ptr to ptr. I don't recommend this list traversal style. Readability and maintainability suffer due to cleverness.
    • Pointers to Pointers
  • Implement (I did with tail pointer & without):
    • size() - returns the number of data elements in the list
    • empty() - bool returns true if empty
    • value_at(index) - returns the value of the nth item (starting at 0 for first)
    • push_front(value) - adds an item to the front of the list
    • pop_front() - remove the front item and return its value
    • push_back(value) - adds an item at the end
    • pop_back() - removes end item and returns its value
    • front() - get the value of the front item
    • back() - get the value of the end item
    • insert(index, value) - insert value at index, so the current item at that index is pointed to by the new item at the index
    • erase(index) - removes node at given index
    • value_n_from_end(n) - returns the value of the node at the nth position from the end of the list
    • reverse() - reverses the list
    • remove_value(value) - removes the first item in the list with this value
  • Doubly-linked List
    • Description (video)
    • No need to implement

• Stack

  • Stacks (video)
  • [Review] Stacks in 3 minutes (video)
  • Will not implement. Implementing with the array is trivial

• Queue

  • Queue (video)
  • Circular buffer/FIFO
  • [Review] Queues in 3 minutes (video)
  • Implement using linked-list, with tail pointer:
    • enqueue(value) - adds value at a position at the tail
    • dequeue() - returns value and removes least recently added element (front)
    • empty()
  • Implement using a fixed-sized array:
    • enqueue(value) - adds item at end of available storage
    • dequeue() - returns value and removes least recently added element
    • empty()
    • full()
  • Cost:
    • a bad implementation using a linked list where you enqueue at the head and dequeue at the tail would be O(n) because you'd need the next to last element, causing a full traversal of each dequeue
    • enqueue: O(1) (amortized, linked list and array [probing])
    • dequeue: O(1) (linked list and array)
    • empty: O(1) (linked list and array)

• Hash table

  • Videos:

    • Hashing with Chaining (video)
    • Table Doubling, Karp-Rabin (video)
    • Open Addressing, Cryptographic Hashing (video)
    • PyCon 2010: The Mighty Dictionary (video)
    • PyCon 2017: The Dictionary Even Mightier (video)
    • (Advanced) Randomization: Universal & Perfect Hashing (video)
    • (Advanced) Perfect hashing (video)
    • [Review] Hash tables in 4 minutes (video)

  • Online Courses:

    • Core Hash Tables (video)
    • Data Structures (video)
    • Phone Book Problem (video)
    • distributed hash tables:
      • Instant Uploads And Storage Optimization In Dropbox (video)
      • Distributed Hash Tables (video)

  • Implement with array using linear probing

    • hash(k, m) - m is the size of the hash table
    • add(key, value) - if the key already exists, update value
    • exists(key)
    • get(key)
    • remove(key)

⬆ back to top

• Binary search

  • Binary Search (video)
  • Binary Search (video)
  • detail
  • blueprint
  • [Review] Binary search in 4 minutes (video)
  • Implement:
    • binary search (on a sorted array of integers)
    • binary search using recursion

• Bitwise operations

  • Bits cheat sheet
    • you should know many of the powers of 2 from (2^1 to 2^16 and 2^32)
  • Get a really good understanding of manipulating bits with: &, |, ^, ~, >>, <<
    • words
    • Good intro: Bit Manipulation (video)
    • C Programming Tutorial 2-10: Bitwise Operators (video)
    • Bit Manipulation
    • Bitwise Operation
    • Bithacks
    • The Bit Twiddler
    • The Bit Twiddler Interactive
    • Bit Hacks (video)
    • Practice Operations
  • 2s and 1s complement
    • Binary: Plusses & Minuses (Why We Use Two's Complement) (video)
    • 1s Complement
    • 2s Complement
  • Count set bits
    • 4 ways to count bits in a byte (video)
    • Count Bits
    • How To Count The Number Of Set Bits In a 32 Bit Integer
  • Swap values:
    • Swap
  • Absolute value:
    • Absolute Integer

⬆ back to top

• Trees - Intro

  • Intro to Trees (video)
  • Tree Traversal (video)
  • BFS(breadth-first search) and DFS(depth-first search) (video)
    • BFS notes:
      • level order (BFS, using queue)
      • time complexity: O(n)
      • space complexity: best: O(1), worst: O(n/2)=O(n)
    • DFS notes:
      • time complexity: O(n)
      • space complexity: best: O(log n) - avg. height of tree worst: O(n)
      • inorder (DFS: left, self, right)
      • postorder (DFS: left, right, self)
      • preorder (DFS: self, left, right)
  • [Review] Breadth-first search in 4 minutes (video)
  • [Review] Depth-first search in 4 minutes (video)
  • [Review] Tree Traversal (playlist) in 11 minutes (video)

• Binary search trees: BSTs

  • Binary Search Tree Review (video)
  • Introduction (video)
  • MIT (video)
  • C/C++:
    • Binary search tree - Implementation in C/C++ (video)
    • BST implementation - memory allocation in stack and heap (video)
    • Find min and max element in a binary search tree (video)
    • Find the height of a binary tree (video)
    • Binary tree traversal - breadth-first and depth-first strategies (video)
    • Binary tree: Level Order Traversal (video)
    • Binary tree traversal: Preorder, Inorder, Postorder (video)
    • Check if a binary tree is a binary search tree or not (video)
    • Delete a node from Binary Search Tree (video)
    • Inorder Successor in a binary search tree (video)
  • Implement:
    • insert // insert value into tree
    • get_node_count // get count of values stored
    • print_values // prints the values in the tree, from min to max
    • delete_tree
    • is_in_tree // returns true if a given value exists in the tree
    • get_height // returns the height in nodes (single node's height is 1)
    • get_min // returns the minimum value stored in the tree
    • get_max // returns the maximum value stored in the tree
    • is_binary_search_tree
    • delete_value
    • get_successor // returns the next-highest value in the tree after given value, -1 if none

• Heap / Priority Queue / Binary Heap

  • visualized as a tree, but is usually linear in storage (array, linked list)
  • Heap
  • Introduction (video)
  • Binary Trees (video)
  • Tree Height Remark (video)
  • Basic Operations (video)
  • Complete Binary Trees (video)
  • Pseudocode (video)
  • Heap Sort - jumps to start (video)
  • Heap Sort (video)
  • Building a heap (video)
  • MIT 6.006 Introduction to Algorithms: Binary Heaps
  • CS 61B Lecture 24: Priority Queues (video)
  • Linear Time BuildHeap (max-heap)
  • [Review] Heap (playlist) in 13 minutes (video)
  • Implement a max-heap:
    • insert
    • sift_up - needed for insert
    • get_max - returns the max item, without removing it
    • get_size() - return number of elements stored
    • is_empty() - returns true if the heap contains no elements
    • extract_max - returns the max item, removing it
    • sift_down - needed for extract_max
    • remove(x) - removes item at index x
    • heapify - create a heap from an array of elements, needed for heap_sort
    • heap_sort() - take an unsorted array and turn it into a sorted array in place using a max heap or min heap

⬆ back to top

• Notes:

  • Implement sorts & know best case/worst case, average complexity of each:
    • no bubble sort - it's terrible - O(n^2), except when n <= 16
  • Stability in sorting algorithms ("Is Quicksort stable?")
    • Sorting Algorithm Stability
    • Stability In Sorting Algorithms
    • Stability In Sorting Algorithms
    • Sorting Algorithms - Stability
  • Which algorithms can be used on linked lists? Which on arrays? Which of both?
    • I wouldn't recommend sorting a linked list, but merge sort is doable.
    • Merge Sort For Linked List

• For heapsort, see the Heap data structure above. Heap sort is great, but not stable

• Sedgewick - Mergesort (5 videos)