I bought the book, and so far it's a good overview of big-O notation. However, I'm halfway through the first chapter and I've already found a handful of typos. I commend OP for taking the risk and self-publishing but please have someone proofread your work before you start selling it!
Thanks for reading the book and commenting here! Could you please open an issue with the typos https://github.com/amejiarosario/dsa.js-data-structures-algo... or create a pull request with fixes? I'll be more than happy to go over them and fix/merge them. I've spent weeks proofreading the material, but apparently, some slipped through the cracks. Thanks again for taking the time.
Sorry, but since the book itself isn't open source, I'm not going to do your editing for free. There's plenty of paid editor sites out there. If you give me co-author credit and a slice of sales, though...
The book is open-source! All the book's chapters and exercises are open to anybody to see and edit. E.g. First chapter is here: https://github.com/amejiarosario/dsa.js-data-structures-algo.... The offline formats (PDF, ePub, Mobi) are there for convenience (and to solve the limited support Github has for asciidoc's `include` directives) but all the text/code is open.
I think one of the point of using Markdown is that you can read it unformatted. Using `<details>` & `<summary>` kinda breaks that mentality don't you think?
Small plug-- this is what I tried to do with https://algodaily.com - going from the easiest algorithms (like "Reverse a String") all the way to Union-Find, while sprinkling implementations of BST, graphs, etc. along the way.
I just tried signing up but I'm getting an error. "The change you wanted was rejected. Maybe you tried to change something you didn't have access to. If you are the application owner check the logs for more information."
Fyi if you're going to handle any kind of account signup you should be running in TLS/SSL. I know this is just algo practice but these are best security practices.
Also, I don't see how this is any different from leetcode/hackrank etc. You just support less languages. Your first question is a "island" style problem which isn't a CS algo question, it's just a brainteaser like leetcode often gives you.
1 - It does have TLS/SSL, just changed the referring link to https and redirecting all http to https
2 - That's a fair assessment, check out https://algodaily.com/challenges/validate-palindrome for a sense of how it differs: a) the step-through visualization button helps you know what's going on at each step, b) the trivia style questions help you "piece together" the solution before answering it fully, and c) each walkthrough walks you through the actual solution step by step, in plain English.
Agreed. Sites like HackerRank are great for learning test taking but are not optimized for learning the underlying material. Would like to see modern human language learning techniques applied to small data structures and algorithms exercises.
Off Topic: GitHub has so many navigation bars nowadays. Just look at the incorrect overflow caused by the overlapping project name and the buttons on the side: https://i.imgur.com/iXCgXYH.png . I don’t need to be an expert in UI/UX to know the GitHub UI is cluttered with an unnecessary amount of buttons. I can predict a redesign in less than a year or so, mark my words.
The title used to be "Show HN: I made this repo to practice Algorithms in JavaScript", which the GP commented on. It has since been changed to "Show HN: Data Structures and Algorithms in JavaScript".
