Culture
Design Docs at Google 9 minutes read.
"As software engineers our job is not to produce code per se, but rather to solve problems." -- I like the structure presented by Malte Ubl in this post as it covers most areas you should consider to maximize understanding (of value and tradeoffs) and the adoption of your peers (where needed).
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Microsoft Analyzed Data on Its Newly Remote Workforce 10 minutes read.
The findings in this post by Microsoft is something we all feel. We need to take care of managers in our company who deal with much more pressure to build those connections and navigate daily challenges in this setup. We need to set more time to build relationships that are harder to create or nurture when people are working remotely. Yes, some companies were built like that from day 1. Most companies didn't. As we all go through it together, we can also look at it as an opportunity to change our working setup in the long run.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Your Interviews Shouldn’t Be Spoilable 4 minutes read.
I'm with Rafe Colburn on sharing with your candidates the interview structure and topics covered in each interview: "If an interview can be spoiled, it means that the answers can be memorized. Questions that can be answered by reciting a set of memorized facts are bad interview questions. Your interview questions should require people to work through problems or describe and analyze their personal experiences."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.