Why should we read books frequently?

- Technicals – coders, scientists, engineers, artists, builders, etc. - Non-technicals – business people, marketers, writers, policy folks, ops, etc.

There are also two broad skillsets:

- Technical skills – like coding, design, architecture, engineering. - Non-technical skills – and the core of all of these is communication.

The foundation of communication is language. Reading or listening to books, and building core knowledge are how people become strong communicators.

Many of the most successful tech professionals are not just highly skilled technically — they’re also at least above average in communication.

Those who lack communication skills tend to fail — especially in non-technical roles, but sometimes even in technical ones.

That’s why reading and listening to books isn’t optional — it’s essential. Whether you’re in marketing, product, or engineering, communication is a core part of the job.

Say we had two heirs to a monarchy: one who never read a book in his life, and the other who was exclusively allowed to interpret Mein Kampf and The Fountainhead to formulate their political ideologies. Would the reader really be the more intelligent, grounded leader? Would their surrogate, vicarious experiences in literature give them an advantage over someone who synthesizes their judgement from nothing but personal experience?

This can be good.

It can also be bad.

The best part is that we can choose which books we read.