https://github.com/psudo-dev/codewars-typescript
Repository dedicated to storing my TypeScript solutions for Codewars challenges (Katas). This repo serves as a personal archive for practicing problem-solving, mastering native TypeScript array methods, and sharpening algorithmic thinking.
https://github.com/psudo-dev/codewars-typescript
Last synced: 4 days ago
JSON representation
Repository dedicated to storing my TypeScript solutions for Codewars challenges (Katas). This repo serves as a personal archive for practicing problem-solving, mastering native TypeScript array methods, and sharpening algorithmic thinking.
- Host: GitHub
- URL: https://github.com/psudo-dev/codewars-typescript
- Owner: psudo-dev
- License: mit
- Created: 2026-05-26T17:07:53.000Z (6 days ago)
- Default Branch: main
- Last Pushed: 2026-05-26T18:23:41.000Z (6 days ago)
- Last Synced: 2026-05-26T20:14:51.449Z (6 days ago)
- Language: TypeScript
- Size: 2.93 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Codewars TypeScript Solutions
Welcome to my personal archive of Codewars challenges.
While I believe that building real-world projects is the ultimate way to demonstrate software engineering capabilities, I maintain this repository to sharpen my problem-solving skills, master TypeScript's type system, and build muscle memory for algorithmic efficiency and clean code.
## Repository Purpose
- **Language Mastery:** Deepening my understanding of TypeScript features, strict typing, interfaces, and advanced utility types.
- **Algorithmic Thinking:** Training my brain to break down complex logic into small, performant, and readable steps.
- **Continuous Learning:** Keeping my coding skills sharp with micro-challenges (Katas).
## Approach
I'm not rushing to get to the finish line or something like that, this is a learning tool first and foremost, I'm still getting to know the platform and its community, how it's organized, how it works, and how to best use it to learn and grow as a developer. If I find it's not adding value, I'll probably stop and focus my time on something else, but for now, I'll take the most out of it and have fun with it.
## Project Structure
```text
codewars-typescript/
├── 8-kyu/
│ ├── name-of-exercise/
│ │ ├── README.md
│ │ └── solution.ts
│ └── name-of-exercise/
│ ├── README.md
│ ├── solution.ts
│ └── solution-refactored.ts ← when I revisited it
├── 7-kyu/
│ └── ...
└── README.md
```
### Each kata folder contains
- **`README.md`** — the original problem statement
- **`solution.ts`** — my solution (sometimes with inline comments)
- **`solution-refactored.ts`** — if I revisited after seeing other approaches or learning something new
## Coding Philosophy
When solving these Katas, my priority is readability and maintainability over cleverness. In production, code is read far more often than it is written. So I won't be doing one-liners or using obscure language features just for the sake of it - unless, maybe, I find it really interesting or worth it, but as an alternative solution.
## Kyu reference
Codewars ranks problems from **8 kyu** (easiest) to **1 kyu** (hardest). I'm starting at 8–7 kyu to build confidence with the platform and TypeScript syntax, then moving up as it makes sense.
| Rank | Rough equivalent |
| ------- | ---------------------------- |
| 8–7 kyu | Syntax, basics, simple logic |
| 6–5 kyu | Algorithms, data structures |
| 4–3 kyu | Complex problem solving |
| 2–1 kyu | Advanced, research-level |
## My Codewars Profile
Feel free to view my progress and badges directly on my Codewars profile:
[@psudo-dev](https://www.codewars.com/users/psudo-dev)