Issue #537

Issue #537


Friday 2nd August’s issue is presented by Speakeasy

Integrate API Users Up To 50% Faster


Slow API integrations can block revenue streams. Great SDKs solve this problem but tend to be very resource-intensive.


Speakeasy’s platform makes crafting type-safe, idiomatic SDKs for enterprise APIs easy.


Make SDK generation part of your API’s CI/CD and distribute libraries that users love at a fraction of the cost of maintaining them in-house.

Managing Underperformers

— Jack Danger


tl;dr: “There are two fully unrelated causes of underperformance: Refusal to Align and Failure to Execute. Underperformance is when a person or a team is not bearing their share of the organization’s load. Their colleagues are either relying on them and getting let down, or they’ve learned not to rely on them at all.”


Leadership Management

Advice To The Young

— Murat Demirbas


tl;dr: (1) It is called foundations, not theory. (2) Keep your hands dirty, your mind clean. (3) Ship something, anything, weekly. (4) Cram for the deadlines, put your heart into it. (5) Ask and you shall receive. (6) People skills are very important. (7) Manage the stories you tell yourself. (8) Cultivate deep focus through deliberate practice.


CareerAdvice

Everything You Need to Know About OpenAPI


tl;dr: API design is important, yet it is only useful if it's well-documented and consistently represented across every API surface area (docs, SDKs, etc.). OpenAPI gives you greater visibility into your API, enabling you to unify all aspects of errors, responses, and parameters, ensuring consistency. This open-source documentation project will help you understand the OpenAPI Specification.


Promoted by Speakeasy

API

Management at Pivotal - Draft

— Nat Bennett


tl;dr: “It gets weirder: Not only is your manager on a different team, back on his team he's just a regular engineer, pairing in with the other engineers. He's probably not even that team's lead. Pivotal did a lot of things differently, but it did management really differently. Let's break it down.”


Leadership Management


“A language that doesn’t affect the way you think about programming is not worth knowing.”


— Alan Perlis


How I Computer In 2024

— Jon Seager


tl;dr: “I’m always fascinated to see how people use their computers - which applications they choose, how they set up their desktop environments and even how their screens are laid out on their desk. I’ve learned some great tricks from friends and colleagues over the years, so I thought I’d write up how I use my machines in 2024.”


Guide

Hiring (And Managing) Cracked Engineers

— Charles Cook


tl;dr: When we say cracked, we mean people who: (1) Take extreme ownership of ideas. (2) Stay optimistic at all times. (3) Make people feel excited and energized. (4) Behave in a completely authentic way. (5) Apply themselves to the craft. Charles outlines how to manage such reports. 


Promoted by PostHog

Guide

9 Software Architecture Patterns For Distributed Systems


tl;dr: “Architectural patterns provide proven solutions to common problems encountered in distributed systems, ensuring reliability, scalability, and maintainability. Among these patterns, some patterns stand out as fundamental for managing data and communication flow effectively, which we will see in this article.”


DistributedSystem

Faster Continuous Integration Builds At Canva


tl;dr: In April 2022, the average time for a PR to pass continuous integration and merge into our main branch was around 80 minutes. As shown in the following diagram, we’re now getting our build times down below 30 minutes, as low as 15 minutes. This post shares what we’ve done to improve CI build times in our main code repository, including: (1) Finding the best opportunities (2) Experimentation (3) Deliver fast and incrementally (4) The importance of everyone’s contributions. 


Infrastructure

How To Review Code Effectively: A GitHub Staff Engineer’s Philosophy

— Sarah Vessels


tl;dr: “Over the past eight years, I’ve reviewed more than 7,000 pull requests. Why so many? Because code review is crucial to building good software and another set of eyes can often spot issues you would have otherwise missed.” Sarah discusses how to (1) Fine-tune your code review process. (2) What makes a code review good or bad? (3) How to give a good code review. (4) How to get the most out of code reviews. 


CodeReview

Most Popular From Last Issue

Notable Links


DiceDB: Redis Replacement with SQL-based real-time reactivity.


FastHTML: Next-gen web framework.


GrapesJS: Free & OS web builder framework.


Porffor: JS engine.


Sniffnet: Monitor Internet traffic.


Click the below and shoot me an email!


1 = Didn't enjoy it all // 5 = Really enjoyed it


12345