Save Your Engineers' Sleep: Best Practices For On-call Processes
tl;dr: 8 best practices shared including: (1) Alerts are treated as code i.e. go through code reviews, generated from existing modules. (2) Use percentiles over averages to get a higher quality signal. (3) Use playbooks to document each alert so there is corresponding documentation that explains what is broken and how to investigate and fix it.
featured in #274
The Developer’s Guide to SSO
tl;dr: Single-sign-on via SAML or oAuth is often one of the first features an engineering team needs to build as a product gains traction among larger customers. We explore how it works, how to add it to your app, and best practices for implementation.
featured in #265
Engineering Onboarding - Built to Scale
tl;dr: Management at Robinhood rebuilt their engineering onboarding process around 3 key themes: learning experience, community building, and purposeful team matching, each outlined here.
featured in #264
Use Cases: The Purpose Of Your Code
tl;dr: Use cases are the very entry points to the application domain, they describe how domain actors interact with the application. They're the first place to look to understand the purpose of the application, the domain, and all the business rules it supports. They can be a great benefit to the sustainability of your code, which Joe explains here.
featured in #263
What Makes A Good Changelog
tl;dr: Changelogs are a must for developer tooling. We explore 5 important aspects of a good changelog, from images to formatting, and how to customize your changelog to communicate effectively to your users.
featured in #252
Your E-Mail Validation Logic is Wrong
tl;dr: There's are lots of nuances validating addresses that are not accounted for. Jan highlights 13 examples, such as email addresses can contain multiple @s, punctuation character are allowed, bang paths can be accepted, the percent sign may lead to relaying, and more.
featured in #233
A Survey Of Git Best Practices
tl;dr: David researched articles around Git best practices for a work presentation and collated the most frequently practices, in this post.
featured in #204
Very Short Functions Are A Code Smell – An Overview Of The Science On Function Length
tl;dr: "Considering that short functions tend to lead to longer debug times and that very short functions tend to have higher defect densities (both in historical and modern datasets) the case for using very short functions becomes weak."
featured in #203
Best Practices For Setting SLOs And SLIs For Modern, Complex Systems
tl;dr: A framework for SLIs and SLOs, Elisa concludes with 6 things to remember, including (1) define SLIs and SLOs for specific capabilities at system boundaries. (2) Each logical instance of a system (for example, a database shard) gets its own SLO.
featured in #202
Write Good Commit Messages
tl;dr: "Focus on the intent of the change, not the mechanics. Why was this change needed? What drove it? What would you want to know about this reasoning or decision a year from now? What would you want a new team member approaching this code base to know?"
featured in #196