Read what ships.

01Grab · architecture

App stability at scale with a layered defense

To maintain app stability amidst rapid weekly releases and AI-generated code, Grab uses a layered defense strategy covering prevention, release gates, and incident response. This pipeline includes static analysis via custom lint rules, multiple tiers of automated and manual testing, a pre-production early access build, staged rollouts, and feature flags with instant kill switches. As a result, critical defects are caught early in the development lifecycle before reaching the wider production user base.

DEPTH ■■■■■16 min read4 days ago

MobileReliability

Sign in to save and rate

02Go · 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

03Grab · architecture

Powering AI-led research through simulation

The engineering team built a self-contained simulation platform called sim-rs to model marketplace dispatch dynamics and accelerate experimentation. By connecting automated software agents to this simulator with strict safety safeguards, the team successfully optimized strategy policies and simulator performance. This closed-loop lab environment allows agents to test ideas rapidly while ensuring that only valid, production-ready improvements are produced.

DEPTH ■■■■■10 min read2 weeks ago

Machine Learning

Sign in to save and rate

04Go · 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

05Tailscale · tutorial

It's time to make your own RSS reader

This post walks through the process of self-hosting a personal RSS reader using FreshRSS and Docker, secured privately over a Tailscale network. The author details the configuration of environment variables, auth keys, and Docker compose deployment to avoid exposing the service to the open web. The result is a private, algorithm-free news reader accessible across multiple devices and integrable with external reading apps or AI agents.

DEPTH ■■■■■10 min read9 days ago

Sign in to save and rate

06Tailscale · architecture

Your agent, your network: How Meta’s Muse agent works with Tailscale

Meta integrated Tailscale into its Muse personal AI agent, allowing the agent to join a user's tailnet as a separate node and interact with self-hosted services and SSH sessions. By treating Muse like any standard tailnet node, users can apply Tailscale's access controls, grants, and tags to enforce security and adhere to the principle of least privilege.

DEPTH ■■■■■5 min read3 weeks ago

Sign in to save and rate

07Grab · architecture

Smarter personalization: How property data helps us understand user price sensitivity

Existing user personalization systems fail to systematically account for residential property values, leading to one-dimensional profiles and regional blind spots. A conceptual four-step method is proposed that combines public property data, large language models, building-level price estimation, and hierarchical clustering to classify user affluence. The approach remains unimplemented, with future viability depending on technical validation, data quality, and privacy approvals.

DEPTH ■■■■■4 min read2 weeks ago

Data EngineeringMachine Learning

Sign in to save and rate

08Grab · architecture

Data Mesh at Grab (Part III): Operationalizing data reliability with automated DPIs

Grab addressed runtime data reliability issues in its data mesh by implementing automated Data Production Issues (DPIs). The system uses an incident orchestrator to detect contract breaches, a Data Health API for cross-platform root cause analysis, and Hugo for automated remediation. This approach resolved 86.9 percent of incidents automatically and made mean time to resolve six times faster.

DEPTH ■■■■■12 min read8 weeks ago

DatabasesObservability

Sign in to save and rate

09Grab · architecture

Automated merchant review summary system with integrated feedback

To help users navigate large volumes of unstructured merchant reviews, the engineering team built an automated review summary system using representative sampling, large language models, and automated quality control checks. The pipeline generates overall and topic-based summaries while incorporating maintenance triggers based on new review counts and consumer feedback. This approach reduces the text consumers need to scan while ensuring claims remain grounded in source data.

DEPTH ■■■■■5 min read4 weeks ago

Machine Learning

Sign in to save and rate

10Grab · architecture

GrabMart data for faster disease outbreak detection

The organization proposes a conceptual data pipeline to analyze aggregated GrabMart transaction data for symptom-related product demand, aiming to supplement clinical surveillance for disease outbreaks. The design relies on data aggregation, statistical baseline comparisons, and privacy safeguards like differential privacy without involving individual health inference. The system remains in an early planning phase requiring rigorous validation, privacy review, and public health oversight.

DEPTH ■■■■■5 min read12 days ago

Data EngineeringMachine Learning

Sign in to save and rate