TLDR Index
Daily Editions
Contents
  1. Page 1: Today’s IndexTLDR AI, TLDR Web Dev, TLDR Crypto · 9 stories
  2. Page 2: TLDR AITLDR AI · 5 stories
  3. Page 3: TLDR Web DevTLDR Web Dev · 12 stories
  4. Page 4: TLDR CryptoTLDR Crypto · 10 stories
  5. Page 5: Resources & ToolsTLDR AI, TLDR Web Dev · 6 stories
?
Keyboard shortcuts
← / →
Previous / next page
↑ / ↓
Scroll while full screen
PgUp / PgDn
Scroll by viewport
Space
Scroll down by viewport
Shift+Space
Scroll up by viewport
Home
First page
End
Last page
F
Full screen
Escape
Exit immersive mode

Daily Edition · Page 3

THE DAILY INDEX

Technology, AI, software, security, crypto and business

ARTICLES & TUTORIALS

TLDR Web Dev

TLDR Web Dev

MIGRATING NETFLIX TO GRAPHQL SAFELY

Netflix migrated their mobile apps to GraphQL in 2022. This was done with zero downtime and involved a total overhaul from the client to the API layer. Doing this safely for 100s of millions of customers without disruption was exceptionally challenging, especially considering the many dimensions of change involved. This blog post shares the broadly-applicable techniques (beyond GraphQL) Netflix used to perform this migration. The three strategies discussed are AB Testing, Replay Testing, and Sticky Canaries. Netflix first created a new GraphQL service over the previous legacy monolith API endpoints. It then deprecated both the service and legacy API in favor of GraphQL services owned by the domain teams.

netflixtechblog.com · 8 min

TLDR Web Dev

HOW WE SPED UP SEARCH LATENCY WITH SERVER-SENT EVENTS IN EXPRESS.JS

Using HTTP to query for a search works, but it's not the most optimal UX if your query takes a long time. Users have to wait for the entire search to complete, which can take up to 30 seconds for sparse queries that are not requested often. A better UX would be to stream responses as you query, which can be accomplished with Server-sent events (SSE). This article explains how SSE works, how it differs from traditional web sockets, and how you can integrate it in Express.js.

hyperdx.io · 3 min

TLDR Web Dev

SPEED MATTERS: WHY WORKING QUICKLY IS MORE IMPORTANT THAN IT SEEMS

The obvious benefit to working quickly is that you’ll finish more stuff per unit time. But there’s more to it than that. If you work quickly, the cost of doing something new will seem lower in your mind, so you’ll be inclined to do more. Google famously prioritized speed as a feature. They realized that if search is fast, you’re more likely to search. The reason is that it encourages you to try stuff, get feedback, and try again. Working fast ends up implicitly lowering the activation energy to do new tasks, which means you get more done and try more things.

jsomers.net · 4 min

TLDR Web Dev

MY TAKE ON A UNIFIED THEORY OF REACTIVITY

Reactivity is an important feature of front end frameworks. There are a number of ways to provide this functionality. This post summarizes the three ways frameworks today provide reactivity: value-based (think states in React), observables-based (through subscriptions), and signal-based (which is close to observables-based, but without the need to subscribe/unsubscribe). It discusses the pros and cons of each reactivity model and a hot take on why signals are the best model out of the three.

builder.io · 7 min

TLDR Web Dev

ALWAYS THE SAME WARNING SIGNS

Promising stories like that of Theranos and FTX have ended with the discovery of fraud. But how were investors and so many others fooled by the founders of these companies? Each company had warning signs that were similar and when these warning signs came up, they deserved much more scrutiny than they actually got. For example, if it seems like only one person can get this company to work and/or if a lot of important data is missing or kept secret, then it might be a sign to take a closer look at the company.

science.org · 3 min

TLDR IndexPage 3