The Software Developer's Guide to Linux

Aleksandr Shitik
Aleksandr Shitik

I write my own posts and books, and review movies and books. Expert in cosmology and astronomy, IT, productivity, and planning.

The Software Developer's Guide to Linux
David Cohen, Christian Sturm
Genres: Programming
Year of publication: 2025
Year of reading: 2026
My rating: Highest
Number of reads: 1
Total pages: 310
Summary (pages): 22
Original language of publication: English
Translations to other languages: Russian

General description

The book is a little over 300 pages. Besides text, it contains code inserts, images, tables. The difficulty level is easy / medium. It covers basic administration topics. It will be useful primarily for developers who decided to level up their skills.

Brief contents

  • Chapter 1. How the command line works.
  • Chapter 2. How to work with processes.
  • Chapter 3. How to manage services with systemd.
  • Chapter 4. Command history in the Linux shell.
  • Chapter 5. Files in Linux.
  • Chapter 6. How to edit files from the command line.
  • Chapter 7. Users and groups.
  • Chapter 8. Resource owners and access rights.
  • Chapter 9. How to install software.
  • Chapter 10. How to configure application configuration.
  • Chapter 11. Pipelines and input/output redirection.
  • Chapter 12. How to automate tasks using command shell scripts.
  • Chapter 13. Secure remote access via SSH.
  • Chapter 14. How to manage versions with Git.
  • Chapter 15. Container virtualization of applications using Docker.
  • Chapter 16. Application logs.
  • Chapter 17. Load balancing and the HTTP protocol.

Opinion

For myself, I find this book interesting and useful, and as a result the book received a high rating from me. First, while reading this book, the interest in reading did not disappear, which happens quite rarely. Second, its technical material was moderately complex in the sense that after reading the book there was no impression that you had taken absolutely nothing new from it, just as there was no impression that it was overly overloaded with some brand-new information, of which you know nothing, as often happens with completely new technologies. Third, the material of this book also did not become more complicated as reading progressed in terms of perception. These were different topics, but each of them did not seem very complex. And finally, fourth, the topics themselves turned out to be maximally consistent and well thought out.

Вверх