Tailscale is expanding from a network you configure into a platform you build with and on. The tsnet Go library lets applications embed Tailscale connectivity directly, giving each app its own tailnet identity, MagicDNS name, and automatic TLS certificates without opening ports or managing proxies. A tailscale-rs library is in pre-alpha, promising bindings for Rust, Python, Elixir, and C. On the automation side, the Tailnets API lets teams provision isolated tailnets on demand for per-customer or per-test isolation, and the same APIs power a new admin console so ACL updates, key rotation, and provisioning can be scripted rather than clicked. A new Declarative Node Sharing feature turns manual cross-tailnet sharing into GitOps-managed policy, currently available via waitlist.

Bun v1.4.2 patches two regressions introduced in v1.4.1: a bun build variable name collision that broke Elysia imports with a SyntaxError, and an AsyncLocalStorage memory leak affecting timers and promises created inside store.exit() or nested store.run(). It also fixes a worker_threads 'online' event ordering bug that caused @discordjs/ws to hang, adds CMYK/YCCK JPEG decoding support to Bun.Image, pulls in roughly 350 upstream WebKit/JavaScriptCore commits fixing Intl, TypedArray, and Proxy correctness issues, and resolves several crash and hang bugs including a rare JIT crash, a musl GC crash, a bun install panic, and a double-close file descriptor bug on Linux

Trendyol's product content team details a phased, zero-downtime migration of five 'helper bucket' datasets (2.24 billion documents across two clusters) from Couchbase to PostgreSQL to cut infrastructure costs while preserving read performance. The strategy combined dual-writes via Kafka consumers, a custom CDC-based migrator tool for historical backfill, and feature-flagged cutover of read traffic. Key production challenges included a mysterious TPS spike traced to PgBouncer's server_reset_query_always setting, a connection-limit incident causing a primary node failover, and a hidden scaling issue where PgBouncer's own horizontal autoscaling multiplied backend connections beyond expectations (20 pods × 150 default_pool_size = 3000 potential connections). Final production benchmarks showed stable P50 latency and only a brief P99 spike (200ms to 400ms) under peak load, validating the migration.

React 19.3 is now available on npm, stabilizing two previously experimental APIs: View Transitions and Fragment Refs. The new <ViewTransition> component animates elements entering, exiting, moving, or resizing using the browser's View Transition API, with support for custom animations via addTransitionType and integration with Suspense for coordinated loading of fallbacks, images, and fonts. Fragment Refs let developers attach DOM behaviors (event listeners, focus management, IntersectionObserver/ResizeObserver) to a group of sibling elements without needing a wrapper div, by passing a ref to a Fragment. React DOM adds a new browser() API to opt components out of server-side rendering when they depend on browser-only APIs, plus Trusted Types support to prevent DOM-based XSS. Server Components can now render Context directly from a 'use client' module without a wrapper Provider. The release also includes numerous other changelog items and bug fixes across react, react-dom, and react-server

A developer recounts a bug where a billing report showed bills from the wrong day due to a timezone mismatch: the frontend sent plain calendar dates (e.g. '2026-01-01') without timezone context, and the backend converted them directly to JavaScript Date objects while MongoDB stored timestamps in UTC. The core lesson is that a calendar date is not the same as a timestamp - a date needs a timezone to be meaningful, and query boundaries should be computed in the user's local timezone before converting to UTC. Also covers using half-open [start, end) ranges to avoid excluding the last day of a range, and a mental model separating calendar dates, timestamps, and local date/time.

A .NET blogger reflects on four years and 210 weekly issues of his newsletter, distilling four lessons: consistency beats brilliance, teaching accelerates learning, fundamentals (modular monoliths, domain-driven business rules, API contracts, idempotency, outbox pattern) outlast frameworks, and audience feedback sharpens thinking. He also shares his bullish stance on AI coding agents, arguing fundamentals become the review checklist for judging AI-generated code, and teases more AI-focused content ahead

A detailed guide to the strangler fig pattern for modernizing legacy systems capability by capability rather than through a big-bang rewrite. It covers how the facade layer routes traffic, the tradeoffs between dual writes and change data capture for data ownership during migration overlap, how to choose which capability to strangle first, why migrations commonly stall around 80% completion, the real infrastructure and reconciliation costs of running two systems in parallel, when the pattern is a poor fit, and how to define when a migration is actually finished versus just feature-complete

A comprehensive tutorial walks through building a REST API with Solon, an independent enterprise Java framework, starting from a basic greeting endpoint and extending it into a task management API backed by H2 and MyBatis-Flex. It covers Solon's architecture, dependency injection, configuration layering, HTTP handling, and testing with solon-test, drawing comparisons to Spring Boot concepts throughout. The example uses Solon 4.1.0, Java 21, Maven 3.9.16, and MyBatis-Flex 1.11.8, with full source code available on GitHub.