Kamran Ahmed
9 months ago
commit
f8e5833f6a
169 changed files with 11176 additions and 383 deletions
Binary file not shown.
Binary file not shown.
|
After Width: | Height: | Size: 288 KiB |
@ -0,0 +1,41 @@ |
||||
import { useState } from 'react'; |
||||
import { GitHubButton } from './GitHubButton'; |
||||
import { GoogleButton } from './GoogleButton'; |
||||
import { LinkedInButton } from './LinkedInButton'; |
||||
import { EmailLoginForm } from './EmailLoginForm'; |
||||
import { EmailSignupForm } from './EmailSignupForm'; |
||||
|
||||
type AuthenticationFormProps = { |
||||
type?: 'login' | 'signup'; |
||||
}; |
||||
|
||||
export function AuthenticationForm(props: AuthenticationFormProps) { |
||||
const { type = 'login' } = props; |
||||
|
||||
const [isDisabled, setIsDisabled] = useState(false); |
||||
|
||||
return ( |
||||
<> |
||||
<div className="flex w-full flex-col gap-2"> |
||||
<GitHubButton isDisabled={isDisabled} setIsDisabled={setIsDisabled} /> |
||||
<GoogleButton isDisabled={isDisabled} setIsDisabled={setIsDisabled} /> |
||||
<LinkedInButton isDisabled={isDisabled} setIsDisabled={setIsDisabled} /> |
||||
</div> |
||||
|
||||
<div className="flex w-full items-center gap-2 py-6 text-sm text-slate-600"> |
||||
<div className="h-px w-full bg-slate-200" /> |
||||
OR |
||||
<div className="h-px w-full bg-slate-200" /> |
||||
</div> |
||||
|
||||
{type === 'login' ? ( |
||||
<EmailLoginForm isDisabled={isDisabled} setIsDisabled={setIsDisabled} /> |
||||
) : ( |
||||
<EmailSignupForm |
||||
isDisabled={isDisabled} |
||||
setIsDisabled={setIsDisabled} |
||||
/> |
||||
)} |
||||
</> |
||||
); |
||||
} |
||||
@ -1,42 +1,34 @@ |
||||
--- |
||||
import { getFormattedStars } from '../lib/github'; |
||||
import Icon from './AstroIcon.astro'; |
||||
import { getDiscordInfo } from '../lib/discord'; |
||||
import OpenSourceStat from './OpenSourceStat.astro'; |
||||
|
||||
const starCount = await getFormattedStars('kamranahmedse/developer-roadmap'); |
||||
const discordInfo = await getDiscordInfo(); |
||||
--- |
||||
|
||||
<div class='py-6 sm:py-16 border-b border-t text-left sm:text-center bg-white'> |
||||
<div class='!max-w-[600px] container'> |
||||
<p class='text-2xl sm:text-5xl font-bold'>Community</p> |
||||
<p class='text-gray-600 text-sm sm:text-lg leading-relaxed my-2.5 sm:my-5'> |
||||
<div class='border-b border-t bg-white py-6 text-left sm:py-16 sm:text-center'> |
||||
<div class='container !max-w-[650px]'> |
||||
<p class='text-2xl font-bold sm:text-5xl'>Join the Community</p> |
||||
<p class='my-2.5 text-sm leading-relaxed text-gray-600 sm:my-5 sm:text-lg'> |
||||
roadmap.sh is the <a |
||||
href='https://github.com/search?o=desc&q=stars%3A%3E100000&s=stars&type=Repositories' |
||||
target='_blank' |
||||
class='font-medium text-gray-600 hover:text-black underline underline-offset-2' |
||||
class='font-medium text-gray-600 underline underline-offset-2 hover:text-black' |
||||
>6th most starred project on GitHub</a |
||||
> and is visited by hundreds of thousands of developers every month. |
||||
</p> |
||||
|
||||
<div class='flex justify-start flex-col sm:flex-row sm:justify-center gap-2 sm:gap-3 mb-1.5 sm:mb-0'> |
||||
<a |
||||
href='https://github.com/kamranahmedse/developer-roadmap' |
||||
target='_blank' |
||||
class='inline-flex items-center border border-black py-1.5 px-3 rounded-lg text-sm hover:text-white hover:bg-black bg-white' |
||||
> |
||||
<Icon icon='star' class='mr-1 -ml-1 fill-current' /> |
||||
|
||||
<span class='lowercase'>{starCount}</span> |
||||
<span class='ml-2 hover:block'>GitHub Stars</span> |
||||
</a> |
||||
|
||||
<a |
||||
href="https://discord.gg/cJpEt5Qbwa" |
||||
target='_blank' |
||||
class='relative pointer inline-flex items-center border border-black py-1.5 px-3 rounded-lg text-sm hover:text-white hover:bg-black bg-white group' |
||||
> |
||||
<Icon icon='discord' class='h-[14px] mr-2 -ml-1 fill-current' /> |
||||
Join on Discord |
||||
</a> |
||||
<div |
||||
class='mt-5 grid grid-cols-1 justify-between gap-2 divide-x-0 sm:my-11 sm:grid-cols-3 sm:gap-0 sm:divide-x' |
||||
> |
||||
<OpenSourceStat text='GitHub Stars' value={starCount} /> |
||||
<OpenSourceStat text='Registered Users' value={'850k'} /> |
||||
<OpenSourceStat |
||||
text='Discord Members' |
||||
value={discordInfo.totalFormatted} |
||||
/> |
||||
</div> |
||||
</div> |
||||
</div> |
||||
|
||||
@ -0,0 +1,105 @@ |
||||
--- |
||||
import { ChevronUp } from 'lucide-react'; |
||||
import Icon from './AstroIcon.astro'; |
||||
export interface Props { |
||||
value: string; |
||||
text: string; |
||||
} |
||||
|
||||
const { value, text } = Astro.props; |
||||
|
||||
const isGitHubStars = text.toLowerCase() === 'github stars'; |
||||
const isRegistered = text.toLowerCase() === 'registered users'; |
||||
const isDiscordMembers = text.toLowerCase() === 'discord members'; |
||||
--- |
||||
|
||||
<div |
||||
class='flex items-start sm:items-center justify-start flex-col sm:justify-center sm:gap-0 gap-2 sm:bg-transparent bg-gray-200 sm:rounded-none rounded-xl p-4' |
||||
> |
||||
{ |
||||
isGitHubStars && ( |
||||
<p class='flex items-center text-sm text-blue-500 sm:flex'> |
||||
<span class='rounded-md bg-blue-500 px-1 text-white'>Rank 6th</span> |
||||
out of 28M! |
||||
</p> |
||||
) |
||||
} |
||||
|
||||
{ |
||||
isRegistered && ( |
||||
<p class='flex items-center text-sm text-blue-500 sm:flex'> |
||||
<span class='mr-1.5 rounded-md bg-blue-500 px-1 text-white'>+55k</span> |
||||
every month |
||||
</p> |
||||
) |
||||
} |
||||
|
||||
{ |
||||
isDiscordMembers && ( |
||||
<p class='flex items-center text-sm text-blue-500 sm:flex'> |
||||
<span class='mr-1.5 rounded-md bg-blue-500 px-1 text-white'>+1.5k</span> |
||||
every month |
||||
</p> |
||||
) |
||||
} |
||||
<div class="flex flex-row items-center sm:flex-col my-1 sm:my-0"> |
||||
<p |
||||
class='relative my-0 sm:my-4 mr-1 sm:mr-0 text-base font-bold lowercase sm:w-auto sm:text-5xl' |
||||
> |
||||
{value} |
||||
</p> |
||||
<p class='mb-0 mt-0 text-base sm:text-xs tracking-wide text-black sm:-mt-3 sm:mb-5'> |
||||
{text} |
||||
</p> |
||||
</div> |
||||
{ |
||||
isGitHubStars && ( |
||||
<a |
||||
href='https://github.com/kamranahmedse/developer-roadmap' |
||||
target='_blank' |
||||
class='group mt-0 flex flex-col items-center rounded-lg border border-black bg-white px-3 py-2 text-sm hover:bg-black hover:text-white' |
||||
> |
||||
<div class='mb-0.5 flex items-center font-semibold'> |
||||
<Icon icon='star' class='-ml-1 fill-current' /> |
||||
<span class='ml-1.5 hover:block'>Star us on GitHub</span> |
||||
</div> |
||||
<span class='text-xs text-gray-500 group-hover:text-gray-100'> |
||||
Help us reach #1 |
||||
</span> |
||||
</a> |
||||
) |
||||
} |
||||
{ |
||||
isRegistered && ( |
||||
<a |
||||
href='/signup' |
||||
class='group mt-0 flex flex-col items-center rounded-lg border border-black bg-white px-3 py-2 text-sm hover:bg-black hover:text-white' |
||||
> |
||||
<div class='mb-0.5 flex items-center font-semibold'> |
||||
<Icon icon='users' class='-ml-1 h-[15px] fill-current' /> |
||||
<span class='ml-1 hover:block'>Register yourself</span> |
||||
</div> |
||||
<span class='text-xs text-gray-500 group-hover:text-gray-100'> |
||||
Commit to your growth |
||||
</span> |
||||
</a> |
||||
) |
||||
} |
||||
{ |
||||
isDiscordMembers && ( |
||||
<a |
||||
href='https://discord.gg/cJpEt5Qbwa' |
||||
target='_blank' |
||||
class='group mt-0 flex flex-col items-center rounded-lg border border-black bg-white px-3 py-2 text-sm hover:bg-black hover:text-white' |
||||
> |
||||
<div class='mb-0.5 flex items-center font-semibold'> |
||||
<Icon icon='discord' class='-ml-1 h-[13px] fill-current' /> |
||||
<span class='ml-1 hover:block'>Join on Discord</span> |
||||
</div> |
||||
<span class='text-xs text-gray-500 group-hover:text-gray-100'> |
||||
Join the community |
||||
</span> |
||||
</a> |
||||
) |
||||
} |
||||
</div> |
||||
@ -1,7 +1,3 @@ |
||||
# Hateoas |
||||
|
||||
HATEOAS is an acronym for <b>H</b>ypermedia <b>A</b>s <b>T</b>he <b>E</b>ngine <b>O</b>f <b>A</b>pplication <b>S</b>tate, it's the concept that when sending information over a RESTful API the document received should contain everything the client needs in order to parse and use the data i.e they don't have to contact any other endpoint not explicitly mentioned within the Document |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [Oktane17: Designing Beautiful REST + JSON APIs (3:56 - 5:57)](https://youtu.be/MiOSzpfP1Ww?t=236) |
||||
HATEOAS is an acronym for <b>H</b>ypermedia <b>A</b>s <b>T</b>he <b>E</b>ngine <b>O</b>f <b>A</b>pplication <b>S</b>tate, it's the concept that when sending information over a RESTful API the document received should contain everything the client needs in order to parse and use the data i.e they don't have to contact any other endpoint not explicitly mentioned within the Document. |
||||
|
||||
@ -0,0 +1,16 @@ |
||||
# JavaScript |
||||
|
||||
JavaScript allows you to add interactivity to your pages. Common examples that you may have seen on the websites are sliders, click interactions, popups and so on. Apart from being used on the frontend in browsers, there is Node.js which is an open-source, cross-platform, back-end JavaScript runtime environment that runs on the V8 engine and executes JavaScript code outside a web browser. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [Visit Dedicated JavaScript Roadmap](/javascript) |
||||
- [W3Schools – JavaScript Tutorial](https://www.w3schools.com/js/) |
||||
- [The Modern JavaScript Tutorial](https://javascript.info/) |
||||
- [Codecademy - Learn JavaScript](https://www.codecademy.com/learn/introduction-to-javascript) |
||||
- [JavaScript Crash Course for Beginners](https://youtu.be/hdI2bqOjy3c) |
||||
- [Node.js Crash Course](https://www.youtube.com/watch?v=fBNz5xF-Kx4) |
||||
- [Node.js Tutorial for Beginners](https://www.youtube.com/watch?v=TlB_eWDSMt4) |
||||
- [W3Schools – Node.js Tutorial](https://www.w3schools.com/nodejs/) |
||||
- [What is NPM?](https://www.w3schools.com/nodejs/nodejs_npm.asp) |
||||
- [Official Documentation](https://nodejs.org/en/learn/getting-started/introduction-to-nodejs) |
||||
@ -0,0 +1,13 @@ |
||||
# Java |
||||
|
||||
Java is general-purpose language, primarily used for Internet-based applications. |
||||
It was created in 1995 by James Gosling at Sun Microsystems and is one of the most popular options for backend developers. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [Visit Dedicated Java Roadmap](/java) |
||||
- [Java Website](https://www.java.com/) |
||||
- [Codeacademy - Free Course](https://www.codecademy.com/learn/learn-java) |
||||
- [W3 Schools Tutorials](https://www.w3schools.com/java/) |
||||
- [Java Crash Course](https://www.youtube.com/watch?v=eIrMbAQSU34) |
||||
- [Complete Java course](https://www.youtube.com/watch?v=xk4_1vDrzzo) |
||||
@ -0,0 +1,14 @@ |
||||
# Go |
||||
|
||||
Go is an open source programming language supported by Google. Go can be used to write cloud services, CLI tools, used for API development, and much more. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [Visit Dedicated Go Roadmap](/golang) |
||||
- [A Tour of Go – Go Basics](https://go.dev/tour/welcome/1) |
||||
- [Go Reference Documentation](https://go.dev/doc/) |
||||
- [Go by Example - annotated example programs](https://gobyexample.com/) |
||||
- [Learn Go | Codecademy](https://www.codecademy.com/learn/learn-go) |
||||
- [W3Schools Go Tutorial ](https://www.w3schools.com/go/) |
||||
- [Making a RESTful JSON API in Go](https://thenewstack.io/make-a-restful-json-api-go/) |
||||
- [Go, the Programming Language of the Cloud](https://thenewstack.io/go-the-programming-language-of-the-cloud/) |
||||
@ -0,0 +1,10 @@ |
||||
# C# |
||||
|
||||
C# (pronounced "C sharp") is a general purpose programming language made by Microsoft. It is used to perform different tasks and can be used to create web apps, games, mobile apps, etc. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [C# Learning Path](https://docs.microsoft.com/en-us/learn/paths/csharp-first-steps/?WT.mc_id=dotnet-35129-website) |
||||
- [C# on W3 schools](https://www.w3schools.com/cs/index.php) |
||||
- [Introduction to C#](https://docs.microsoft.com/en-us/shows/CSharp-101/?WT.mc_id=Educationalcsharp-c9-scottha) |
||||
- [C# tutorials](https://www.youtube.com/watch?v=gfkTfcpWqAY&list=PLTjRvDozrdlz3_FPXwb6lX_HoGXa09Yef) |
||||
@ -0,0 +1,8 @@ |
||||
# C++ |
||||
|
||||
C++ is a powerful general-purpose programming language. It can be used to develop operating systems, browsers, games, and so on. C++ supports different ways of programming like procedural, object-oriented, functional, and so on. This makes C++ powerful as well as flexible. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [Learn Cpp](https://learncpp.com/) |
||||
- [C++ Reference](https://en.cppreference.com/) |
||||
@ -0,0 +1,18 @@ |
||||
# Python |
||||
|
||||
Python is a well known programming language which is both a strongly typed and a dynamically typed language. Being an interpreted language, code is executed as soon as it is written and the Python syntax allows for writing code in functional, procedural or object-oriented programmatic ways. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [Visit Dedicated Python Roadmap](/python) |
||||
- [Python Website](https://www.python.org/) |
||||
- [Python Getting Started](https://www.python.org/about/gettingstarted/) |
||||
- [Automate the Boring Stuff](https://automatetheboringstuff.com/) |
||||
- [FreeCodeCamp.org - How to Learn Python ? ](https://www.freecodecamp.org/news/how-to-learn-python/) |
||||
- [Python principles - Python basics](https://pythonprinciples.com/) |
||||
- [W3Schools - Python Tutorial ](https://www.w3schools.com/python/) |
||||
- [Python Crash Course](https://ehmatthes.github.io/pcc/) |
||||
- [Codecademy - Learn Python 2](https://www.codecademy.com/learn/learn-python) |
||||
- [An Introduction to Python for Non-Programmers](https://thenewstack.io/an-introduction-to-python-for-non-programmers/) |
||||
- [Getting Started with Python and InfluxDB](https://thenewstack.io/getting-started-with-python-and-influxdb/) |
||||
- [Python for Beginners - Learn Python in 1 Hour](https://www.youtube.com/watch?v=kqtD5dpn9C8&ab_channel=ProgrammingwithMosh) |
||||
@ -0,0 +1,10 @@ |
||||
# Rust |
||||
|
||||
Rust is a modern systems programming language focusing on safety, speed, and concurrency. It accomplishes these goals by being memory safe without using garbage collection. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [The Rust Programming Language - online book](https://doc.rust-lang.org/book/) |
||||
- [Rust by Example - collection of runnable examples](https://doc.rust-lang.org/stable/rust-by-example/index.html) |
||||
- [Rust vs. Go: Why They’re Better Together](https://thenewstack.io/rust-vs-go-why-theyre-better-together/) |
||||
- [Rust by the Numbers: The Rust Programming Language in 2021](https://thenewstack.io/rust-by-the-numbers-the-rust-programming-language-in-2021/) |
||||
@ -0,0 +1,10 @@ |
||||
# Ruby |
||||
|
||||
Ruby is a high-level, interpreted programming language that blends Perl, Smalltalk, Eiffel, Ada, and Lisp. Ruby focuses on simplicity and productivity along with a syntax that reads and writes naturally. Ruby supports procedural, object-oriented and functional programming and is dynamically typed. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [Ruby Website](https://www.ruby-lang.org/en/) |
||||
- [Learn Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) |
||||
- [Learn Ruby | Codecademy](https://www.codecademy.com/learn/learn-ruby) |
||||
- [Ruby, An Introduction to a Programmer’s Best Friend](https://thenewstack.io/ruby-a-programmers-best-friend/) |
||||
@ -0,0 +1,3 @@ |
||||
# Pick a Language |
||||
|
||||
Pick a programming language to practice data structures and algorithms with. You should pick a language that you are comfortable with or plan to adopt. |
||||
@ -0,0 +1,5 @@ |
||||
# Language Syntax |
||||
|
||||
Language syntax refers to the set of rules that dictate how programs written in a particular programming language must be structured. This can include rules for how to declare variables, how to call functions, how to structure control flow statements, and so on. Syntax varies significantly between different programming languages, so it is critical to grasp the specific syntax of the language you are using. It’s similar to grammar in human languages - putting words in the wrong order or including extraneous punctuation can make a sentence hard to understand, and the same applies to programming. Incorrect syntax leads to syntax errors which prevent your code from executing. |
||||
|
||||
Learn the language syntax of the programming language you are using. |
||||
@ -0,0 +1,3 @@ |
||||
# Control Structures |
||||
|
||||
Control structures are fundamental elements in most programming languages that facilitate the flow of control through a program. There are three main types of control structures: Sequential, Selection and Iteration. Sequential control structures are the default mode where instructions happen one after another. Selection control structures (often called "conditional" or "decision" structures) allow one set of instructions to be executed if a condition is true and another if it's false. These typically include `if...else` statements. Iteration control structures (also known as "loops") allow a block of code to be repeated multiple times. Common loop structures include `for`, `while`, and `do...while` loops. All these control structures play a vital role in shaping the program logic. |
||||
@ -0,0 +1,3 @@ |
||||
# Functions |
||||
|
||||
Functions in programming are named sections of a program that perform a specific task. They allow us to write a piece of code once and reuse it in different places throughout the program, making our code more modular and easier to maintain. Functions often take in input, do something with it, and return output. Functions can be categorized into four main types: built-in functions (like `print()`, provided by the programming language), user-defined functions (written by the user for a specific use case), anonymous functions (also known as lambda functions, which are not declared using the standard `def` keyword), and higher-order functions (functions that take other functions as arguments or return a function). |
||||
@ -0,0 +1,3 @@ |
||||
# OOP Basics |
||||
|
||||
Object-oriented programming (OOP) is a programming paradigm that uses "objects" to design applications and software. In OOP, each object is an instance of a class. A class defines the properties (often known as attributes or fields) and methods (actions) that are common to all objects of a certain kind. A key principle of OOP is the ability to hide certain parts of the objects’ data from the outside, a concept known as encapsulation. Other key principles are inheritance, a way to form new classes using classes that have already been defined, and polymorphism, the concept of designing objects to share behaviors and being able to override shared behaviors with specifics. |
||||
@ -0,0 +1,3 @@ |
||||
# Pseudo Code |
||||
|
||||
Pseudo code is a plain language description of the steps in an algorithm or another system. It is intended for human reading rather than machine reading. Pseudo code often uses control structures and terms common to popular high-level programming languages without strictly adhering to the syntax of any particular one. The foremost aim of pseudocode is to explain the inner "algorithmic thinking" behind coding, rather than focusing on the syntax of a particular language. A nice feature of pseudocode is that it is largely able to be understood by a wider range of people than the corresponding code in a specific programming language, which enhances its roles in drafting, documentation, learning, and collaboration aspects. |
||||
@ -0,0 +1,3 @@ |
||||
# Programming Fundamentals |
||||
|
||||
Programming Fundamentals are the basic concepts and principles that form the foundation of any computer programming language. These include understanding variables, which store data for processing, control structures such as loops and conditional statements that direct the flow of a program, data structures which organize and store data efficiently, and algorithms which step by step instructions to solve specific problems or perform specific tasks. Mastery of these fundamentals forms the basis for learning any specific programming language and for writing efficient, effective code. |
||||
@ -0,0 +1,3 @@ |
||||
# What are Data Structures? |
||||
|
||||
Data structures are specialized formats for organizing and storing data in a computer so that it can be used efficiently. They provide a means to manage large amounts of data efficiently for uses such as large databases and internet indexing services. They are critical to programming and are used in almost all software systems including web development, operating systems, image editing, and much more. Some common types of data structures are arrays, linked lists, queues, stacks, trees, and graphs. The choice of the data structure often begins from the choice of an abstract data type, a broad type encapsulating various possible data structures." |
||||
@ -0,0 +1,3 @@ |
||||
# Importance of Data Structures |
||||
|
||||
Data structures are crucial in the field of computer science and coding because they offer a method of organizing and storing data in an efficient and manageable format. They're critical because they form the foundation for modern algorithm design. Your ability to choose or design the most suited data structure for a particular task can be the difference between a solution that's functional and efficient and one that isn't. They allow data to be processed in a variety of ways - stored, sorted, ordered, or accessed - which is integral to software or database development. By implementing effective data structures, programmers can enhance performance, ease coding procedures, allow flexibility of data and most importantly, reduce complexity of code in a significant manner. Markdown offers the advantage of clear, straightforward formatting to express these concepts. |
||||
@ -0,0 +1,3 @@ |
||||
# Data Structures |
||||
|
||||
Data Structures are a fundamental element of computer science. They provide a specific way to organize and store data so that it can be accessed and used efficiently. Different types of data structures include arrays, linked lists, stacks, queues, hash tables, trees, and graphs. Each of these has its unique characteristics and use-cases, and is optimal for certain kinds of operations. For example, arrays are excellent for random access, while linked lists work well for frequent insertions and deletions. The correct choice of data structure can significantly enhance the performance of your programs. |
||||
@ -0,0 +1,3 @@ |
||||
# Array |
||||
|
||||
An **Array** is a linear data structure that holds elements of the same type, which means we can store only a specific type of elements in the array. It uses contiguous memory space to store elements. In an array, we can directly access any element based on its index which makes it an efficient data structure. Arrays have two types: one-dimensional and multi-dimensional. In a one-dimensional array, data is stored in a linear form while a multi-dimensional array can store data in the form of a matrix or in 3-D format. |
||||
@ -0,0 +1,3 @@ |
||||
# Linked Lists |
||||
|
||||
Linked Lists are a type of data structure used for storing collections of data. The data is stored in nodes, each of which contains a data field and a reference (link) to the next node in the sequence. Structurally, a linked list is organized into a sequence or chain of nodes, hence the name. Two types of linked lists are commonly used: singly linked lists, where each node points to the next node and the last node points to null, and doubly linked lists, where each node has two links, one to the previous node and another one to the next. Linked Lists are used in other types of data structures like stacks and queues. |
||||
@ -0,0 +1,11 @@ |
||||
# Stacks |
||||
|
||||
A **stack** is a linear data structure that follows a particular order in which the operations are performed. The order may be LIFO (Last In First Out) or FILO (First In Last Out). Mainly three basic operations are performed in the stack: |
||||
|
||||
1. **Push**: adds an element to the collection. |
||||
|
||||
2. **Pop**: removes an element from the collection. A pop can result in stack underflow if the stack is empty. |
||||
|
||||
3. **Peek** or **Top**: returns the top item without removing it from the stack. |
||||
|
||||
The basic principle of stack operation is that in a stack, the element that is added last is the first one to come off, thus the name "Last in First Out". |
||||
@ -0,0 +1,3 @@ |
||||
# Queues |
||||
|
||||
Queues are a type of data structure in which elements are held in a sequence and access is restricted to one end. Elements are added ("enqueued") at the rear end and removed ("dequeued") from the front. This makes queues a First-In, First-Out (FIFO) data structure. This type of organization is particularly useful for specific situations such as printing jobs, handling requests in a web server, scheduling tasks in a system, etc. Due to its FIFO property, once a new element is inserted into the queue, all elements that were inserted before the new element must be removed before the new element can be invoked. The fundamental operations associated with queues include Enqueue (insert), Dequeue (remove) and Peek (get the top element). |
||||
@ -0,0 +1,3 @@ |
||||
# Hash Tables |
||||
|
||||
`Hash Tables` are specialized data structures that allow fast access to data based on a key. Essentially, a hash table works by taking a key input, and then computes an index into an array in which the desired value can be found. It uses a hash function to calculate this index. Suppose the elements are integers and the hash function returns the value at the unit's place. If the given key is 22, it will check the value at index 2. Collisions occur when the hash function returns the same output for two different inputs. There are different methods to handle these collisions such as chaining and open addressing. |
||||
@ -0,0 +1,9 @@ |
||||
# Basic Data Structures |
||||
|
||||
The five main types of basic data structures are: **Arrays**, **Linked Lists**, **Stacks**, **Queues**, and **Hash Tables**. |
||||
|
||||
- **Arrays** are static data structures that store elements of the same type in contiguous memory locations. |
||||
- **Linked Lists** are dynamic data structures that store elements in individual nodes, with each node pointing to the next. |
||||
- **Stacks** follow the Last-In-First-Out principle (LIFO) and primarily assist in function calls in most programming languages. |
||||
- **Queues** operate on the First-In-First-Out principle (FIFO) and are commonly used in task scheduling. |
||||
- Lastly, **Hash Tables** store key-value pairs allowing for fast insertion, deletion, and search operations. |
||||
@ -0,0 +1,3 @@ |
||||
# Time vs Space Complexity |
||||
|
||||
In the context of algorithmic complexity, "time" refers to the amount of computational time that the algorithm takes to execute, while "space" refers to the amount of memory that the algorithm needs to complete its operation. The time complexity of an algorithm quantifies the amount of time taken by an algorithm to run, as a function of the size of the input to the program. The space complexity of an algorithm quantifies the amount of space or memory taken by an algorithm to run, as a function of the size of the input to the program. It's important to note that time and space are often at odds with each other; optimizing an algorithm to be quicker often requires taking up more memory, and decreasing memory usage can often make the algorithm slower. This is known as the space-time tradeoff. |
||||
@ -0,0 +1,3 @@ |
||||
# How to Calculate Complexity? |
||||
|
||||
The process of calculating algorithmic complexity, often referred to as Big O notation, involves counting the operations or steps an algorithm takes in function of the size of its input. The aim is to identify the worst-case, average-case, and best-case complexity. Generally, the main focus is on the worst-case scenario which represents the maximum number of steps taken by an algorithm. To calculate it, you consider the highest order of size (n) in your algorithm's steps. For instance, if an algorithm performs a loop 5 times for 'n' items, and then does 3 unrelated steps, it has a complexity of O(n), because the linear steps grow faster than constant ones as n increases. Other complexities include O(1) for constant complexity, O(n) for linear complexity, O(n^2) for quadratic complexity, and so on, based on how the steps increase with size. |
||||
@ -0,0 +1,3 @@ |
||||
# Constant |
||||
|
||||
Constant time complexity is denoted as O(1). This means the running time of the algorithm remains constant, regardless of the size of the input data set. Whether you're working with an array of 10 elements or 1 million, if an operation takes the same amount of time regardless of the size of the array, it is said to have a constant time complexity. For example, accessing any element in an array by index is an O(1) operation, as the access operation takes the same amount of time regardless of the position of the element in the array. |
||||
@ -0,0 +1,3 @@ |
||||
# Logarithmic |
||||
|
||||
Logarithmic time complexity (O(log n)) often indicates that the algorithm halves the size of the input at each step. It's more efficient compared to linear time complexity. Binary search is a classic example of logarithmic time complexity where at every step, the algorithm breaks the list into half until it finds the desired element. As the size of the input increases, the growth of the time taken by an algorithm with logarithmic complexity grows slowly because it divides the problem into smaller parts in each step. |
||||
@ -0,0 +1,3 @@ |
||||
# Linear |
||||
|
||||
Linear time complexity, denoted as O(n), is one of the best possible algorithmic performance situations. An algorithm is said to have a linear time complexity when the running time increases at most linearly with the size of the input data. This means that if you double the size of the input, the running time will at most double as well. In an ideal situation, every single element in the data set should be viewed exactly once. Sorting algorithms such as counting sort and bucket sort have linear time complexity under certain conditions. |
||||
@ -0,0 +1,3 @@ |
||||
# Polynomial |
||||
|
||||
Polynomial time complexity, denoted as O(n^k), is a class of time complexity that represents the amount of time an algorithm takes to run as being proportional to the size of the input data raised to a constant power 'k'. Polynomial time complexity includes runtimes like O(n), O(n^2), O(n^3), etc. The value 'n' is a representation of the size of the input, while 'k' represents a constant. Algorithms running in polynomial time are considered to be reasonably efficient for small and medium-sized inputs, but can become impractical for large input sizes due to the rapid growth rate of function. |
||||
@ -0,0 +1,3 @@ |
||||
# Exponential |
||||
|
||||
Exponential time complexity is denoted as `O(2^n)`, where a growth in `n` leads to an exponential growth in the number of steps required to complete a task. It means that the time complexity will double with every additional element in the input set. This is seen in many recursive algorithms, where a problem is divided into two sub-problems of the same type. Examples of such algorithms include the naive recursive approach for the Fibonacci sequence or the Towers of Hanoi problem. Although exponential time complexity solutions are often simpler to implement, they are inefficient for larger input sizes. |
||||
@ -0,0 +1,3 @@ |
||||
# Factorial |
||||
|
||||
Factorial, often denoted as `n!`, is a mathematical operation. In the context of computer science and algorithm complexity, it represents an extremely high growth rate. This occurs because of the way a factorial is calculated: The product of all positive integers less than or equal to a non-negative integer `n`. Thus, if an algorithm has a complexity of O(n!), it means the running time increases factorially based on the size of the input data set. That is, for an input of size `n`, the algorithm does `n` * `(n-1)` * `(n-2)` * ... * `1` operations. O(n!) is essentially the worst case scenario of complexity for an algorithm and is seen in brute-force search algorithms, such as the traveling salesman problem via brute-force. |
||||
@ -0,0 +1,13 @@ |
||||
# Common Runtimes |
||||
|
||||
Common runtimes are used to quantify the performance of an algorithm as the size of the input data increases. They are usually expressed in Big O notation such as: |
||||
|
||||
- **O(1)**: Constant time complexity, the algorithm will always execute in the same time regardless of the size of the input data set. |
||||
- **O(N)**: Linear time complexity, the running time increases linearly with the size of the input data. |
||||
- **O(log N)**: Logarithmic time complexity, the running time increases logarithmically with the size of the input data set. |
||||
- **O(N log N)**: Quasilinear time complexity, slightly worse than linear but better than polynomial. |
||||
- **O(N^2)**: Quadratic time complexity, the running time increases quadratically with the size of the input data. |
||||
- **O(N^3)**: Cubic time complexity, the running time increases cubically with the size of the input. |
||||
- **O(2^N)**, **O(N!)**: Exponential and factorial time complexities respectively, the running time grows very quickly with the size of the input. |
||||
|
||||
Each of these represent different classes of algorithms and the increase in their running time as the size of input increases. Algorithms with lesser time complexity are generally preferred as they scale better with larger input sizes. |
||||
@ -0,0 +1,3 @@ |
||||
# Big O Notation |
||||
|
||||
"Big O" notation, officially known as O-notation, is used in computer science to describe the performance or complexity of an algorithm. Specifically, it provides an upper bound on the time complexity, describing the worst-case scenario. Thus, it gives an upper limit on the time taken for an algorithm to complete based on the size of the input. The notation is expressed as O(f(n)), where f(n) is a function that measures the largest count of steps that an algorithm could possibly take to solve a problem of size n. For instance, O(n) denotes a linear relationship between the time taken and the input size, while O(1) signifies constant time complexity, i.e., the time taken is independent of input size. Remember, Big O notation is only an approximation meant to describe the scaling of the algorithm and not the exact time taken. |
||||
@ -0,0 +1,3 @@ |
||||
# Big-θ Notation |
||||
|
||||
Big Theta \(\Theta\) notation is used in computer science to describe an asymptotic tight bound on a function. This essentially means it provides both an upper and lower bound for a function. When we say a function f(n) is \(\Theta(g(n))\), we mean that the growth rate of f(n) is both bounded above and below by the function g(n) after a certain point. This is more precise than Big O and Big Omega notation, which provide only an upper and a lower bound, respectively. Big Theta notation tells us exactly how a function behaves for large input values. For example, if an algorithm has a time complexity of \(\Theta(n^2)\), it means the running time will increase quadratically with the input size. |
||||
@ -0,0 +1,3 @@ |
||||
# Big-Ω Notation |
||||
|
||||
The Big Omega (Ω) notation is used in computer science to describe an algorithm's lower bound. Essentially, it provides a worst-case analysis of an algorithm's efficiency, giving us a lower limit of the performance. If we say a function f(n) is Ω(g(n)), it means that from a certain point onwards (n0 for some constant n0), the value of g(n) is a lower bound on f(n). It implies that f(n) is at least as fast as g(n) past a certain threshold. This means that the algorithm won't perform more efficiently than the Ω time complexity suggests. |
||||
@ -0,0 +1,3 @@ |
||||
# Asymptotic Notation |
||||
|
||||
In computer science, **asymptotic notation** is used to describe the efficiency of algorithms for large inputs. It is the mathematical notation of the growth rate of an algorithm's time complexity. The most commonly used notations are *O-notation* (Big O), *Ω-notation* (Omega), and *Θ-notation* (Theta). Big O notation provides an upper bound of the complexity in the worst-case, giving an approximated maximum amount of time taken by an algorithm for any input. Omega notation provides a lower bound of the complexity in the best-case, whereas Theta notation defines a tight bound giving both the lower and upper bound. These notational systems allow for a comparison of the efficiency of algorithms without considering the effect of hardware or software related factors. |
||||
@ -0,0 +1,3 @@ |
||||
# Algorithmic Complexity |
||||
|
||||
"Algorithmic Complexity" refers to the computing resources needed by an algorithm to solve a problem. These computing resources can be the time taken for program execution (time complexity), or the space used in memory during its execution (space complexity). The aim is to minimize these resources, so an algorithm that takes less time and space is considered more efficient. Complexity is usually expressed using Big O notation, which describes the upper bound of time or space needs, and explains how they grow in relation to the input size. It's important to analyze and understand the algorithmic complexity to choose or design the most efficient algorithm for a specific use-case. |
||||
@ -0,0 +1,3 @@ |
||||
# Bubble Sort |
||||
|
||||
Bubble Sort is a simple sorting algorithm that works by repeatedly swapping the adjacent elements if they are in the wrong order. It gets its name because with each iteration the largest element "bubbles" up to its proper location. It continues this process of swapping until the entire list is sorted in ascending order. The main steps of the algorithm are: starting from the beginning of the list, compare every pair of adjacent items and swap them if they are in the wrong order, and then pass through the list until no more swaps are needed. However, despite being simple, Bubble Sort is not suited for large datasets as it has a worst-case and average time complexity of O(n²), where n is the number of items being sorted. |
||||
@ -0,0 +1,3 @@ |
||||
# Merge Sort |
||||
|
||||
__Merge sort__ is a type of sorting algorithm that follows the divide-and-conquer paradigm. It was invented by John von Neumann in 1945. This algorithm works by dividing an unsorted list into `n` partitions, each containing one element (a list of one element is considered sorted), then repeatedly merging partitions to produce new sorted lists until there is only 1 sorted list remaining. This resulting list is the fully sorted list. The process of dividing the list is done recursively until it hits the base case of a list with one item. Merge sort has a time complexity of `O(n log n)` for all cases (best, average and worst), which makes it highly efficient for large data sets. |
||||
@ -0,0 +1,3 @@ |
||||
# Insertion Sort |
||||
|
||||
Insertion sort is a simple sorting algorithm that builds the final sorted array (or list) one item at a time. It's much less efficient on large lists than more advanced algorithms like quicksort, heapsort, or merge sort. Still, it provides several advantages such as it's easy to understand the algorithm, it performs well with small lists or lists that are already partially sorted and it can sort the list as it receives it. The algorithm iterates, consuming one input element each repetition and growing a sorted output list. At each iteration, it removes one element from the input data, finds the location it belongs within the sorted list and inserts it there. It repeats until no input elements remain. |
||||
@ -0,0 +1,3 @@ |
||||
# Quick Sort |
||||
|
||||
Quicksort, also known as partition-exchange sort, is an efficient, in-place sorting algorithm, which uses divide and conquer principles. It was developed by Tony Hoare in 1959. It operates by selecting a 'pivot' element from the array and partitioning the other elements into two sub-arrays, according to whether they are less than or greater than the pivot. The sub-arrays are then recursively sorted. This process continues until the base case is achieved, which is when the array or sub-array has zero or one element, hence is already sorted. Quicksort can have worst-case performance of O(n^2) if the pivot is the smallest or the largest element in the array, although this scenario is rare if the pivot is chosen randomly. The average case time complexity is O(n log n). |
||||
@ -0,0 +1,3 @@ |
||||
# Selection Sort |
||||
|
||||
Selection Sort is a simple and intuitive sorting algorithm. It works by dividing the array into two parts - sorted and unsorted. Initially, the sorted part is empty and the unsorted part contains all the elements. The algorithm repeatedly selects the smallest (or largest, if sorting in descending order) element from the unsorted part and moves that to the end of the sorted part. The process continues until the unsorted part becomes empty and the sorted part contains all the elements. Selection sort is not efficient on large lists, as its time complexity is O(n²) where n is the number of items. |
||||
@ -0,0 +1,3 @@ |
||||
# Heap Sort |
||||
|
||||
Heap Sort is an efficient, comparison-based sorting algorithm. It utilizes a datastructure known as a 'binary heap', and works by dividing its input into a sorted and an unsorted region, and iteratively shrinking the unsorted region by extracting the largest element and moving that to the sorted region. It's an in-place algorithm but not a stable sort. It involves building a Max-Heap, which is a specialized tree-based data structure, and then swapping the root node (maximum element) with the last node, reducing the size of heap by one and heapifying the root node. The maximum element is now at the end of the list and this step is repeated until all nodes are sorted. Heap Sort offers a good worst-case runtime of O(n log n), irrespective of the input data. |
||||
@ -0,0 +1,3 @@ |
||||
# Sorting Algorithms |
||||
|
||||
Sorting algorithms are used to rearrange a given array or list elements according to a comparison operator on the elements. The comparison operator is used to decide the new order of element in the respective data structure. For example, the numerical order is a commonly used sequence but a lexicographical order is also a commonly used sequence type. There are several types of sorting algorithms: quick sort, bubble sort, merge sort, insertion sort, selection sort, heap sort, radix sort, bucket sort among others. Each has its own properties and are suited to specific types of tasks and data. |
||||
@ -0,0 +1,3 @@ |
||||
# Linear Search |
||||
|
||||
Linear search is one of the simplest search algorithms. In this method, every element in an array is checked sequentially starting from the first until a match is found or all elements have been checked. It is also known as sequential search. It works on both sorted and unsorted lists, and does not need any preconditioned list for the operation. However, its efficiency is lesser as compared to other search algorithms since it checks all elements one by one. |
||||
@ -0,0 +1,3 @@ |
||||
# Binary Search |
||||
|
||||
`Binary Search` is a type of search algorithm that follows the divide and conquer strategy. It works on a sorted array by repeatedly dividing the search interval in half. Initially, the search space is the entire array and the target is compared with the middle element of the array. If they are not equal, the half in which the target cannot lie is eliminated and the search continues on the remaining half, again taking the middle element to compare to the target, and repeating this until the target is found. If the search ends with the remaining half being empty, the target is not in the array. Binary Search is log(n) as it cuts down the search space by half each step. |
||||
@ -0,0 +1,3 @@ |
||||
# Search Algorithms |
||||
|
||||
Search algorithms are techniques used for finding a specific item or group of items among a collection of data. They operate by checking each element in the dataset in order to locate the target selection. The primary types of search algorithms are linear search, binary search, depth-first search, and breadth-first search. Linear search scans each element in sequence, while binary search operates by splitting the dataset in half repeatedly until finding the desired element. Depth-first and breadth-first searches are both used with more intricate data structures like trees and graphs. The former explores the depth of a branch before the breadth, while the latter explores all neighboring nodes before proceeding to the nodes at the next level depth. |
||||
@ -0,0 +1,3 @@ |
||||
# Binary Trees |
||||
|
||||
A **Binary Tree** is a type of tree data structure in which each node has at most two children, referred to as the left child and the right child. This distinguishes it from trees in which nodes can have any number of children. A binary tree is further classified as a strictly binary tree if every non-leaf node in the tree has non-empty left and right child nodes. A binary tree is complete if all levels of the tree, except possibly the last, are fully filled, and all nodes are as left-justified as possible. Multiple algorithms and functions employ binary trees due to their suitable properties for mathematical operations and data organization. |
||||
@ -0,0 +1,3 @@ |
||||
# Binary Search Trees |
||||
|
||||
A **Binary Search Tree** (BST) is a type of binary tree data structure where each node carries a unique key (a value), and each key/node has up to two referenced sub-trees, the left and right child. The key feature of a BST is that every node on the right subtree must have a value greater than its parent node, while every node on the left subtree must have a value less than its parent node. This property must be true for all the nodes, not just the root. Due to this property, searching, insertion, and removal of a node in a BST perform quite fast, and the operations can be done in O(log n) time complexity, making it suitable for data-intensive operations. |
||||
@ -0,0 +1,3 @@ |
||||
# AVL Trees |
||||
|
||||
An **AVL tree** is a type of binary search tree that is self-balancing, which means the heights of the two child subtrees of any node in the tree differ by at most one. If at any point the difference becomes greater than one, rebalancing is done to restore the property. The tree is named after its inventors, G.M. Adelson-Velsky and E.M. Landis, who introduced it in 1962. Each node in an AVL tree carries extra information (its Balance Factor) which could be either -1, 0, or +1. AVL trees balance themselves by rotating sub-trees in different manners(named as Left-Left rotation, Right-Right rotation, Left-Right rotation, and Right-Left rotation) whenever an insert operation causes the balance factor to go beyond this range. |
||||
@ -0,0 +1,3 @@ |
||||
# B-Trees |
||||
|
||||
B-Tree is a self-balanced search tree data structure that maintains sorted data and allows for efficient insertion, deletion, and search operations. It is most commonly used in systems where read and write operations are performed on disk, such as databases and file systems. The main characteristic of a B-Tree is that all leaves are at the same level, and the internal nodes can store more than one key. Each node in a B-Tree contains a certain number of keys and pointers which navigate the tree. The keys act as separation values which divide its subtrees. For example, if a node contains the values [10,20,30] it has four children: the first contains values less than 10, the second contains values between 10 and 20, the third contains values between 20 and 30, and the fourth contains values greater than 30. |
||||
@ -0,0 +1,3 @@ |
||||
# In-Order Traversal |
||||
|
||||
In order traversal is a method for traversing binary trees. This method follows a specific order: Left Node, Root Node, then Right Node (L-N-R). Starting from the leftmost node of the tree, you first visit the left subtree, then the root node, and finally the right subtree. If the tree is a binary search tree, in order traversal will output the values of the nodes in the tree in ascending order. This traversal method is recursive in nature, as it requires each subtree to be visited in the exact same way. |
||||
@ -0,0 +1,3 @@ |
||||
# Pre-Order Traversal |
||||
|
||||
Pre Order Traversal is a very specific kind of tree traversal in data structures. In this method of traversal, the process starts from the root node, then proceeds to the left subtree, and finally to the right subtree. To put it concisely, the order of traversal is Root, Left, and Right (often abbreviated as R-L-R). This makes it particularly useful in scenarios where it's important to duplicate or clone a tree, or to get a prefix expression (Polish notation) of a binary expression tree. |
||||
@ -0,0 +1,3 @@ |
||||
# Post-Order Traversal |
||||
|
||||
Post Order Traversal is a technique used in Binary Tree structure where each node is processed after its child nodes. As the name suggests, it first traverses the left subtree, then the right subtree, and finally the root node. The process is recursively repeated for each subtree until the entire tree has been traversed. This traversal method is often used for calculations that require that all child nodes be processed before the parent, such as evaluating a mathematical expression represented in a tree structure. |
||||
@ -0,0 +1,3 @@ |
||||
# Tree Traversal |
||||
|
||||
Tree Traversal is a method of visiting all the nodes in a tree data structure. There are three main types of tree traversal, these include Preorder, Inorder, and Postorder. Preorder traversal visits the current node before its child nodes, Inorder traversal visits the left child, then the parent and right child, and Postorder traversal visits the children before their respective parents. There's also a level order traversal which visits nodes level by level. Depth First Search (DFS) and Breadth First Search (BFS) are two popular algorithms used for tree traversal. DFS involves exhaustive searches of nodes by going forward if possible and if it is not possible then by going back. BFS starts traversal from the root node and visits nodes in a level by level manner. |
||||
@ -0,0 +1,3 @@ |
||||
# Breadth First Search |
||||
|
||||
Breadth-First Search (BFS) is a searching algorithm that's used in tree or graph data structures. It starts from the root (the topmost node in the tree) and expands all neighboring nodes at the present depth prior to moving on to nodes at the next depth level. This technique uses a queue data structure to remember to explore the next vertex or node and every edge that leads to a vertex will be explored, which ensures the discovery of every vertex reachable from the source. BFS is complete in nature, which means if the searched node is in the tree, BFS is guaranteed to find it. |
||||
@ -0,0 +1,3 @@ |
||||
# Depth First Search |
||||
|
||||
Depth First Search (DFS) is an algorithm for traversing or searching tree or graph data structures. The process starts at the root (in the case of a tree) or an arbitrary node (in case of a graph), and explores as far as possible along each branch before retracing steps. Essentially, DFS is about diving deep into the tree/graph from a starting point, and when no more nodes are left to explore, it backtracks, moving up the tree/graph. This repeat until all nodes have been visited. This algorithm is often used in simulation of game states, solving puzzles and finding connected components in a graph. |
||||
@ -0,0 +1,3 @@ |
||||
# Search Algorithms |
||||
|
||||
Search algorithms in context of the tree data structure typically include breadth-first search (BFS) and depth-first search (DFS). BFS traverses the tree level by level starting from the root. It visits all nodes at current depth or level before proceeding to nodes at the next level. On the contrary, DFS travels toward the deepest node first, which means it travels as far as it can down one path before backtracking and exploring the next available path. DFS has three types - pre-order (root, left, right), in-order (left, root, right) and post-order (left, right, root). Another important search algorithm is the Binary Search that operates only on sorted dataset and effectively halves the search space after each comparison. It seeks the mid-point of the array and compares it against the target value. If the mid-point value is greater, it repeats the process on the left half and if the mid-point value is less, then on the right half. |
||||
@ -0,0 +1,3 @@ |
||||
# Tree Data Structures |
||||
|
||||
A **Tree data structure** is a type of non-linear, hierarchical data structure that consists of nodes connected by edges. It follows the parent-child relationship, with the top node being called the root. Each node in a tree can have child nodes and each of these child nodes has a single parent node. Nodes with same parents are known as siblings. Nodes without any children are referred to as leaves. Its structure allows the organization of data in a natural hierarchy. The simplification it provides in accessing, managing and manipulating data with complex relationships makes it a vital data structure in computer science. Implementations of the tree data structure are seen in databases, file systems, and HTML DOM. |
||||
@ -0,0 +1,3 @@ |
||||
# Directed Graph |
||||
|
||||
A **Directed Graph**, also known as a DiGraph, is a set of vertices and a collection of directed edges. Each directed edge has an initial vertex, also called the tail, and a terminal vertex, also known as the head. The directed edge is said to point from the tail to the head. To visualize this, think of a graph where the nodes are cities and the edges are one-way roads. Directed graphs are often used to represent relationships between objects where direction does matter, such as a sequence of events in a workflow. |
||||
@ -0,0 +1,3 @@ |
||||
# Undirected Graph |
||||
|
||||
An **Undirected Graph** is a type of graph in which the edges are not directed. That is, they do not point in any specific direction and are not ordered pairs. They cannot be referred to as originating or ending node, instead, they are endpoints of the edges. In this type of graph, the edges essentially represent a two-way relationship, in the sense that, a travel can be made back and forth between the two vertices without any restriction. Every edge of the undirected graph always connects two different vertices or nodes. |
||||
@ -0,0 +1,3 @@ |
||||
# Breadth First Search |
||||
|
||||
Breadth-First Search (BFS) is a searching algorithm used to traverse or search in data structures like a tree or a graph. The algorithm starts with a root node and visits the nodes in a level by level manner (i.e., visiting the ones nearest to the root first). It makes use of a queue data structure to store nodes not yet visited. A check is performed before nodes are put in the queue. This is to ensure same node is not visited twice. BFS can be used in multiple areas like finding shortest paths, serialized tree or in test case scenarios where all vertices are equally important. |
||||
@ -0,0 +1,3 @@ |
||||
# Depth First Search |
||||
|
||||
**Depth-First Search (DFS)** is an algorithm used for traversing or searching tree or graph data structures. The process starts at the root node (selecting some arbitrary node as the root in the case of a graph), and explores as far as possible along each branch before backtracking. It uses a last in, first out (LIFO) stack to remember to get the next vertex to start a search when a dead end occurs in any iteration. DFS has been used in a variety of applications including finding connected components, topological sorting, and finding articulation points (or cut vertices) in a graph. |
||||
@ -0,0 +1,3 @@ |
||||
# Search Algorithms |
||||
|
||||
Search algorithms are fundamental techniques used for exploring a graph. Two classical methods are **Depth-First Search** (DFS) and **Breadth-First Search** (BFS). **DFS** relies on a stack and the concept of backtracking. Starting from a given node, it explores as far down a path as possible before backtracking. **BFS**, on the other hand, uses a queue and visits all of a node's neighbors at one level before moving on to the next. For discovering the shortest path between two nodes, Dijkstra’s algorithm and the A* search algorithm are often used. **Dijkstra's algorithm** builds up a table that provides the shortest distances to each reachable node from a selected starting node. **A* search algorithm**, a modification of Dijkstra's algorithm, uses a heuristic to provide a best estimate of the path from the current node to the goal, thus often increasing the algorithm's efficiency. |
||||
@ -0,0 +1,3 @@ |
||||
# Dijkstra's Algorithm |
||||
|
||||
Dijkstra's algorithm is a popular method used in computing and graph theory for finding the shortest paths between nodes in a graph. Named after Dutch computer scientist Edsger W. Dijkstra, this algorithm works by visiting vertices in the graph starting from the object's starting point and gradually spreading out until the shortest path to the desired endpoint is known. This algorithm is applicable in such situation where all the edges are non-negative. Linear data structures such as stacks and queues are commonly used in the implementation of this algorithm. Although its worst-case time complexity appears to be high (O(|V|^2)), it runs significantly faster in practice. |
||||
@ -0,0 +1,3 @@ |
||||
# Bellman-Ford |
||||
|
||||
The **Bellman Ford algorithm** is a method used in graph theory for finding the shortest path between a single source vertex and all other vertices in a weighted graph. This algorithm is significant because it is capable of handling graphs with negative weight edges, unlike Dijkstra's algorithm. It follows a bottom-up approach, filling up the distance table gradually while relaxing edges. The algorithm gets its name from its developers, Richard Bellman and Lester Ford. However, it can lead to an infinite loop if there are negative weight cycles in the graph, which should be addressed separately using another check. |
||||
@ -0,0 +1,3 @@ |
||||
# Shortest Path Algos. |
||||
|
||||
Shortest Path Algorithms are a set of algorithms used in graph theory to find the shortest path between two vertices or nodes. The two most well-known algorithms are Dijkstra's Algorithm and the Bellman-Ford Algorithm. Dijkstra's Algorithm operates by visiting neighbors of the starting vertex and keeps a running tally of the shortest distance from the starting vertex to each visited vertex. This is repeated until all vertices have been visited and the shortest distances calculated. Bellman-Ford Algorithm, on the other hand, is capable of handling graphs with negative edges. It works by iteratively relaxing the graph edges and thereby finding the shortest paths to all vertices. |
||||
@ -0,0 +1,3 @@ |
||||
# Prim's Algorithm |
||||
|
||||
Prim's algorithm is a greedy algorithm that finds a minimum spanning tree for a weighted undirected graph. This means it finds a subset of the edges that forms a tree that includes every vertex, where the total weight of all the edges in the tree is minimized. The algorithm operates by building this tree one vertex at a time, from an arbitrary starting vertex, at each step adding the cheapest possible connection from the tree to another vertex. |
||||
@ -0,0 +1,3 @@ |
||||
# Kruskal's Algorithm |
||||
|
||||
Kruskal's algorithm is a popular procedure in computer science for finding minimum spanning trees in a graph, developed by Joseph Kruskal in 1956. The algorithm operates by sorting the edges of the graph by their weight in ascending order. Then, it loops through each, adding the edge to the spanning tree if it doesn't form a circuit with the edges already there. This process repeats until all the vertices in the graph are included in the tree. Kruskal's algorithm belongs to the group of Greedy Algorithms as it tries to find the local optimum at each stage with the hope of finding the global optimum. It has an overall time complexity of O(E log E) or O(E log V), where E is the number of edges and V is the number of vertices. |
||||
@ -0,0 +1,3 @@ |
||||
# Minimum Spanning Tree |
||||
|
||||
A **Minimum Spanning Tree (MST)** is a concept in graph theory where it represents a subset of the edges of a connected, undirected graph. This subset connects all the vertices together, without any cycles and with the minimum possible total edge weight. There are quite a few algorithms that can be used to find the MST of a graph such as Prim's, Kruskal's, and Boruvka's algorithm. The concept is important in network design, where the goal is to minimize the total length of the wires yet still connect all of the points. |
||||
@ -0,0 +1,3 @@ |
||||
# Graph Data Structure |
||||
|
||||
A **Graph Data Structure** consists of a set of vertices (or nodes) and edges where each edge connects a pair of vertices. It can be visualized as networks consisting of elements in interconnected various relationships. There are two major types of graphs: Directed and Undirected. In a directed graph, all the edges are unidirectional - they only go one way. On the other hand, in an undirected graph, the edges are not directed - they are bidirectional. Another concept important to graphs is the idea of 'Weighted' and 'Unweighted' graphs. In a weighted graph, each edge is assigned a weight or cost. Unweighted graphs don't have these extra edge information. Graphs have a diverse set of applications in computer science, from creating connections between web pages to modeling networks and much more. |
||||
@ -0,0 +1,3 @@ |
||||
# Trie |
||||
|
||||
A **Trie**, also called digital tree and sometimes radix tree or prefix tree, is a type of search tree that is used to store a dynamic set or associative array where the keys are usually strings. Unlike binary search trees, no node in the tree stores the key associated with that node; instead, its position in the tree defines the key with which it is associated. All the descendants of any one node have a common prefix of the string associated with that node, and the root is associated with the empty string. A 'trie' is thus a way to represent the 're**trie**val' of information and is a type of tree structure used for this purpose. Typical usage scenarios could be in storing a predictive text or autocomplete dictionary, such as found on your smartphone or search engine. |
||||
@ -0,0 +1,3 @@ |
||||
# Segment Trees |
||||
|
||||
A **Segment Tree** is a data structure designed for efficient processing of range queries and updates on array elements. In a situation where you have an array and you need to execute several types of queries including updating array elements and computing sum or minimum or maximum of elements in a given range, segment trees could be a great choice. The tree itself is a height-balanced binary tree and is filled with data from the input array. The leaves of the Segment Tree contain the array elements, while the internal nodes store information needed for processing the query, often the sum, minimum, or maximum of the elements represented by their child nodes. Efficient implementation of segment trees can achieve query and update operations in logarithmic time. |
||||
@ -0,0 +1,3 @@ |
||||
# Fenwick Trees |
||||
|
||||
Fenwick Trees, also known as Binary Indexed Trees, are data structures that can efficiently support the operation of updating elements and calculating prefix sums in a table of numbers. This makes it particularly useful in situations where the table gets updated often and different kinds of queries (such as sum of elements) need to be answered fast. A Fenwick Tree typically takes O(log n) time for both updation and query operations, which is more efficient than an array or a segment tree. It achieves this efficiency by storing partial sum information in the array. This allows for efficient calculation of sum ranges, with the operation of adding an element and getting the sum of a range both achieve in O(log n) time. |
||||
@ -0,0 +1,3 @@ |
||||
# Disjoint Set (Union-Find) |
||||
|
||||
A **disjoint-set** data structure, also called a union-find data structure or merge-find set, is a data structure that tracks a partition of a set into numerous non-overlapping subsets. It provides near-constant-time operations to add new sets, to merge existing sets, and to determine whether elements are in the same set. The underlying algorithm uses two main techniques, `Union by Rank` and `Path Compression`, to achieve the efficient time complexity. Each element is represented as a node, and each group of disjoint sets forms a tree structure. Disjoint sets are useful in multitude of graph algorithms like Kruskal’s algorithm and many more. |
||||
@ -0,0 +1,3 @@ |
||||
# Suffix Trees and Arrays |
||||
|
||||
**Suffix Trees and Arrays** are advanced data structures used primarily for string manipulation and searches. A **Suffix Tree** is a compressed trie containing all the suffixes of a given text as their keys and positions as their values. On the other hand, a **Suffix Array** is a sorted array of all possible suffixes of a given text. Both these data structures provide an efficient way to store and search substrings in a text, but differ in terms of space complexity and time complexity. |
||||
@ -0,0 +1,3 @@ |
||||
# Advanced Data Structures |
||||
|
||||
Advanced data structures are an integral part of advanced programming. They include structures such as Binary Search Trees (BST), Balanced trees like AVL Trees, Red-Black Trees, Heap, Disjoint Data Set, Trie, Suffix Array, Suffix tree and others. BST is a node-based data structure where each node contains a key, a pointer to left child and a pointer to right child. AVL and Red-Black trees are self-balancing binary search trees. Disjoint set data structure supports union and find operations making them useful in computer vision for segmentation. Trie is an ordered tree structure used for faster retrievals, while Suffix Array and Suffix tree are data structures used in pattern matching algorithms. These structures offer an efficient way of manipulating and storing data. |
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in new issue