Coding Challenges

This repository saves my solutions to the following different coding challenges:

• Cracking The Coding Interview (CTCI)
• Interviewing.io
• Leetcode
• Project Euler

The solutions are written in Golang.

Format

1. Problem from one coding challenge is created as an Issue. The issue has relevant Labels and a description of the problem.

2. Solution to a Issue (coding problem) is submitted as a Pull Request. The solution also has an associated _test file with test cases to verify the solution.

3. The solution file will be named to reflect problem name, e.g. problem_001.go, and associated test file will have the same name and end with _test suffix, e.g. problem_001_test.go.

4. The solution file should contain a brute force solution and an improved solution. Write the time and space complexities as comments about the function. The test cases should test both solutions.

Solution Template

/*
[Issue title]
*/

package challenge

// Time complexity:     O(n^2)
// Space complexity:    O(1)
func BruteForceSolution() {
    // Implementation here
    return answer
}

// Time complexity:     O(n)
// Space complexity:    O(n)
func ImprovedSolution() {
    // Implementation here
    return answer
}

Set up

The repository is organised into folders for the different challenges (projects) and each Issue created will belong to one of the challenges, i.e. One Issue = One Problem.

Once a coding solution is verified, it is merged and placed in the relevant folder - together with the associated test file. The test cases are run in a GitHub Action and the workflow is triggered when a pull request is opened or updated.