<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: yaso</title>
    <description>The latest articles on DEV Community by yaso (@__yaso).</description>
    <link>https://dev.to/__yaso</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3863995%2Fe9d1445c-982c-4483-964e-34e4357a4e7b.png</url>
      <title>DEV Community: yaso</title>
      <link>https://dev.to/__yaso</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/__yaso"/>
    <language>en</language>
    <item>
      <title>I scanned 1.27M DEV articles to find the books developers actually recommend.</title>
      <dc:creator>yaso</dc:creator>
      <pubDate>Tue, 21 Apr 2026 13:21:26 +0000</pubDate>
      <link>https://dev.to/__yaso/i-scanned-127m-dev-articles-to-find-the-books-developers-actually-recommend-5fd7</link>
      <guid>https://dev.to/__yaso/i-scanned-127m-dev-articles-to-find-the-books-developers-actually-recommend-5fd7</guid>
      <description>&lt;p&gt;&lt;strong&gt;I kept wishing for a data-driven book ranking for developers.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;"Top 10 Books Every Developer Should Read" articles all come down to one person's opinion. Some of them are paid posts.&lt;/p&gt;

&lt;p&gt;But I got curious. Out of the millions of articles on DEV.to — written by actual working developers — the books that lots of engineers mention have to be good ones, right? And wouldn't it be useful to see them sorted by topic, by level?&lt;/p&gt;

&lt;p&gt;What does the brutal data — &lt;strong&gt;"how many times a working developer recommended this book to another developer"&lt;/strong&gt; — actually surface?&lt;/p&gt;

&lt;p&gt;To get that answer, I counted. All of it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem with every "best developer books" list
&lt;/h2&gt;

&lt;p&gt;You've read them. So have I. They usually come in one of three shapes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;One person's taste.&lt;/strong&gt; "10 books that made me a better engineer." Fine — but that's your list.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bestseller rollups.&lt;/strong&gt; "Top-selling programming books on Amazon." That's a popularity proxy, not a recommendation signal. You can buy your way in.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Expert panels.&lt;/strong&gt; "We asked 10 senior engineers…" Ten is a small number. Which ten?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of them go back to the source. &lt;em&gt;What do developers themselves write when they recommend a book?&lt;/em&gt; That's the signal I wanted.&lt;/p&gt;

&lt;p&gt;DEV.to has 1.27 million public articles. Developers recommend books on it constantly — not just in "tech books" posts, but in career articles, interview prep guides, "books that changed my life" threads, framework tutorials. Nobody had aggregated all of it. So I did.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I did
&lt;/h2&gt;

&lt;p&gt;I scanned every public article on DEV.to. Full pipeline with numbers is on the &lt;a href="https://geekpeak.dev/methodology" rel="noopener noreferrer"&gt;methodology page&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Corpus collection (29 hours, 20 proxy IPs in parallel)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Scanned all &lt;strong&gt;2.42M article IDs&lt;/strong&gt; from DEV.to's public API&lt;/li&gt;
&lt;li&gt;Retrieved &lt;strong&gt;1,271,389 articles&lt;/strong&gt; (the rest had been deleted)&lt;/li&gt;
&lt;li&gt;100% recovery rate via retry logic&lt;/li&gt;
&lt;li&gt;3.1 GB corpus saved to disk&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. Book-article detection (3 layers)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Deterministic signals:&lt;/strong&gt; Amazon ASINs, ISBNs, publisher URLs (O'Reilly, Manning, Packt, etc.)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Heuristics:&lt;/strong&gt; recommendation phrases, title patterns, "Top N" list structures&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lexical match:&lt;/strong&gt; known-book dictionary&lt;/li&gt;
&lt;li&gt;Result: &lt;strong&gt;12,568 articles&lt;/strong&gt; flagged as containing a book recommendation (0.99% of the corpus)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. Extraction + canonicalization
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Pulled book references from each article (ASINs, ISBNs, Markdown links, text patterns)&lt;/li&gt;
&lt;li&gt;Merged duplicates with fuzzy title matching + 100+ manual merge rules&lt;/li&gt;
&lt;li&gt;Non-book filters: video courses, GitHub repos, physical products, spam&lt;/li&gt;
&lt;li&gt;Final: &lt;strong&gt;664 unique books&lt;/strong&gt;, &lt;strong&gt;4,616 mentions&lt;/strong&gt;, &lt;strong&gt;2,830 articles&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  4. Quality
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Book Precision 99.7%:&lt;/strong&gt; Manually reviewed all &lt;strong&gt;684 initial candidates&lt;/strong&gt; against Google Books / Open Library / publisher sites. Removed 27 non-books, corrected 345 title/author fields → 657 books (March snapshot). Since then, 23 further non-books have been excluded and 30 entries reclassified back in, leaving the current &lt;strong&gt;664&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Article Recall probe ~99%:&lt;/strong&gt; Sampled 100 non-detected articles stratified by engagement. 1 miss found.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Known limitations:&lt;/strong&gt; DEV.to only, primarily English, pattern-based detection (no LLM) — documented in full on the &lt;a href="https://geekpeak.dev/methodology" rel="noopener noreferrer"&gt;methodology page&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Every number on that page links to the raw sample.&lt;/p&gt;

&lt;h2&gt;
  
  
  All-time Top 10
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Rank&lt;/th&gt;
&lt;th&gt;Book&lt;/th&gt;
&lt;th&gt;Author&lt;/th&gt;
&lt;th&gt;Articles&lt;/th&gt;
&lt;th&gt;Unique authors&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;1&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Clean Code&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Robert C. Martin&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;228&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;143&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;The Pragmatic Programmer&lt;/td&gt;
&lt;td&gt;Hunt &amp;amp; Thomas&lt;/td&gt;
&lt;td&gt;119&lt;/td&gt;
&lt;td&gt;83&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Designing Data-Intensive Applications&lt;/td&gt;
&lt;td&gt;Martin Kleppmann&lt;/td&gt;
&lt;td&gt;85&lt;/td&gt;
&lt;td&gt;55&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Design Patterns (GoF)&lt;/td&gt;
&lt;td&gt;Gamma, Helm, Johnson, Vlissides&lt;/td&gt;
&lt;td&gt;74&lt;/td&gt;
&lt;td&gt;62&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;The Phoenix Project&lt;/td&gt;
&lt;td&gt;Kim, Behr, Spafford&lt;/td&gt;
&lt;td&gt;69&lt;/td&gt;
&lt;td&gt;54&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Clean Architecture&lt;/td&gt;
&lt;td&gt;Robert C. Martin&lt;/td&gt;
&lt;td&gt;59&lt;/td&gt;
&lt;td&gt;54&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;Deep Work&lt;/td&gt;
&lt;td&gt;Cal Newport&lt;/td&gt;
&lt;td&gt;75&lt;/td&gt;
&lt;td&gt;27&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;Head First Design Patterns&lt;/td&gt;
&lt;td&gt;Freeman, Robson, Bates, Sierra&lt;/td&gt;
&lt;td&gt;76&lt;/td&gt;
&lt;td&gt;45&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;Test-Driven Development: By Example&lt;/td&gt;
&lt;td&gt;Kent Beck&lt;/td&gt;
&lt;td&gt;47&lt;/td&gt;
&lt;td&gt;45&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;Code Complete&lt;/td&gt;
&lt;td&gt;Steve McConnell&lt;/td&gt;
&lt;td&gt;44&lt;/td&gt;
&lt;td&gt;39&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Live ranking (sortable, filterable, with score history): &lt;a href="https://geekpeak.dev" rel="noopener noreferrer"&gt;geekpeak.dev&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Four things the data showed me
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Clean Code is a landslide.&lt;/strong&gt; 228 mentions &amp;gt; #2 + #3 combined (204). And 143 different authors recommended it. That's not a loud minority — it's a real working consensus across DEV.to.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Robert C. Martin has two books in the Top 10.&lt;/strong&gt; Clean Code (#1) and Clean Architecture (#6). No other author has two. "Uncle Bob" dominance is measurable and has lasted a decade.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Deep Work is #7 — and it's not a technical book.&lt;/strong&gt; Cal Newport's productivity book ranks above Clean Architecture. Developers clearly see meta-skills (focus, mental models, learning strategy) as part of the job, not adjacent to it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. 60% of the Top 10 is 10+ years old.&lt;/strong&gt; Pragmatic Programmer (1999), Design Patterns (1994), Code Complete (2004), TDD by Example (2002), Clean Code (2008). Classics stay classic. What moves is #11 and below.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's NOT in this post
&lt;/h2&gt;

&lt;p&gt;This is the overall all-time ranking. GeekPeak shows slices no single post can fit:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Topic-specific #1s.&lt;/strong&gt; What's the #1 for Python? System design? Interview prep? AI/ML? &lt;strong&gt;Career?&lt;/strong&gt; A few will surprise you. The AI/ML #1 was ranked &lt;strong&gt;#424 in September 2025&lt;/strong&gt;. Today it's &lt;strong&gt;#13 overall&lt;/strong&gt;. That's seven months.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Source articles per book.&lt;/strong&gt; Every one of Clean Code's 228 mentions links to the actual article that made it. Not "trust me" — "check me."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Score history.&lt;/strong&gt; Which books are rising? Which are fading? Per-book trend charts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Last 90 days.&lt;/strong&gt; The short-term top 10 looks &lt;em&gt;nothing&lt;/em&gt; like the all-time list above. Clean Code is still #1 even over 90 days — but #2 through #5 have shifted dramatically. &lt;em&gt;That's the next post.&lt;/em&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Come look: &lt;strong&gt;&lt;a href="https://geekpeak.dev" rel="noopener noreferrer"&gt;geekpeak.dev&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I'm sharing this
&lt;/h2&gt;

&lt;p&gt;Just one person (&lt;a href="https://x.com/__yaso" rel="noopener noreferrer"&gt;@__yaso&lt;/a&gt;) who scanned a lot of articles out of curiosity. No editorial board — when the methodology page says "we," it's me using the royal plural.&lt;/p&gt;

&lt;p&gt;Honestly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Solo project, non-commercial intent.&lt;/strong&gt; Book detail pages have Amazon affiliate links, but they have zero effect on ranking (scoring runs before the monetization layer — documented on the &lt;a href="https://geekpeak.dev/methodology#scoring-formula" rel="noopener noreferrer"&gt;methodology page&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The data isn't perfect.&lt;/strong&gt; DEV.to only (no Hashnode / Medium yet), English-primary, pattern-based detection (no LLM), popularity bias — a niche excellent book will always rank below a well-known decent one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Email me if you spot an error.&lt;/strong&gt; &lt;code&gt;geekpeak.dev@gmail.com&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What would help most: &lt;strong&gt;tell me a book that should be ranked but isn't, or one that's in the wrong spot.&lt;/strong&gt; Better data = more useful to everyone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Coming next
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;"Clean Code is still the #1 book developers recommend on DEV in 2026. But the last-90-days Top 10 looks almost nothing like the all-time list."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Follow me if you want that one too.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;📚 &lt;a href="https://geekpeak.dev" rel="noopener noreferrer"&gt;Full Top 100, topic-filtered lists, per-book source articles →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Actually go use the ranking, poke at it, and tell me what you think.&lt;/p&gt;

</description>
      <category>books</category>
      <category>showdev</category>
      <category>beginners</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
