|
Tuesday 3rd October’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. |
|
|
Drowning In Feedback — Ed Batista
tl;dr: “A wealth of information creates a poverty of attention and a need to allocate that attention efficiently among the overabundance of information sources that might consume it.” Ed discusses the challenges leaders face in an era saturated with feedback and emphasizes the pitfalls of information overload. He critiques common organizational beliefs, such as "feedback is a gift" and the objectivity of anonymous feedback. Ed encourages leaders to self-reflect, manage their attention, and prioritize meaningful insights over sheer data volume. Ed advises leaders to create an "information ecosystem" that filters out noise, allocate dedicated time for deep reflection, and regularly assess the quality and relevance of feedback sources. CareerAdvice |
 |
|
How To Hire — Sam Altman
tl;dr: “The vast majority of founders don’t spend nearly enough time hiring. After you figure out your vision and get product-market fit, you should probably be spending between a third and a half of your time hiring. It sounds crazy, and there will always be a ton of other work, but it’s the highest-leverage thing you can do, and great companies always, always have great people.” Sam provides his hiring playbook.
Leadership Management |
|
|
A Complete Guide To Session Management In Next.js — Nick Parsons
tl;dr: “Session management is a concept that flies under the radar in most applications. It’s built into every authentication library you are using, and seamlessly allows users to stay logged in, use different tabs, and stay secure while they are using your app. But because it is abstracted away by auth systems, it’s also opaque. How does session management work to keep track of your usage? Here, we want to build session management in Next.js without using any authentication library to show you what is really happening under the hood.”
Promoted by Clerk
Guide NextJS |
|
|
Working At A Startup Vs In Big Tech — Gergely Orosz, Willem Spruijt
tl;dr: Willem, who Gergely met at Uber, share his experience and insights working as a developer, transitioning between startups and big tech companies. Willem recalls the "rapid skill development" and "direct influence" at startups, juxtaposed with the financial uncertainties and heightened stress. Big tech provided a platform for deep domain expertise, financial perks, and expansive networking, albeit with potential bureaucratic hurdles and diluted individual impact. “Doing work that results in a great performance review is not always the same work that best helps the company. And this can create pretty twisted, political situations.” CareerAdvice |
|
|
|
“Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?"
— Brian Kernighan |
|
|
Lessons From Debugging — Matt Rickard
tl;dr: (1) Reproduce with the smallest example. In the simplest environment. (2) Read and re-read the error statement. Read the stack trace. Add more logging if you don’t know where the error is thrown. (3) Change one thing at a time. (4) Divide and conquer. Sometimes that means binary search on good/bad commits. Other times isolating the problem. (5) Be open to debugging in different environments. (6) State your assumptions. (7) Get a second set of eyes on it. (8) If you're debugging some stateful code, think about _how_ you ended up at that state. A recipe that (reproducibly) gets you to that state is often the path to fixing it. (9) Look at the logs, all the logs. (10) When in doubt, start with the most recent changes, especially dependencies changes.
CareerAdvice Debugging |
|
|
Exponential Value At Linear Cost — Marc Brooker
tl;dr: “Binary search is kind a of a magical thing. With each additional search step, the size of the haystack we can search doubles. In other words, the value of a search is exponential in the amount of effort. That's a great deal. There are a few similar deals like that in computing, but not many. How often, in life, do you get exponential value at linear cost? Here's another important one: redundancy,” which Marc discusses here.
ThoughtPiece |
|
|
The Surprising Impact Of Medium-Size Texts On PostgreSQL Performance — Haki Benita
tl;dr: Haki’s article delves into the intricacies of text field sizes and their impact on PostgreSQL query performance. He classifies text fields into "small", "medium", and "large", highlighting the unexpected performance implications of medium-sized texts. Through the lens of PostgreSQL's TOAST mechanism, which compresses and/or breaks up large field values, Haki demonstrates that medium texts can sometimes lead to slower queries than even larger texts. "The main problem with medium-size texts is that they make the rows very wide," affecting performance due to increased IO. PostgreSQL Performance |
|
|
Wifi Without Internet On A Southwest Flight — James Vaughan
tl;dr: “I was on my way home from Strange Loop, a direct flight from St. Louis to Oakland. It’s a long enough flight that I planned to purchase the $8 internet access and get some work done, but Southwest’s wifi portal wouldn’t accept any form of payment. The web page didn’t give me any helpful error messages, so I opened up my browser’s network dev tools to see if I could figure out what was going wrong.”
Entertaining |
|
|
Autogen: Enable Next-Gen LLM apps.
Bruno: OS IDE For exploring and testing apis.
LocalStack: Fully functional local AWS cloud stack
Openpilot: OS driver assistance system.
Streamlit: Turn data scripts into shareable web apps.
|
|
Click the below and shoot me an email!
1 = Didn't enjoy it all // 5 = Really enjoyed it
1 … 2 … 3 … 4 … 5 |
|
|
|