|
Friday 24th May’s issue is presented by Knock |
|
 |
|
|
|
Emotional Signposting: Why You Should Tell People How To Feel — Wes Kao
tl;dr: “If you share information that’s not obviously positive or negative, you must proactively tell people how they should feel. Give context to the information, data, or fact. If there’s even a slight chance your audience might benefit from the extra clues, I would consider using signposting. It’s super fast for you, and super helpful for them.” Wes shares examples.
Leadership Management |
|
|
An Engineering Manager Challenge — Ted Neward
tl;dr: Ted shares his answer to the following interview question: "You're the tech lead and your team is getting stretched thin. You decide to add resources but you can afford 1 senior full-stack developer or 2 junior full-stack devs. Which do you choose and why?"
Management InterviewAdvice |
|
|
The Developer's Guide To Notification System Tooling — Chris Bell
tl;dr: Chris covers: (1) The key components of a notification system and their relevant use cases. (2) An overview of the tools, frameworks, and services available when building a notification system. (3) How to put these together to make the right choice for your use case and product.
Promoted by Knock Management Guide |
|
|
No Wrong Doors — Will Larson
tl;dr: “Some governmental agencies have started to adopt No Wrong Door policies, which aim to provide help – often health or mental health services – to individuals even if they show up to the wrong agency to request help. The core insight is that the employees at those agencies are far better equipped to navigate their own bureaucracies than an individual who knows nothing about the bureaucracy’s internal function.” Will discusses how engineering orgs can implement similar policies.
Leadership Management |
|
|
|
“Trust is the glue of life. It's the most essential ingredient in effective communication. It's the foundational principle that holds all relationships.”
— Stephen Covey
|
|
|
|
Prefer Noun-Adjective Naming — Kyle Shevlin
tl;dr: Kyle uses noun-adjective naming for components, e.g., StreamCreated instead of CreatedStream. This keeps related components together alphabetically in directories and makes them easier to search for. It's a small change but can lead to better organization in a codebase.
Naming BestPractices |
|
|
|
|
Stripe's Monorepo Developer Environment — Nelson Elhage
tl;dr: “I worked at Stripe for about seven years, from 2012 to 2019. Over that time, I used and contributed to many generations of Stripe’s developer environment – the tools that engineers used daily to write and test code. I think Stripe did a pretty good job designing and building that developer experience, and since leaving, I’ve found myself repeatedly describing features of that environment to friends and colleagues.”
DevEx |
|
|
Avoid The Long Parameter List — Gene Volovich
tl;dr: “Always try to group data that belongs together and break up long, complicated parameter lists. The result will be code that is easier to read and maintain, and harder to make mistakes with.“ Gene shares examples.
Tests |
|
|
The Worst Bug We Faced At Antithesis — Will Wilson, Colin Percival
tl;dr: “It was early days at Antithesis, and we had a problem: machines kept crashing. The bug was rare. Frustratingly rare. Like, one crash every couple thousand machine-hours rare. Rare enough to trigger a giant internal debate about whether this bug was even worth fixing.”
Debugging |
|
|
Most Popular From Last Issue |
|
|
|
Amber: Programming language compiled to bash.
Cover-Agent: AI-powered automated test generation.
DeskPad: Virtual monitor for screen sharing.
Fabric: OS framework for augmenting humans using AI.
Openpanel: OS alternative to Mixpanel.
|
|
|
Click the below and shoot me an email!
1 = Didn't enjoy it all // 5 = Really enjoyed it
1 … 2 … 3 … 4 … 5 |
|
|
|
|