/Best Practice

Best Practices For Managing And Storing Secrets Including API Keys And Other Credentials

- Mackenzie Jackson tl;dr: "Secrets management doesn’t have a one-size-fits-all approach so this list considers multiple perspectives so you can be informed in deciding to, or not to, implement strategies."

featured in #188

Encouraging A Culture Of Written Communication

- Maarten Claes tl;dr: As remote work becomes a normal, written communication becomes more critical. Good is the enemy of great - employees should be encouraged to write imperfectly to share ideas. Best practices are outlined here. 

featured in #183

Product For Internal Platforms

- Camille Fournier tl;dr: The role of building products for your own engineering team requires atypical product management. Camille discusses how it's unique, and her approach. 

featured in #183

Dos And Don'ts In Open Source

- Olafur Pall Geirsson tl;dr: Ólafur is a prolific contributor to OS. He tries to avoid unproductive discussions and focus on work. He outlines his dos and don'ts, applicable to both maintainers and contributors. 

featured in #177

Things I Believe

- Jan Stette tl;dr: A collection of things Jan believes about development broken down into fundamentals, code, design, quality, teams and more.  

featured in #171

Good Code Is 90% Boilerplate

tl;dr: The more code you write, the more monotonous it becomes. Some languages like Java require a lot of code to be written for little functionality. In this article there is an example of writing a Java app in a "more efficient, more enjoyable way".  

featured in #165

How Not To Store Passwords

- Paul Boyd tl;dr: Primer on how to not store passwords. While some of these may be obvious, there are interesting examples of how companies still do this incorrectly.  

featured in #163

Long Names Are Long

- Bob Nystrom tl;dr: Code at Google is reviewed for readability, engineers tend to create name that are too long & verbose. A name has two goals - clarity and precision. The author provides examples and suggestions on how to shorten and improve naming.

featured in #149

On Simplicity

- Max Böck tl;dr: Often, complex solutions are created to solve complex problems. However, this isn't always the case - "sometimes the smarter way to build things is to try and take some pieces away." Complexity can arise from the inflexibility of best practices or developers wanting to show off how smart they are. In either case customers lose out.

featured in #132

Never Feel Overwhelmed At Work Again: How To Use The M.I.T. Technique

- Sihui Huang tl;dr: M.I.T. stands for Most Important Task, a critical task that will create significant results. "Every day, create a list of 2 or 3 M.I.T.s, and focus on getting them done as soon as possible." The article details how to approach this and benefits. Are the short summaries (tl;dr sections) helpful? Please vote here

featured in #131