Digital Replacement Tech Books: Migration Guide Paper

Last month, when I was moving, I stood in front of the 47 tech books on my bookshelf and seriously asked myself for the first time: do I really need them all?

The answer: no, not all of them.

Those books weighed at least 30 kg combined, and they took up the only wall in my rental that could fit a bookshelf. The irony is, in the past six months, I've opened fewer than 3 of them. Most of the content can be found in newer versions online, and some of the tech stacks are already outdated.

But throwing them out? I can't bring myself to. After all, every one of them was bought with real money, and I made notes in some of them. So I started researching digitization, with one goal: free up the bookshelf space while keeping all the content I need.

The Pain Points of Paper Tech Books

Let me start with why I decided to migrate.

Too heavy. A copy of "Computer Systems: A Programmer's Perspective" weighs over 2 kg. Carrying it to a coffee shop to study? My shoulders would protest. I tried it once, then gave up.

Takes up space. My rental is only 12 square meters, and the bookshelf takes up an entire wall. If I could clear that wall, I could put a small desk there, or a folding chair, or just nothing — empty space is a luxury too.

Updates too slowly. From writing to publishing, a tech book takes at least a year, but tech stacks update on a monthly cycle. I bought a React book, and when I got it, the content was still all about class components, but by the time I started reading it, hooks were already mainstream. I never finished the book before the tech changed.

Hard to search. To find a specific concept, you have to flip through the table of contents, the index, and the page numbers. With an e-book, just Ctrl+F, instant results. The efficiency gap is just too big.

Of course, paper books have their merits: better reading experience, less distraction, you can take physical notes. I'll admit that. But for me, the merits don't outweigh the pain points, especially the two hard ones of weight and space.

E-Book Platform Comparison

I researched the major e-book platforms on the market. Here's what I actually use.

Kindle: pros are a huge library, especially for English tech books — O'Reilly and Manning are basically all there. The reading experience is good, e-ink is easy on the eyes. Cons: relatively fewer Chinese tech books, and after Amazon left China, buying books is a bit more hassle, requires switching regions.

WeChat Reading: the Chinese library is strong, lots of domestically published tech books. Pros: social features, you can see other people's notes and highlights. Cons: lots of tech books aren't available, especially English originals. Plus it's subscription-based, so if you only read tech books, the value isn't great.

O'Reilly Learning Platform: a developer's dream. Almost all O'Reilly, Manning, and Packt books are there, plus video courses. Cons: expensive, the annual fee is a few hundred dollars. But if you read more than 5 tech books a year, it's actually more cost-effective than buying individually. My company reimburses it, so I'm using it.

Douban Reading / Duokan Reading: the Chinese library is okay, tech book coverage is average. Pros: good Chinese typography, relatively cheap. Good for non-tech books or tech books by Chinese authors.

My approach is to combine them: English tech books on Kindle or O'Reilly, Chinese tech books on WeChat Reading or Douban Reading. No single platform covers everything, so combining is the most practical.

Paper Book Migration Steps

After deciding to migrate, I followed these steps.

Step 1: Sort. Out of 47 books, I divided them into three categories:

• Keep paper: classics, books I flip through often, ones with important handwritten notes. Kept 8, like "Code Complete," "Design Patterns," and "Introduction to Algorithms" — these don't go out of style.
• Digitize: content has value but I don't need a paper copy. The biggest group, 28 books.
• Get rid of: outdated, no value left, ones I bought and never opened. 11 books.

Step 2: Find the digital version. For the 28 I wanted to digitize, I first searched the major platforms for an official e-book. Found 19, bought or subscribed directly. For the remaining 9, some were out of print, some had no e-book — I scanned the key chapters of those 9, then gave the physical books to coworkers or donated them to a community library.

Step 3: Scan the notes. For the books with handwritten notes, I used a phone scanning app to photograph the note pages and save them to the cloud drive. The process was a bit tedious, but it was worth it — those notes were the product of my thinking at the time, I couldn't lose them.

Step 4: Handle the physical books. The 11 books I was getting rid of, I split into two batches: the ones in good condition I sold on a second-hand book platform for about $30 back; the ones in rough shape or with outdated content, I sold as waste paper for about $2. Not a lot of money, but at least the books didn't go straight into the trash.

E-Book Management System

After digitizing, management became the new problem. My e-books are scattered across four platforms, and without management, finding a book is even worse than flipping through a bookshelf.

My solution is a simple Notion database. One entry per book, with the following fields:

• Title and author
• Platform (Kindle / WeChat Reading / O'Reilly / local PDF)
• Reading status (Not started / In progress / Completed / Paused)
• Tech domain (frontend / backend / algorithms / architecture, etc.)
• Rating and short notes
• Purchase / acquisition date

This database lets me quickly filter by tech domain, and see where I've been spending the most time. For example, I noticed I've read 8 frontend books but only 3 backend books — that reminded me to catch up on backend.

For local PDFs (like internal company tech docs and conference papers), I use a unified folder structure:

E-Books/
  Frontend/
  Backend/
  Algorithms/
  Architecture/
  Soft Skills/
  Uncategorized/

Each file is named [Author] Title.pdf. That way, sorting by filename groups books by the same author, easier to find.

When You Still Need Paper Books

Although I'm pushing digitization, there are still some cases where paper is irreplaceable.

Classic reference books: like "Structure and Interpretation of Computer Programs" — the paper reading experience really is better. And these books don't go out of style, so worth keeping long-term.

Books that need deep reading: some books need you to flip back and forth, take lots of notes, draw mind maps. Paper is more convenient. E-books can be annotated too, but the experience is just worse.

Exam prep books: if you're going for a certification, paper books are better for marking and flipping back to review.

Collector's value: some books are first editions or signed by the author. Those have emotional value, of course you keep them.

My rule: unless one of the above applies, e-book first.

Choosing E-Reading Devices

Let me end with the devices. My main devices right now are three.

Kindle Paperwhite: for books that are mostly text, like algorithms or design patterns with little code. E-ink is genuinely comfortable, doesn't tire my eyes. Cons: not great for code, small screen, layout can get messed up sometimes.

iPad Pro 11-inch: for books with lots of code, or ones where I need to read and code at the same time. Big screen, color display, code highlighting works. Cons: heavy, holding it up to read is tiring, and easy to get distracted — suddenly I'm on WeChat.

MacBook: for PDFs and tech papers. Big screen + keyboard, perfect for deep reading. But staring at an LCD screen for a long time really does make my eyes sore.

My usage: Kindle for non-code books, iPad for code books, MacBook for PDFs. No device is perfect, only the right scenario.

Wrapping Up

Going from 47 paper books down to 8, my bookshelf is more than half empty. That wall now has a map and a small whiteboard — the whiteboard for weekly to-dos, way more practical than a bookshelf.

Digitization took me two weekends, but the payoff is long-term: moving is easier, finding books is faster, and the rental feels more spacious. Best of all, I no longer have to choose between "buy a new book but nowhere to put it" and "want to learn but the book is too heavy to carry."

If you're a tech book hoarder, I'd suggest starting with sorting. You don't have to digitize everything at once — pick 10 of the most-used ones to try first. You'll find that the e-book version isn't as painful as you imagined, and the space and shoulder relief will be very grateful.