summaryrefslogtreecommitdiffstats
path: root/content/lit/97-things
diff options
context:
space:
mode:
Diffstat (limited to 'content/lit/97-things')
-rw-r--r--content/lit/97-things/97-things-cover.webpbin0 -> 64412 bytes
-rw-r--r--content/lit/97-things/index.en.md43
2 files changed, 43 insertions, 0 deletions
diff --git a/content/lit/97-things/97-things-cover.webp b/content/lit/97-things/97-things-cover.webp
new file mode 100644
index 0000000..6509e2c
--- /dev/null
+++ b/content/lit/97-things/97-things-cover.webp
Binary files differ
diff --git a/content/lit/97-things/index.en.md b/content/lit/97-things/index.en.md
new file mode 100644
index 0000000..f8e1592
--- /dev/null
+++ b/content/lit/97-things/index.en.md
@@ -0,0 +1,43 @@
++++
+title = "97 Things Every Programmer Should Know"
+date = 2020-06-13
+
+[taxonomies]
+tags = ["programming"]
+
+[extra]
+author = "harald"
++++
+
+{% figure(img="97-things-cover.webp") %}
+_97 Things Every Programmer Should Know_ cover
+([CC BY-SA v3.0](http://creativecommons.org/licenses/by-nc-sa/3.0/))
+{% end %}
+
+As the title suggets, this is a book filled with pretty obvious advice for
+programmers. That is not the same as to say it's not worth reading though. On
+the contrary: I like this book, and think it is a good addition to any
+programmers bookshelf.
+
+<!-- more -->
+
+Each advice is self contained, short and to the point. Most are well written,
+and together they cover topics like code style, handling exceptions, design
+issues, choosing your tool, advancing your craft and perhaps most importantly –
+social aspects of being a professional developer.
+
+With well known names like Kevlin Henney (editor of the book), Robert Martin,
+Walter Bright, Scott Meyers, Michael Feathers and many more, the book ranges
+from "you know what you get" to the occational a-ha moments of things you never
+thought about.
+
+While not quite as indispensable as "The Pragmatic Programmer", I feel this
+book easily fits along side it on the bookshelf next to your bed. Flip trhough
+it every now and again, read a passage or two to remind yourself of some of the
+points it makes.
+
+The contents of the book has an open license, and is also available as [a
+gitbook] where you can either read it online, or download it in a suitable
+format for you.
+
+[a gitbook]: https://legacy.gitbook.com/book/97-things-every-x-should-know/97-things-every-programmer-should-know/details