GitHub Hot Board

GitHub Hot Board · Archiwum repozytorium

egonSchiele/grokking_algorithms

Code for the book Grokking Algorithms (https://www.amazon.com/dp/1633438538) (Opis pochodzi z samego repozytorium.)

Dane na October 25egonSchiele

Najlepsze miejsce

#435

Mistrzowie · JavaScript wg języka

14K

Wszystkich gwiazdek

4.1K

Wszystkich forków

0

Dni w rankingach (30 d)

Status projektuLicencja: NOASSERTIONOstatni push: April 12Otwarte issues (z PR): 6

Zbierane od 2026-10-25; nieznane = jeszcze nie zebrane

Wklej odznakę do swojego README · egonSchiele/grokking_algorithms[![Wklej odznakę do swojego README](https://git.vaiox.xyz/api/badge/egonSchiele/grokking_algorithms.svg)](https://git.vaiox.xyz/pl/repo/egonSchiele/grokking_algorithms)
<a href="https://git.vaiox.xyz/pl/repo/egonSchiele/grokking_algorithms"><img src="https://git.vaiox.xyz/api/badge/egonSchiele/grokking_algorithms.svg" alt="Wklej odznakę do swojego README" height="20"></a>

Dokumentacja projektu

Grokking Algorithms

This is the code in my book Grokking Algorithms.

Check out Python Tutor, a great website that guides you through Python code line by line.

Errata

Here's the errata page.

Images

This repository contains every image in Grokking Algorithms in high resolution. These images are available for non-commercial use. If you use an image, please add "copyright Manning Publications, drawn by adit.io". You are welcome to use these images in any non-commercial materials (i.e. teaching materials, presentations, etc.)

Contributing

Thanks for wanting to contribute to this repo!

If you have found a mistake in the book or have a question, please email me as that will be the best way to get a response. My email is listed on my website, adit.io. If you would like to make a change, please go ahead and open a PR with your suggested change. I am quicker at responding to those than I am to issues.

It takes me a long time to respond to PRs. It's something I'm trying to get better at, but I apologize in advance for how long it will take. I will eventually get to it.

The contributions that are most useful are:

  • fixing errors in existing code
  • adding examples to new languages
  • modernizing code as the language evolves
  • making code easier to read.

I'm less likely to merge code that involves stylistic changes, and I'm very unlikely to merge PRs that add complex optimizations, as the main purpose of this repo is to have easy to read examples that help people understand concepts.

Thanks for contributing and I hope you're enjoying the book!

Aktualne miejsca

Przebieg z 30 dni

Brak wpisów w ostatnich 30 dniach.

← Powrót do rankingów