Reading List • Recommended Books

Books I Read

Ten foundational books that shaped how I build fast software, audit cloud bills, manage lean teams, and write in plain English. Each entry includes five direct lines on what the book teaches and why it matters.

Honest Disclosure

I read physical paper books and re-read foundational titles every year. Some links on this page are affiliate links. If you buy through them, this independent platform may receive a tiny commission at zero extra cost to you. I only recommend books I have tested and applied in real production systems.

How I Read • 3 Simple Habits
Habit 01

Read on Physical Paper

Screens invite distraction, notifications, and skimming. Paper forces deep attention and lets you mark up the margins with ink.

Habit 02

The 3-Sentence Summary

After finishing any chapter, write its core point on an index card in three sentences that a 10-year-old child could understand.

Habit 03

Re-read the Greats

Reading ten timeless books five times each gives you far more real leverage than skimming fifty forgettable airport business books once.

Foundational Books • 10 Recommendations
Systems • Read 3 Times
Essential

Systems Performance: Enterprise and the Cloud

by Brendan Gregg
  • What it is: The ultimate field manual for understanding where computers spend time across CPU, memory, storage disks, and network interfaces.
  • What I learned: Software is rarely slow because of complex math. It is slow because it sits idle waiting on disk blocks or network packets.
  • Core lesson: Never guess what makes a program slow. Measure hardware counters and operating system queues directly.
  • Who should read it: Any backend developer or systems architect tasked with lowering cloud bills and fixing slow response times.
  • Favorite concept: The USE method (Utilization, Saturation, and Errors) for diagnosing bottlenecks in five minutes.
Focus: Computer Hardware & Latency View on Amazon →
Data • Read 2 Times
Essential

Designing Data-Intensive Applications

by Martin Kleppmann
  • What it is: A master-level textbook explaining how databases, caches, queues, and distributed clusters store and replicate information.
  • What I learned: True data consistency across multiple machines is expensive and difficult. Every distributed system must make trade-offs.
  • Core lesson: Reliability is not an accident. You must design code expecting networks to cut out, hard drives to fail, and clocks to drift.
  • Who should read it: Engineers scaling their software past one server or deciding between SQL, key-value stores, and stream processors.
  • Favorite concept: Log-structured storage engines and write-ahead logs as the single source of truth.
Focus: Distributed Systems & Databases View on Amazon →
Networking • Annual Reread
Speed

High Performance Browser Networking

by Ilya Grigorik
  • What it is: A guide on how data packets travel across the world via TCP, UDP, TLS handshakes, mobile radios, and HTTP protocols.
  • What I learned: The speed of light in glass is a hard physical wall. You cannot buy more CPU power to fix a 200-millisecond roundtrip latency.
  • Core lesson: The fastest request is the request never made. Move computation to the edge and cache aggressively.
  • Who should read it: Web engineers, mobile developers, and anyone trying to make websites load in under 500 milliseconds.
  • Favorite concept: Head-of-line blocking in TCP versus multiplexed streams in modern protocols.
Focus: Packet Latency & Network Protocols View on Amazon →
Writing • Read 5 Times
Clarity

The Elements of Style

by William Strunk Jr. and E.B. White
  • What it is: A tiny 80-page manual on the rules of clear, direct, and unpretentious English prose.
  • What I learned: Vigorous writing is concise. A sentence should contain no unnecessary words, just as a machine should contain no unnecessary parts.
  • Core lesson: Omit needless words. If you can state an engineering idea in 6 words, never use 25.
  • Who should read it: Engineers, founders, and leaders who want their emails, proposals, and essays to be understood instantly.
  • Favorite concept: Put statements in positive form rather than hiding behind double negatives.
Focus: Plain English & Clear Communication View on Amazon →
Mental Models • Read 2 Times
Wisdom

Poor Charlie's Almanack

by Charles T. Munger
  • What it is: The collected speeches and practical wisdom of Charlie Munger on multidisciplinary thinking and decision-making.
  • What I learned: It is remarkably easy to get ahead in life and business simply by avoiding consistent stupidity rather than attempting to be brilliant.
  • Core lesson: Invert, always invert. When designing a system, list all the ways it can crash, and systematically remove them.
  • Who should read it: Anyone making capital allocation, architecture, or life decisions under uncertainty.
  • Favorite concept: The psychology of human misjudgment and incentive-caused bias.
Focus: Decision-Making & Multidisciplinary Models View on Amazon →
Engineering Management • Read 2 Times
Classic

The Mythical Man-Month

by Fred Brooks
  • What it is: Classic essays written by the project manager of the IBM System/360 operating system on software complexity and human coordination.
  • What I learned: Adding developers to a delayed software project makes it even later due to communication overhead.
  • Core lesson: Conceptual integrity is the most important attribute of great software. It is best achieved by a tiny team of 3 to 5 builders.
  • Who should read it: Engineering managers, CTOs, and founders who wonder why their 50-person department moves slowly.
  • Favorite concept: The surgical team model: one chief programmer supported by specialized toolmakers.
Focus: Team Size & Software Delivery View on Amazon →
Computer Science • Read 2 Times
Foundational

Structure and Interpretation of Computer Programs

by Harold Abelson and Gerald Jay Sussman
  • What it is: The legendary MIT textbook on procedural abstraction, data representations, metalinguistic abstraction, and interpreters.
  • What I learned: Programs must be written for people to read, and only incidentally for computers to execute.
  • Core lesson: Master simple primitives and clean combination rules. You do not need giant frameworks to build powerful systems.
  • Who should read it: Programmers who want to see past syntax and understand the underlying mathematics of computing.
  • Favorite concept: Building an interpreter from scratch to create a custom language suited to your problem.
Focus: Abstraction & Language Design View on Amazon →
Startups • Read 2 Times
Honest

The Hard Thing About Hard Things

by Ben Horowitz
  • What it is: A blunt, unfiltered look at founding and running technology businesses when everything is breaking and money is running out.
  • What I learned: There are no silver bullets in leadership or systems crisis response. There are only lead bullets: hard work, honest talk, and relentless focus.
  • Core lesson: Tell it like it is. Your team already knows when things are difficult. Honesty creates trust and focus.
  • Who should read it: Founders, CEOs, and senior engineers navigating real business or technical crises.
  • Favorite concept: Peacetime CEO versus Wartime CEO tactics and mindset.
Focus: Founder Psychology & Crisis Management View on Amazon →
Code Quality • Read 2 Times
Craft

Refactoring: Improving the Design of Existing Code

by Martin Fowler
  • What it is: A systematic catalog of disciplined steps to clean code and clarify architecture without changing user-facing behavior.
  • What I learned: Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
  • Core lesson: Refactor in tiny, verified increments backed by comprehensive test suites. Never do massive, untestable rewrites.
  • Who should read it: Every software professional who maintains production systems.
  • Favorite concept: Code smells and the disciplined extract function refactoring move.
Focus: Clean Code & Architecture Discipline View on Amazon →
Strategy • Read 3 Times
Leverage

Zero to One: Notes on Startups

by Peter Thiel with Blake Masters
  • What it is: A short treatise on technology monopolies, contrarian secrets, and building products that create brand-new markets.
  • What I learned: Competition is for losers. If you want to create and capture lasting value, build a business around proprietary technology in a focused niche.
  • Core lesson: What important truth do very few people agree with you on? Build software that proves your answer true.
  • Who should read it: Independent builders, engineers planning startups, and product leaders.
  • Favorite concept: The power law of venture returns and why distribution is as important as the product.
Focus: Proprietary Technology & Market Power View on Amazon →
Continue Exploring
Essays • Free

Start Here →

The 10 most popular essays covering latency, cloud waste, and small software teams.

Deep Work • Notes

Think Week Notes →

Notes and reading synthesis from our annual off-grid architectural retreat.

Store • Digital

Digital Store →

Our handbooks, spreadsheets, and technical toolkits for immediate download.

1-on-1 Advisory Session

Need Architecture Guidance or Book Recommendations?

Book a focused 30-minute private advisory consultation with Arkajit Das. We will discuss your team reading curriculum, software latency bottlenecks, or cloud infrastructure savings.

Fee: INR 2,000 / $20 USD
Book a 30-Minute Call →