I own and have read his following books and they were all superb!
The Go Programming Language
The Practice of Programming
The C Programming Language
The AWK Programming Language11–20 of 141 posts
I own and have read his following books and they were all superb!
The Go Programming Language
The Practice of Programming
The C Programming Language
The AWK Programming LanguageYou'd think he would have found someone to design a nicer cover for him.
The book is a great read otherwise!
I've been lucky enough to work and hang out with some of the co-founders of very impactful projects, such as OpenStack and Cloud Foundry, and there are so many stories I've heard that I'm sure would be insightful and valuable lessons for whomever is embarking on new ideas. And yet, we all move so fast, that there is no time to stop and write them down.
I'm glad BK did. UNIX is foundational to essentially all software-driven technology today, in one way or another. His book (along with Dennis Ritchie) on the C Programming Language made a huge impact for me as a CompSci student in the 80s, as did UNIX itself (Ultrix and DG/OS were my fist UNIX variants).
I look forward to read his book.
Is there a kindle/digital/ebook version of this book? I can't seem to find it.
You'd think he would have found someone to design a nicer cover for him.
You have no idea. I received my copy a few days ago. The whole cover is a low-resolution bitmap for both the image and the text. The book is a great read otherwise!
Is there a kindle/digital/ebook version of this book? I can't seem to find it.
I don’t see one either, which puzzles me. I only read on paper if there is no other alternative. This seems like exactly the kind of book I would hope to read in digital form, but I'm not finding it.
I have stopped buying paper books over past several years as they simply accumulate moisture and mould in the climate I live in and make rooms smell musty. It is incomprehensible to me why primarily textual books would be published without and ebook version these days.
I've always felt we don't appreciate history very much in our industry. I've been lucky enough to work and hang out with some of the co-founders of very impactful projects, such as OpenStack and Cloud Foundry, and there are so many stories I've heard that I'm sure would be insightful and valuable lessons for whomever is embarking on new ideas. And yet, we all move so fast, that there is no time to stop and write them…
I try and keep the following in mind (even when my ego fights it).
(A) I am very unlikely to be the smartest person who's ever thought about a problem. (B) Even if their technology differed, some parts of their approach are useful. (C) Clues and references pop up in the oddest places, so ears open and notepad ready. (D) Accept references graciously, in the spirit of a gift. (E) Name dropping historical references without providing actual context is always in poor taste.