https://github.com/seandewar/challenge-solutions

My solutions for programming puzzles from various websites.
https://github.com/seandewar/challenge-solutions

advent-of-code hackerrank hackerrank-solutions interviewbit-solutions leetcode leetcode-solutions practice-exercises protohackers-solutions revision solutions

Last synced: 20 days ago
JSON representation

My solutions for programming puzzles from various websites.

• Host: GitHub
• URL: https://github.com/seandewar/challenge-solutions
• Owner: seandewar
• Created: 2019-10-10T21:12:31.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2024-10-22T01:14:25.000Z (22 days ago)
• Last Synced: 2024-10-22T11:08:56.286Z (21 days ago)
• Topics: advent-of-code, hackerrank, hackerrank-solutions, interviewbit-solutions, leetcode, leetcode-solutions, practice-exercises, protohackers-solutions, revision, solutions
• Language: C
• Homepage: https://leetcode.com/seandewar/
• Size: 1.34 MB
• Stars: 3
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Sean's Challenge Solutions Repository

This is my personal repository for solutions to programming puzzles from various

websites, including:

- [LeetCode](https://leetcode.com)

- [Advent of Code](https://adventofcode.com)

- [HackerRank](https://www.hackerrank.com)

- [Protohackers](https://protohackers.com)

- [InterviewBit](https://www.interviewbit.com)

- [TUHH's System Call Advent Calendar](https://osg.tuhh.de/Advent)

I try to annotate most Leetcode solutions with a link to their respective

questions, comments regarding their time & space complexities and other notes,

while also sometimes providing alternative solutions you may want to consider.

The directory structure is pretty straightforward, with solutions grouped in

directories indicating their respective question's difficulty (usually "easy",

"medium" or "hard", as ranked by the website the question is from).

You may see my programming style change every-so-often (e.g widespread use of

brace initialization syntax in some C++ solutions), as this is a good place to

experiment.