|
Friday 12th April’s issue is presented by Kinde |
 |
Kinde: Enterprise Ready, Without The Enterprise Bulls**t
Powerful authentication for modern applications. Loved by over 25,000 developers, including teams at Datadog, ROKT, Atlassian and Figma.
Built from the ground up using best-in-class security protocols. SOC 2, HIPAA, and ISO27001.
Serve enterprise customers with SSO, SAML, MFA, and more.
Before May 31st, enterprise customers with more than 100,000 MAU, or 3,000 MAO, get 6 months free after migration. |
|
|
Meetings For An Effective Eng Organization — Will Larson
tl;dr: "I’d like to recommend 6 core meetings that I recommend every organization start with, and that I’ve found can go a surprisingly long way. These six are split across three operational meetings, two developmental meetings and finally a monthly engineering Q&A to learn what the organization is really thinking about." Will discusses each in depth.
Leadership Management |
|
Learning To Learn — Jason Liu
tl;dr: (1) Environments matters: Identifying the right environment is crucial for learning. Changing environment can be effective. (2) Get ahead and teach: If you're able to get ahead of your peer group, you can teach them and learn from them at the same time. (3) Process vs outcome: Try to set process based goals. (4) Periodize your training: Set long time horizons and peak at the end of them. Take breaks and deload weeks. (5) Learn from people actively doing what you want to do. Ask yourself how far along they are in their journey. (6) Focus on fundamentals to avoid unforced errors.
CareerAdvice |
|
An Open Letter To Auth Providers
tl;dr: The first job of any auth company is to protect its customers – before anything else. Somewhere along the way it feels like a lot of auth providers lost sight of the thing that matters: You, their customers.
Promoted by Kinde Management |
|
How To Send Progress Updates — Slava Akhmechet
tl;dr: 15 tips, including: (1) Understand your role, and with each update add to the body of evidence that you’re a good steward in that role. (2) Add a little randomness to the cadence. (3) Know what your next update will be and work toward it. (4) Always start with a one sentence TL;DR and a 2-4 sentence recap of the overall goals of the project. (5) Within reason, deliberately engineer pleasant surprises so you can include them in your updates. And more.
Management CareerAdvice |
|
|
“Live out of your imagination, not your history.”
— Stephen Covey
|
|
|
Notes On How To Use LLMs In Your Product — Will Larson
tl;dr: “I’ve been working fairly directly on meaningful applicability of LLMs to existing products for the last year, and wanted to type up some semi-disorganized notes. These notes are in no particular order, with an intended audience of industry folks building products.” Will discusses opportunities re-configuration, combining LLMs with unsophisticated algorithms to retrieve data. And more.
Productivity LLM |
|
Notes On Git's Error Messages — Julia Evans
tl;dr: Julia discusses various strategies she’s put into place when facing an unclear error messages in Git. “I’m going to go through a bunch of Git’s error messages, list a few things that I think are confusing about them for each one, and talk about what I do when I’m confused by the message.”
Git |
|
Shell History Is Your Best Productivity Tool — Martin Heinz
tl;dr: “If you work in shell / terminal often enough, then over time the history will become your personal knowledge vault, documentation and command reference. Being able to use this personal documentation efficiently can hugely boost your productivity. So, here are a couple of tips on how to optimize your shell history configuration and usage to get the most out of it.”
Shell Tips |
|
Developing Rapidly With Generative AI — Shannon Phu
tl;dr: From the engineering team at Discord: “We break down the process of building with LLMs into a few stages. Starting with product ideation and defining requirements, we first need to figure out what we’re building and how it can benefit users. Next, we develop a prototype of our idea, learn from small-scale experiments, and repeat that process until our feature is in a good state. Finally, we fully launch and deploy our product at scale. In this post, we will dive deeper into each stage of this process.”
Productivity LLM Process |
|
|
Index Conference
Join engineers from Netflix, Uber and DoorDash at the free community conference for search and AI applications on May 16th. Talks include: Vector search and the FAISS library by Matthijs Douze, Co-creator of FAISS Homepage personalization at Netflix by Shriya Arora, Engineering Manager
Register Here |
Most Popular From Last Issue |
|
|
Aider: AI pair programming in your terminal.
Conductor: Microservices orchestration engine.
DrawDB: Database design tool and SQL generator.
Sparrow: Data processing with ML and LLM.
RAGFlow: RAG engine based on deep document understanding.
|
|
Click the below and shoot me an email!
1 = Didn't enjoy it all // 5 = Really enjoyed it
1 … 2 … 3 … 4 … 5 |
|
|
|