|
Friday 8th December’s issue is presented by Clerk |
 |
Authentication & User Management For The Modern Web
Clerk is the easiest way to add authentication and user management to your app.
With prebuilt UI components and feature-rich SDKs & APIs, Clerk is purpose-built for the React, Next.js, and the modern web, and designed to get developers up and running in minutes. |
|
|
Writing Is Thinking — Andrew Bosworth
tl;dr: Andrew gives us tips on writing, leading with: "I believe in this concept so completely that I’ll take the importance of writing a step further: I find it valuable to write even if only for my own benefit. Writing is a linear process that forces a tangle of loose connections in your brain through a narrow aperture exposing them to much greater scrutiny. In my experience, discussion expands the space of possibilities while writing reduces it to its most essential components."
CareerAdvice |
 |
|
First Decide How To Decide: “One Weird Trick” For Easier Decisions — Jacob Kaplan-Moss
tl;dr: "The heart of this process – the move that I think makes it work so well – is that it includes an explicit step to first decide how to decide. That is: when a decision appears that it’ll be controversial or difficult to make, instead of immediately starting to discuss the matter at hand, the stakeholders first come to an agreement about how they’ll eventually decide. In fact, this happens twice: first at the macro scale when the organization agrees to adopt this process overall, and then in the micro scale, for each individual decision." Jacob discusses an example.
Leadership Management |
|
|
Clerk Quickstart Guides
tl;dr: A comprehensive set of guides and tutorials designed to help developers implement authentication and user management features into a range of applications including Next.js, React, Remix, Gatsby and others.
Promoted by Clerk BestPractices Guide |
|
|
New Engineering Managers Have A High Failure Rate — This Figma Leader Is On A Mission To Fix It — Marcel Weekes
tl;dr: Marcel discusses the context and solutions to three common problems he sees when engineers transition from IC to management roles: (1) The best-suited folks aren’t the ones elevated to management. (2) New managers fall into a spiral that never pulls them out of IC work. (3) Managing former peers can be just plain awkward. Leadership Management |
|
|
|
“Beware of 'obvious'; it often means "I haven't thought carefully about it"
— Bjarne Stroustrup |
|
|
How Google Takes The Pain Out Of Code Reviews, With 97% Dev Satisfaction
tl;dr: The author discusses: (1) Google’s guidelines for efficient code review. (2) Critique, Google’s code review tooling, and AI-powered improvements. (3) Internal statistics on Google code reviews. (4) Why Critique seems to be so loved by Googlers. Google’s guidelines for a good code review include: continuous improvement over perfection, maintain or improve the health of the codebase, and more.
BestPractices |
|
|
Platform Teams Have Too Many Tools
tl;dr: There’s a new wave of platform tools and understanding what they are, when to use them, and how they differentiate is challenging. What’s a cloud development environment? How do you use platform orchestrators and Kubernetes? What does IDP even stand for? And how does all of this fit into a platform strategy?
Promoted by Gitpod Platform Event |
|
|
Data Quality Score: The Next Chapter Of Data Quality At Airbnb — Clark Wright
tl;dr: "With 1.4 billion cumulative guest arrivals as of year-end 2022, Airbnb’s growth pushed us to an inflection point where diminishing data quality began to hinder our data practitioners. Weekly metric reports were difficult to land on time. Seemingly basic metrics like “Active Listings” relied on a web of upstream dependencies. Conducting meaningful data work required significant institutional knowledge to overcome hidden caveats in our data." Clark discusses the implementation of a Data Quality Score.
Scale Data |
|
|
Exceptional Exception Handling — Yiming Sun
tl;dr: Have you ever seen huge exception-handling blocks that throws an exception? Yiming shows an example and highlights the core problems: (1) It obscures the logic so unintended exceptions may be caught. (2) The code might end up catching different exceptions. (3) It rethrows a general exception, with the original exception ignored. This means that the root cause is lost - we don't know what exactly goes wrong. Yiming shows a better way to handle errors.
Antipattern Tips |
|
|
Mounting Git Commits As Folders — Julia Evans
tl;dr: "The main reason I wanted to make this was to give folks some intuition for how git works under the hood. After all, git commits really are very similar to folders – every Git commit contains a directory listing of the files in it, and that directory can have subdirectories, etc... It’s just that git commits aren’t actually implemented as folders to save disk space. So in git-commit-folders, every commit is actually a folder, and if you want to explore your old commits, you can do it just by exploring the filesystem!"
Git |
|
|
Fleece: JSON-equivalent binary data format.
Stylex: Styling system for ambitious user interfaces.
SuperDuperDB: OS framework for integrating AI with your database.
TaskWeaver: Agent for planning and executing data analytics tasks.
Wing: OS language designed for the cloud.
|
|
Click the below and shoot me an email!
1 = Didn't enjoy it all // 5 = Really enjoyed it
1 … 2 … 3 … 4 … 5 |
|
|
|