Issue #218

22 December 2020

Issue #218
A Reading Club For Software Developers - Sign Up Here
#Management #Leadership #Culture
tl;dr: To change engineering values as a leader, you need to change what you reward and focus on. This can be slow and has negative consequences e.g. some feel their skill are less relevant. As a platform engineer, you can find tools that bake in and support the values you want to be taken seriously. 
Toxic And Woke Engineering Orgs
- Marianne Bellotti
#Leadership #Management
tl;dr: Given many tech companies push social impact ideals, Marianne feels it's important to understand internal, external and interpersonal boundaries of her reports. "It is so easy to violate or indeed completely throw out appropriate boundaries" when the cause is important.

Click on the link in this tweet if you're paywalled
#CodeReview #CareerAdvice
tl;dr: Many tips, including review your own code first, write a clear changelist description to provide context, conduct your review after your code passes all automated tests, and more. 
tl;dr: "I hope this piece helps non-mobile engineers build empathy for the type of challenges and tradeoffs mobile engineers face and be a conversation starter between backend, web and mobile teams."
tl;dr: The chance to study what goes on in the "guts of boring, everyday systems" - how Git stores data or why pip install failed - is often ignored or circumvented. However, it's helped Ben. It's become easier to track tricky bugs, learn languages and libraries by pattern-matching, improved software design skills and provided confidence in understanding complexity.

"Debugging is like being the detective in a crime movie where you are also the murderer."

- Filipe Fortes

Command Line Interface Guidelines
- Aanand Prasad, Ben Firshman, Carl Tashian, Eva Parish
tl;dr: "An open-source guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day."
End of Year Pay Report 2020
- Zuhayeer Musa, Zaheer Mohiuddin
tl;dr: "The following report examines data we've collected this year and dives into compensation at companies by level and location."
There's Always More History
- Hillel Wayne
#Javascript #Vim
tl;dr: Hillel provides explanations around two historical questions: (1) Why Vim Uses hjkl (2) Why JavaScript months start from 0. 
Here’s What People In Tech Had To Say About JavaScript When It Debuted In 1995
- Chris Brandrick
tl;dr: "Here’s what members of the tech industry had to say about little old JavaScript back in 1995."
#GitHub #IndustryTrend
tl;dr: Github releases its state of the union in three reports - work life balance, open source communities and software security.