# BibliotecaDev: a Portuguese-language index of programming books > An MIT-licensed repository that organises programming books into eleven categories, pairing a store link with a direct PDF link and an edition-language badge for every title. **KAYOKG/BibliotecaDev** — 📚 Biblioteca de livros essenciais da área da programação. (Confira o meu novo projeto `SendScriptWhatsapp`) - Repository: https://github.com/KAYOKG/BibliotecaDev - Website: https://github.com/KAYOKG/SendScriptWhatsapp-Global - Stars: 15,159 · Forks: 2,393 - Language: Unknown - License: MIT - Published: 2026-10-07 · Updated: 2026-10-07 · Language: en - Canonical page: https://hysenlabs.com/projects/kayokg-bibliotecadev ## What this repository is, and what it is not BibliotecaDev holds no code. GitHub reports no primary language for it, because the payload is a directory of PDF files and a Markdown file that describes them. That absence is the first useful fact about the project: it is an index, maintained in the way an index is maintained, by someone deciding what belongs in a category and adding a row. The repository description is in Portuguese and reads as a library of essential books for the programming field, which is an accurate description of a collection rather than a library in the code sense. The topic list is more revealing, and it contains a small inconsistency worth naming: alongside `pdf`, `leitura`, `livro` and two Portuguese spellings of the name, there is an `english` tag. The tag reflects that some editions in the collection are English, which is also what the language column in the tables is for. It does not make the repository bilingual. The homepage field points somewhere unexpected. It resolves to `SendScriptWhatsapp-Global`, a different project by the same owner, and the description promotes it too. So the useful mental model is that this is a personal curation project by one maintainer, and part of its traffic flows toward something else the maintainer built. ## The eleven-category map at the top of the file The first thing in the README is a summary table called Sumário, and it is the part that makes the repository worth using. Each row pairs a category anchor with a one-sentence description of what belongs under it, so you can decide where to look without opening any of the sections. The categories run: algorithms and data structures, software architecture, career and skills, data science, agile development, DevOps, company and organisational culture, interview preparation, leadership and team management, advanced agile methodologies, and software patterns and design. Two of those are worth distinguishing, because they sit next to each other and cover different ground. Desenvolvimento Agile is framed around implementing agile practices for frequent delivery and code quality, while Metodologias Agile Avancadas is framed around the named frameworks themselves, with Scrum, Kanban and Lean called out by name. The career-oriented categories are unusually well represented for a technical library: interview preparation has its own section, and there are two separate sections on managing people, one on leading teams and one on company culture. Every description in that table is written in Portuguese, which is a practical limit on who gets value from the map. A reader who cannot read Portuguese still gets the section titles from the category list and the anchors, but they lose the guidance sentences that explain what each section actually collects. ## How a single row is assembled The section tables share one shape, with five columns: LIVRO, NOME, AUTOR, STATUS and IDIOMA. The first column is a cover image pointing at an SVG held in the repository's own `.github/img` directory, which means the covers render in GitHub without a third-party image host and without the repository growing a media library of its own. The second column is the title, and it is where the two link types live. In the algorithms table, the cover image for Cormen points at a product page on the Brazilian Amazon storefront, while the title text points at the PDF inside `LivrosDev/` on GitHub. Aurelio Marinho's regular expressions book is the exception that proves the pattern: its cover link is a short `amzn.to` redirect rather than a full store URL, because that row is older. So a reader gets both routes to the same book, a purchase route and a download route, which is why the two-link arrangement is not redundant. The last two columns are image badges served from a user-images host rather than from the repository, and they encode different things. STATUS uses one badge consistently across the table. IDIOMA uses two distinct badge images: most rows share one, and the English edition of J. Clark Scott's But How Do It Know gets the other. That is the column to read first if you care about which language you will actually be reading, because the NOME column tells you the edition title but the badge tells you the file language. ## The algorithms section as the worked example The algorithms and data structures section is the one to read closely, because it shows the collection's taste. Five titles appear there, and they span levels deliberately. Thomas Cormen's Algoritmos: Teoria e Pratica is the reference volume, the one you keep on a shelf rather than finish. J. Clark Scott's But How Do It Know is the opposite, a gentle introduction to how computers work, and it is also the one entry carrying the English edition badge. Aditya Y. Bhargava's Entendendo Algoritmos is the illustrated middle, popular with readers who bounce off Cormen's density. The remaining two show the collection reaching past theory. Aurelio Marinho's Expressoes Regulares: uma abordagem divertida treats a narrow topic at book length, which is a fair criticism of technical publishing generally and a reasonable thing to want on a shelf. The Casa do Codigo data science title, subtitled around machine learning algorithms and analysis methods, is the odd placement: it sits under algorithms and data structures rather than under the data science category, and it is the clearest example of a row that could reasonably live in either place. Category boundaries in a hand-maintained index are suggestions, not rules. The architecture section begins with Robert Martin's Arquitetura Limpa, the craftsman guide to structure and design, which is about as uncontroversial a first entry as a software architecture shelf can have. ## The maintenance profile tells you how to read it There are no releases, no version tags and no changelog, and for a repository whose content is a set of files that either exist or do not, that is the correct shape rather than a gap. What the numbers do say is worth reading carefully. The repository has 14,842 stars and 2,363 forks, with 3 open issues. A fork count at roughly one sixth of the star count is unusually high for a project that produces no buildable artifact, and the reason is structural: forking is how people version their own copy of a list, and a curated index is exactly the kind of thing people want to specialise for their own stack or their own language. Three open issues against that traffic means very little is being triaged. The last push was 2026-05-03, which is inside the last six months, so the repository is not abandoned, but a repository that receives this much attention and this few issues is a repository people bookmark rather than report to. Read it as a maintained snapshot with a long shelf life. The file tree reinforces that reading. Alongside `.github/`, `README.md`, `.gitignore` and `LICENSE.md` there are three community files: `SECURITY.md`, `code_of_conduct.md` and `contributing.md`. Those are boilerplate for many repositories and meaningful for this one, because a table like this does invite pull requests, and having a stated path for adding a book is better than having an untracked comment thread. ## The licence question, stated plainly The repository is MIT licensed, and the distinction that matters is between the repository and its contents. The MIT file covers the files the maintainer authored or holds rights to: the README, the cover SVGs under `.github/img`, the configuration files. It does not grant rights over Thomas Cormen's book, Aditya Y. Bhargava's book, or any of the other titles in the tables, because copyright in those works sits with their authors and publishers. This is the ordinary situation for a link index, and it is worth stating rather than glossing because the two facts get conflated. The MIT label is a real signal about the index. It is not a signal about the PDFs in `LivrosDev/`, and it is not an invitation to treat them as freely licensed. The store link in each row exists for a reason, and it is the route to take for a title you intend to keep. Practical advice follows from the structure. Use the summary table to choose a category, use the cover and the language badge to decide between editions, then decide route deliberately: the PDF for a quick look, the store when you want a properly typeset, legally licensed copy. And if you want the collection in your own language or your own stack, the 2,363 existing forks suggest you would not be the first, and the contributing file is where that conversation belongs. ## Conclusion BibliotecaDev is a catalogue, not a tool, and reading it that way sets the right expectation. What it does well is organisation: eleven named categories, one table shape repeated for each, and enough metadata per row that you can tell at a glance which edition and which format you are about to get. What it cannot do is replace a publisher, and the MIT licence on the repository should not be read as applying to the books themselves. Come to it when you already know roughly what you want to learn and want the shortlist in one place instead of five browser tabs. Follow the summary table at the top rather than scrolling, because the anchor structure is what makes the repository usable, and use the store link when a title matters enough to buy properly. ## FAQ ### What is BibliotecaDev? An MIT-licensed GitHub repository that indexes programming books, mostly Portuguese editions, organised into categories. It contains no code. The content is a README of category tables plus a `LivrosDev/` directory of PDF files and a set of cover images under `.github/img`. ### What categories does the index cover? Eleven, listed in the summary table at the top of the README: algorithms and data structures, software architecture, career and skills, data science, agile development, DevOps, company and organisational culture, interview preparation, leadership and team management, advanced agile methodologies, and software patterns and design. ### How do I tell which edition language a PDF is? Read the IDIOMA column, which uses two different badge images. Most rows share one badge and the English edition of J. Clark Scott's But How Do It Know carries the other. The title text sometimes hints at it too, but the badge is the column designed for the job. ### Can I use this if I do not read Portuguese? Partly. The category table, the section headings and the anchor links are readable, and the English edition badges tell you which files are in English, but every category description sentence and every book title description in the file is written in Portuguese. Expect to read the structure and infer the contents rather than read the guidance. ### Does the MIT licence cover the books? No. The MIT file covers the repository's own files, such as the README and the cover SVGs. Copyright in the listed books stays with their authors and publishers, which is why each row also carries a store link alongside the PDF link. ## Sources - [Issues](https://github.com/KAYOKG/BibliotecaDev/issues) - [KAYOKG/BibliotecaDev on GitHub](https://github.com/KAYOKG/BibliotecaDev) - [License: MIT](https://github.com/KAYOKG/BibliotecaDev/blob/main/LICENSE) - [Project website](https://github.com/KAYOKG/SendScriptWhatsapp-Global) - [README](https://github.com/KAYOKG/BibliotecaDev/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/kayokg-bibliotecadev