rcmnd

Writing Solid CodeBook

by Steve Maguire

Who uses, recommends or left Writing Solid Code, in their own words: each a verbatim quote with a link to where it was said.

1 person

Software engineer working on distributed systems and databases; creator of the rqlite distributed SQLite database.
liked

This book had a big impact on me as young software developer. It was the first time I saw in print the principle "bugs that go away by themselves come back by themselves". It's something that I've often repeated to myself, and my team, if nothing else but to prepare us mentally for when that hard bug does come back. The chapter advising developers to "proactively step through your code during development, don't wait for the bug report" improved my productivity enormously, and I followed the practice for many years.

A post written after colleagues asked him which programming books had shaped him most.

2016-11-25·philipotoole.com ↗

Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.

The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.

A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.

The shading behind a date shows how dated a recommendation is for its kind of thing.

The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.

What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The shading is gone after about:

Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.