summaryrefslogtreecommitdiff
path: root/content/books/coders-at-work.md
diff options
context:
space:
mode:
authormjkwiatkowski <mati.rewa@gmail.com>2026-02-01 15:02:02 +0100
committermjkwiatkowski <mati.rewa@gmail.com>2026-02-01 15:02:02 +0100
commit9844a5c7694fcae61ed4509f09a595daf15cb44f (patch)
treef844386a8e01e6f3f4bbd4c268edec587e8881a6 /content/books/coders-at-work.md
parente99bd99eeedbf38390e0d4d014c35b04a280767b (diff)
feat: major changes to website design
Diffstat (limited to 'content/books/coders-at-work.md')
-rw-r--r--content/books/coders-at-work.md27
1 files changed, 0 insertions, 27 deletions
diff --git a/content/books/coders-at-work.md b/content/books/coders-at-work.md
deleted file mode 100644
index a4a7568..0000000
--- a/content/books/coders-at-work.md
+++ /dev/null
@@ -1,27 +0,0 @@
-+++
-date = '2025-09-03T18:28:08+02:00'
-draft = true
-title = 'Coders at Work'
-+++
-
-![coders-at-work](/images/coders-at-work.jpg#floatright)
-
-Coders at Work is a book written by Peter Seibel, a programmer who decided to interview some of the most influential coders in the Computer Science field.
-I think this book is a must read for anyone who wants to gain an in-depth view of what prompted the best programmers in the world to start tinkering with computers and code.
-
-To be frank each chapter read of this book has motivated me to immediately stop anything that I was doing and just get to coding, so it is definitely a good motivator to get into the Computer Science field.
-Additionally, sometimes to new programmers it might be challenging and overwhelming to get to realize how much there is to learn and how advanced the people at the top are.
-There is no doubt whatsoever that each person interviewed in this book is a world-renown coder, a master of their craft.
-Nevertheless the interview format and the sometimes informal responses show that in the end they also started just like us from scratch, sometimes late in life.
-Because of this, I think the message of the book is that anyone can program, regardless of when they start or what background they are from.
-
-In this review I would like to write a short paragraph about each chapter and summarize what I think are the most important takeaways.
-
-Joshua Bloch is a Chief Java architect at Google.
-One of the interesting things that he mentions is that in his opinion there are two books any programmer should read, one of them being _The Elements of Style_, which is a book that I have known for a while.
-It is definitely a recommended read for anyone writing prose, as it contains some of the most important rules which should guide the writer towards writing clearly.
-On the topic of picking the right things to read and learn, Joshua Bloch says of programming languages: _It's like choosing a bar. You want to go to a bar that servers good drinks, but that's not the most important thing.
-It's who hangs out there and what they talk about._
-
-
-