Get the weekly digestSubscribe

/ THE FEED /

Read what ships.

Deep, recent reads ranked by depth and freshness.

Striperemove filterGoremove filterDropboxremove filterClear all

  1. 01Go · performance

    Better HTTP/1 connection reuse

    Failing to read an HTTP/1 response body completely prevents connection reuse, forcing clients to repeatedly pay the high cost of TCP and TLS handshakes. While developers previously had to implement complex manual body-draining logic, Go 1.27 introduces automatic asynchronous response draining in the net/http package. This improvement allows developers to simply close response bodies without worrying about connection pooling performance.

    DEPTH ■■■■■7 min read11 days ago

    Sign in to save and rate

  2. 02Dropbox · architecture

    Evolving our calendar assistant Reclaim to be AI-native without starting over

    Dropbox engineers evolved their calendar assistant, Reclaim, to support natural-language AI requests by building a custom agent platform that integrates with existing scheduling logic. They utilized a shared action system and a Preview Mode backed by Redis to ensure AI suggestions are consistent and reviewable before affecting real calendars. This approach allows the product to adopt AI capabilities without fragmenting its core architecture or duplicating functionality.

    DEPTH ■■■■■7 min read3 weeks ago

    InfrastructureMachine Learning

    Sign in to save and rate

  3. 03Go · architecture

    Arch-specific SIMD in Go

    Go 1.27 introduces the archsimd package to provide low-level architecture-specific SIMD intrinsics for amd64, arm64, and wasm without requiring assembly. The API uses sensible naming conventions, zero-cost type reinterpretation, and opaque masks to improve usability and maintainability while achieving high performance. The resulting design enables developers to write optimized vectorized code safely with proper runtime CPU feature checking and compiler optimizations.

    DEPTH ■■■■■12 min read3 weeks ago

    Sign in to save and rate

  4. 04Stripe · practice

    Why I tried to kill token billing (and why we kept it)

    The author examines the limitations of token-based billing as a customer-facing pricing model, noting that it exposes internal margins and commoditizes AI products. The company explored abandoning token billing entirely but realized its necessity for backend cost tracking and margin management. Ultimately, the piece proposes unified credits and output-based pricing as better ways to align invoices with customer value.

    DEPTH ■■■■■7 min read3 weeks ago

    Sign in to save and rate