https://github.com/fabio-miguel/data-structures-algorithms-challenges

A collection of data-structures I have built using JavaScript. Also includes a collection of mini katas completed, using TDD, related to each data structure. Big O was considered per kata.
https://github.com/fabio-miguel/data-structures-algorithms-challenges

data-structures-and-algorithms javascript katas nodejs tdd typescript

Last synced: about 1 month ago
JSON representation

A collection of data-structures I have built using JavaScript. Also includes a collection of mini katas completed, using TDD, related to each data structure. Big O was considered per kata.

• Host: GitHub
• URL: https://github.com/fabio-miguel/data-structures-algorithms-challenges
• Owner: fabio-miguel
• Created: 2024-01-18T14:53:58.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-03-27T09:07:53.000Z (11 months ago)
• Last Synced: 2024-11-08T12:07:49.084Z (3 months ago)
• Topics: data-structures-and-algorithms, javascript, katas, nodejs, tdd, typescript
• Language: JavaScript
• Homepage:
• Size: 83 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# data-structures-algroithms-challanges-tdd

# About

**SPOILER**

If you haven't completed the Katas before and you don't want the solutions, don't view the katas in the katas folder.

This repository is a collection of data structures built with JavaScript and Katas built with TDD. I have another folder with katas, but the katas in this repo are those commonly associated with data structures and common interview questions. My reasoning is... there is a reason these challenges are common interview tasks and are likely used to test knowledge of data structures and algorithms. Again, a reason why they have been organised into this repository. Educational notes and reflective thoughts are included, which may or may not be useful to you, but act as a reference point for mylsef. 

# Katas Folder

The katas have all been completed, while attempting to use strict TDD. Each test was used to drive an implementation. Tests are designed to read almost like a specification. Can you read the tests and understand what the algorithm does. This was the goal and often an overlooked aspect of TDD.