|
Tuesday 24th October’s issue is presented by LinearB |
 |
Engineering Metrics CEOs Love | A Free Presentation Deck
For too many engineering leaders, the most stressful part of their job isn’t a bug or a system crash. The thing they worry about most is making the case that their engineering team is positively impacting the broader company.
In this CEO-approved slide deck, you’ll find simple ways to communicate how your team is increasing engineering efficiency, all while delivering business results consistently |
|
|
Characterizing Software Developers By Perceptions Of Productivity — Abi Noda
tl;dr: “Developers are different in what they consider as a productive or unproductive workday; this study aimed to help leaders make sense of these differences.” The study found 6 types of developers and what they deemed as productive: (1) Social developers: feel productive when helping coworkers, collaborating and doing code reviews. (2) Lone developers: avoid disruptions such as noise, email, meetings, and code reviews. (3) Focused developers: feel most productive when they are working efficiently and concentrated on a single task at a time. (4) Balanced developers: less affected by disruptions. (5) Leading developers: more comfortable with meetings and emails. (6) Goal-oriented developers: productive when they complete or make progress on tasks.
Leadership Management |
 |
|
Communicate Design Tradeoffs Visually — Tim Lyakhovetskiy
tl;dr: “A goal of any written design or project proposal is to present and evaluate alternatives. However, documents that include multiple solutions can be difficult to read when the qualities of each solution are not clearly expressed. A common approach to simplifying proposals is to use “pros and cons” for each alternative, but this leads to biased writing since the pros and cons may be weighed differently depending on the reader’s priorities.” Tim shows us how to color code these tradeoffs to make it easier for readers to parse ideas.
Management Design Tips |
|
|
CTO Board Deck Template
tl;dr: For too many engineering leaders, the most stressful part of their job isn’t a bug or a system crash. The thing they worry about most is making the case that their engineering team is positively impacting the broader company. In this CEO-approved slide deck, you’ll find simple ways to communicate how your team is increasing engineering efficiency, all while delivering business results consistently
Promoted By LinearB Leadership Management |
|
|
Networking As An Introvert CTO — Vadim Kravcenko
tl;dr: (1) You go to an event. (2) Approach person, say Hi, and introduce yourself. (3) Ask questions. (4) Listen carefully and share your experiences. Keep a look out for common ground. (5) Go to 3 if the conversation feels fresh; otherwise, continue. (6) End Gracefully. Go to 2 if you’re not tired; otherwise, continue. (7) Eat some food. Leave the event. (8) Follow up with everyone you liked via email. Vadim also shares his core principles: (a) Make others feel accepted. (b) Give first, then give some more i.e. don’t make networking transactional. (c) Don’t overthink it.
Leadership Management |
|
|
|
“Quality means doing it right when no one is looking.”
— Henry Ford |
|
|
How DoorDash Standardized And Improved Microservices Caching — Lev Neiman, Jason Fan
tl;dr: DoorDash's expanding microservices architecture led to challenges in interservice traffic and caching. The article details how DoorDash addressed these challenges by developing a library to standardize caching, enhancing performance without altering existing business logic. Key features include layered caches, runtime feature flag control, and observability with cache shadowing. The authors also provides guidance on when to use caching.
Cache Scale Microservices |
|
|
Authorization Academy — Sam Scott
tl;dr: Authorization Academy is a series of (free) technical guides for building application authorization. Learn about RBAC, ReBAC, authorization enforcement, and authorization in microservices.
Promoted By Oso
Guide |
|
|
— Simon Willison
tl;dr: “Embeddings are based around one trick: take a piece of content—in this case a blog entry — and turn that piece of content into an array of floating point numbers.” Simon shows us what this looks like and argues that we can learn interesting things about the content this way - “it might capture colors, shapes, concepts or all sorts of other characteristics of the content that has been embedded.” Simon also shows us practical use cases of how this may show up.
LLM AI |
|
|
Optimism vs Pessimism In Distributed Systems — Marc Brooker
tl;dr: Marc discusses the balance between optimistic and pessimistic assumptions. Optimistic assumptions, which anticipate successful outcomes without immediate coordination, contrast with pessimistic ones that proactively coordinate to prevent potential conflicts. The author exemplifies these concepts through distributed caches, Optimistic Concurrency Control, and leases. By identifying and categorizing these assumptions, developers can better understand and optimize system behavior. DistributedSystem |
|
|
Some Miscellaneous Git Facts — Julia Evans
tl;dr: “None of these things feel super surprising in retrospect, but I hadn’t thought about them clearly before. The facts are: (1) The “index”, “staging area” and “–cached” are all the same thing. (2) The stash is a bunch of commits. (3) Not all references are branches or tags. (4) Merge commits aren’t empty.” Julia discusses each in detail.
Git |
|
|
|
Cronicle: Task scheduler with web based front-end UI.
LocalSend: OS cross-platform alternative to AirDrop.
Openv0: Generative UI component framework.
Oxc: Suite of high-performance tools for JS and TypeScript.
Penpot: OS design & prototyping platform.
|
|
Click the below and shoot me an email!
1 = Didn't enjoy it all // 5 = Really enjoyed it
1 … 2 … 3 … 4 … 5 |
|
|
|