When I first imagined The Textsmith Bookshelf, I wondered what book should occupy the first shelf.
Then it occurred to me that perhaps no book should.
Before reviewing books, it is worth asking a simpler question: why should a textsmith still read books at all?
After all, we live in an age where information has never been easier to obtain.
Need to remember an awk command? Search for it.
Forgot the syntax of a regular expression? Someone has already answered it on Stack Overflow.
Looking for a Bash one-liner? A search engine will find dozens.
Need a complete script? Ask ChatGPT, Gemini, Claude, or another AI assistant, and one will appear in seconds.
None of these tools are bad. In fact, I use them myself almost every day.
They save time.
They solve problems.
They make us more productive.
But they are not the same as reading.
There is a profound difference between finding an answer and building understanding.
When we search for a solution online, we usually arrive with a question that is already well defined. We know what is broken and want the quickest path to fixing it.
Books work in the opposite direction.
A good technical book does not simply answer the questions you already have. It introduces questions you never knew to ask.
That is why books continue to matter.
Reading Effective awk Programming, for example, teaches far more than the syntax of awk. It introduces the mindset that every line of text is a record and every word a field. Once you understand that idea, you begin seeing structure everywhere.
The same is true of a good book on regular expressions, version control, typography, documentation, or shell scripting. The lasting value is rarely the commands themselves. It is the way of thinking that those commands represent.
This is also why manuals remain indispensable.
For many people, the manual has become the last place they look. We consult a search engine first. We ask an AI assistant second. Only if those fail do we open the official documentation.
I have gradually come to believe the opposite approach is healthier.
Search engines tell you what worked for someone else.
AI tells you what is likely to work.
The manual tells you what the software was designed to do.
That distinction becomes increasingly important as our tools become more sophisticated.
Artificial intelligence has changed how we learn, and for the better in many ways. Instead of spending an afternoon searching mailing lists, we can ask an assistant to explain an error message, generate a script, or compare two approaches. It is an extraordinary development.
But AI works best when it builds upon understanding rather than replacing it.
Someone who has read the manuals can ask better questions.
Someone who understands the fundamentals can recognise when generated code is elegant and when it merely appears convincing.
Someone who knows the philosophy behind a tool can adapt solutions instead of copying them blindly.
That is the difference between using technology and mastering it.
The craft of the textsmith has always been built upon careful reading.
We read documentation to understand our tools.
We read standards to understand formats.
We read manuals to understand behaviour.
We read good technical books because they collect years of experience into a single, coherent conversation.
Unlike scattered web pages, a well-written technical book has a beginning, a middle, and an end. It takes the reader on a journey from ignorance to competence. Every chapter builds upon the last. Every concept has a place within the larger picture.
That kind of sustained learning is difficult to reproduce through isolated searches.
The internet excels at solving today’s problem.
Books prepare us for tomorrow’s.
That is why The Textsmith Bookshelf exists.
Some Sundays we will explore classics that have shaped generations of programmers and system administrators. Other Sundays we will look at newer works that are redefining how we write, publish, and process text.
The goal is not simply to recommend books.
It is to celebrate the habit of reading them.
Because in a world overflowing with instant answers, the ability to sit down with a thoughtful manual, a carefully written piece of documentation, or a timeless technical book remains one of the greatest investments a textsmith can make.
The fastest answer is not always the deepest one.
And the deepest understanding is still found, one page at a time.