doocs/technical-books: A Curated Reading List of Engineering Books for Developers
😆 国内外互联网技术大牛们都写了哪些书籍:计算机基础、网络、前端、后端、数据库、架构、大数据、深度学习...
At a glance
- What is it?
- doocs/technical-books is a CC-BY-SA-4.0 curated list of recommended engineering books covering computer systems, algorithms, networking, frontend, backend, databases, architecture, big data, and deep learning, hosted as a VitePress site at book.doocs.org. The last push was on 2026-09-12.
- Who is it for?
- doocs/technical-books is a useful reference for developers looking for structured reading recommendations across the major areas of computer science and software engineering, particularly those who prefer to buy and read physical or digital books rather than rely on free online tutorials. It is best suited to readers who can access Chinese book retailers, since many titles link to JD.com and Dangdang.
- Can I use it commercially?
- Yes, with credit. CC-BY-SA-4.0 allows commercial use as long as you credit the authors and indicate what you changed. It is written for creative content, so check how it applies to any code.
- Is it still maintained?
- Yes. The repository last received commits 6 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 29, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What doocs/technical-books is and how it works
doocs/technical-books is a Markdown-based reading list maintained by the Doocs open-source organization. It collects book recommendations across the major areas of software engineering and computer science: computer systems fundamentals, networking, frontend development, backend development, databases, software architecture, big data, and deep learning. Each entry in the list includes a title that links to a purchase page, the author or authors, and a short abstract describing what the book covers and who it is for.
The repository is not a download archive or a link farm to pirated PDFs. The README explicitly encourages purchasing original books to support their authors. Each book title links to a JD.com or Dangdang purchase page. The focus is discovery: the list exists to help a developer who does not know which books to read identify which ones are worth their time, based on curated descriptions.
The repository is hosted as a website at book.doocs.org, which provides a browsable and searchable interface to the full list. The site was built with VitePress and deployed to Cloudflare Workers. The last push to the repository was on 2026-09-12, and development is ongoing.
Repository structure: Markdown tables in the README and the docs/ directory
The core content lives in the README.md at the repository root, organized as Markdown tables grouped by subject area. Each table has three columns: a numbered entry, a book title with a purchase link, and a combined author and abstract column that provides the author's name in parentheses alongside a description of the book's scope and audience.
The GitHub description mentions eight topic areas: computer basics, networking, frontend, backend, database, architecture, big data, and deep learning. The README organizes these as distinct table sections. A developer looking for recommendations in a specific area can navigate directly to the relevant table without reading the entire document.
The docs/ directory holds the VitePress source files that build the site. The top-level entries also include a worker.ts file and wrangler.toml for Cloudflare Workers deployment, and a tsconfig.json for TypeScript checking of the worker code. The package.json manages the build toolchain with [email protected] and requires Node.js 22.12.0 or later.
The computer systems and algorithms selections
The computer systems and algorithms section in the README shows nine entries, each with an author credit and a brief description. The selections span foundational computer science topics.
Charles Petzold's "Code: The Hidden Language of Computer Hardware and Software" (2012 edition) is described as explaining how computers work in an accessible way for both experienced engineers and newcomers. Eric Evans's "Domain-Driven Design" (2016 revised edition) is recommended for its approach to software complexity through domain modeling. The entry for "Computer Systems: A Programmer's Perspective" notes that it covers computer software and hardware theory together in a classic textbook format.
For algorithms, Sedgewick and Wayne's "Algorithms, 4th Edition" is described as a more practical and readable algorithms text with Java code examples, suitable for beginners. Remzi and Andrea Arpaci-Dusseau's "Operating Systems: Three Easy Pieces" is noted for its conversational style and its organization around virtualization, concurrency, and persistence. The section also includes both the Dragon Book (Aho et al., Compilers: Principles, Techniques, and Tools) and the Tiger Book (Appel, Modern Compiler Implementation in C), along with Cormen et al.'s "Introduction to Algorithms."
The networking section includes four entries: Ueno Osamu's "Illustrated HTTP," Stevens's "TCP/IP Illustrated, Volume 1," Kurose and Ross's "Computer Networking: A Top-Down Approach," and a Chinese-authored networking textbook by Xie Jun and Xie Xiren.
Running the site locally and deploying to Cloudflare Workers
The repository includes the full VitePress build toolchain. To start a local development server:
pnpm run docs:devThis runs `vitepress dev docs` and serves the site locally at a VitePress-assigned port. To build the static site for production:
pnpm run docs:buildThe Cloudflare Workers deployment runs through wrangler. The deploy script defined in package.json builds the site and then deploys:
pnpm run deploy:cfThis expands to `pnpm run docs:build && wrangler deploy`. The wrangler.toml at the repository root holds the Cloudflare Workers configuration including the worker script entry point and the deployment settings.
The vitepress-plugin-comment-with-giscus dependency adds Giscus comment integration to the site. Giscus is a GitHub Discussions-based comment system, which means that comments on the book.doocs.org site are stored as GitHub Discussions on the repository. This connects the online reading experience back to the GitHub repository without requiring a separate comment backend.
Contributing: the Discussions path and pull requests
The README documents two contribution paths. The primary path for book recommendations is GitHub Discussions: the README links to Discussion #30 for new suggestions. This allows the community to discuss a recommendation before it is added to the list, which avoids merging books that other contributors find redundant or unsuitable.
The secondary path is a direct pull request. A contributor who wants to add an entry can edit the README or the docs/ source files and submit a PR. The README does not document a specific format requirement beyond what is visible in the existing table structure: a title with a purchase link, an author credit, and a one-paragraph abstract.
The CC-BY-SA-4.0 license applies to the content of the repository. This license permits reuse and redistribution of the curated list, including in adapted form, provided that the attribution and share-alike requirements are met. The license does not restrict how many times a book can be recommended or limit the list to any specific subject area, but it does require that derivative works use the same license.
Limitations: purchase links, Chinese retailers, and what the list does not cover
The most significant limitation for non-Chinese readers is that most book title links lead to JD.com or Dangdang, both of which are Chinese e-commerce platforms. A developer outside China can still use the list for discovery: the abstracts explain what each book covers and who it is for in enough detail to make an informed purchase decision through other channels. But the one-click purchase experience is designed for readers in mainland China.
The list also does not cover freely available online resources. There are no links to free PDFs, open-access textbooks, or online courses. Each entry assumes the reader will buy the book. This is a deliberate editorial choice: the README explicitly encourages purchasing originals to support authors.
The README does not document the total number of books in the list, the frequency with which entries are reviewed for relevance, or a process for removing entries that become outdated. The VitePress version is 2.0.0-alpha.20, which is a pre-release version; the behavior of the build toolchain may change as VitePress 2.0 is finalized.
free-programming-books as an alternative for free online resources
EbookFoundation's free-programming-books is the most widely known alternative in the same category. The fundamental difference is the editorial policy. free-programming-books collects links to freely available online resources including open-access textbooks, tutorial sites, and free e-books in dozens of languages. doocs/technical-books collects purchase recommendations for books worth buying, with a focus on the Chinese market.
The overlap in topic coverage is substantial: both repositories cover algorithms, systems, networking, and web development. The difference shows up in the specific entries. free-programming-books includes resources that can be read immediately at no cost. doocs/technical-books includes books like "Computer Systems: A Programmer's Perspective" and "Domain-Driven Design" that are widely available for purchase but rarely free online.
A developer building a reading list for self-directed learning might use both: doocs/technical-books to identify which books to purchase for in-depth study, and free-programming-books to find supplementary online material for topics covered in those books. The CC-BY-SA-4.0 license on doocs/technical-books permits incorporating its curated entries into other reading list projects with attribution.
Editorial conclusion
doocs/technical-books is a useful reference for developers looking for structured reading recommendations across the major areas of computer science and software engineering, particularly those who prefer to buy and read physical or digital books rather than rely on free online tutorials. It is best suited to readers who can access Chinese book retailers, since many titles link to JD.com and Dangdang. Engineers looking for freely available online resources should look elsewhere, as the focus is on recommending books to purchase. Contributors who want to add a title can use the Discussions area (Discussion #30) or submit a pull request; the CC-BY-SA-4.0 license permits reuse with attribution and share-alike requirements.
Frequently asked questions
How do I suggest a book for doocs/technical-books?
The README directs new book suggestions to GitHub Discussions, specifically Discussion #30. Alternatively, a pull request editing the README or docs/ source files is also accepted. The Giscus-powered comment system on book.doocs.org connects to the same GitHub Discussions, so comments left on the site appear in the repository.
What topics does doocs/technical-books cover?
The repository description lists eight areas: computer basics, networking, frontend, backend, databases, architecture, big data, and deep learning. The README confirms at least computer systems and algorithms, and computer networking sections with named entries including classics like CSAPP, CLRS, and TCP/IP Illustrated.
Can I run the doocs/technical-books site locally?
Yes. The repository uses VitePress and pnpm. After installing dependencies, run pnpm run docs:dev to start the local development server. Node.js 22.12.0 or later and pnpm are required. The deploy:cf script handles Cloudflare Workers deployment through wrangler.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/doocs-technical-books)