#2 / Feb 5, 2021

On "Second Languages"

An excerpt from the Human Who Codes newsletter on how learning new programming languages can give you a better/deeper understanding of ones you already know.

Design Docs at Google

An excellent read on what to focus on (and more importantly not focus on) when writing design docs. I was somewhat anti design doc until I read this a few years ago.

On coffee break moments in a remote world

Twitter thread with interesting ideas on how to create more natural social interactions in a remote work setting. I like the TLDR provided: 1) create structure and 2) provide permission.

Some light-hearted Friday fun

The Documentation System

Some really good documentation on... documentation. πŸ“– on πŸ“– on πŸ“–

There is a secret that needs to be understood in order to write good software documentation: there isn’t one thing called documentation, there are four.

They are: tutorials, how-to guides, technical reference and explanation. They represent four different purposes or functions, and require four different approaches to their creation. Understanding the implications of this will help improve most documentation - often immensely.