Loading…
Latest reads
Every post, summarised
Grounded summaries of engineering blogs, newest first. Each links to the original.
- 4,671 posts
- 20 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Latest posts
2026 customer service planning series: Vol. 05
AI-first customer service makes capacity planning less predictable because automation changes volume, work mix, human responsibilities, and performance over time. The proposed planning model puts automation rate—AI Agent involvement rate multiplied by AI Agent resolution rate—alongside inbound volume, human output for complex remaining work, and occupancy. It recommends ambitious automation assumptions only when backed by named ownership, content and systems investment, work-type targets, and staged improvement, while modeling lower cases closed per person and more time for off-queue work. Finance should treat the plan as a revisable set of assumptions, review it at least quarterly, and avoid cutting headcount before automation is proven. Surplus capacity should be redirected to AI improvement, product feedback, new channels, or proactive customer experience work rather than automatically reduced.
From Python3.8 to Python3.10: Our Journey Through a Memory Leak
During an initiative to upgrade Python services from version 3.8 to 3.10, Lyft engineers encountered severe latency spikes and timeouts in one service within their test environment. Profiling DynamoDB queries revealed that gevent thread joins were taking up to 30 seconds while pod memory consumption climbed steadily. To isolate the issue, engineers used an internal tracemalloc-based profiler triggered via SIGUSR2 signals, temporarily disabling Gunicorn preload to prevent workers from terminating prematurely on signal receipt. Memory traces pointed to botocore and an incompatibility between weakref.finalize and gevent monkey patching in urllib3 version 1.26.16, which prevented connections from returning to the pool. Downgrading urllib3 to version 1.26.15 immediately resolved both the timeouts and the memory leak before a permanent fix arrived in gevent and urllib3 updates.
CUGA on Hugging Face: Democratizing Configurable AI Agents
Many existing AI agent frameworks suffer from brittleness, tool misuse, and failures when executing complex workflows. To address these limitations, the open-source Configurable Generalist Agent (CUGA) introduces structured orchestration that decomposes user goals into programmatic subtasks tracked by a dynamic task ledger. The framework integrates agentic patterns like planner-executor and code-act, delegating subtasks to specialized agents that generate pseudo-code before running execution in a secure sandbox. Released under the Apache 2.0 license, CUGA integrates with Langflow for low-code visual workflow assembly and supports multi-tool environments through OpenAPI specs, MCP servers, and LangChain. Testing on inference platforms like Groq with open models such as gpt-oss-120b demonstrates rapid response times during multi-step planning and validation.
How we made Notion available offline
Notion's Offline Mode required turning a best-effort SQLite cache into storage that could guarantee a page and all its dependent records were available without a network connection. The system uses a forest of offline page trees backed by offline_page and offline_action tables, allowing independent reasons such as explicit toggles, favorites, automatic downloads, and inheritance to coexist while preserving hierarchy. To keep content current, clients subscribe to push channels emitted by the page version snapshot system, then use lastDownloadedTimestamp and server lastUpdatedTime to fetch only newer pages after reconnecting. When pages or databases change, the client reconciles fresh page and database snapshots with offline_action, adding or removing rows rather than rebuilding entire trees. This makes offline availability precise and eventually consistent, while supporting conflict resolution through the CRDT data model.
New in llama.cpp: Model Management
llama.cpp server now includes a router mode that enables dynamic loading, unloading, and switching between multiple LLMs without restarting the server. The architecture runs each model in an isolated process to ensure a single model crash does not affect other active instances. Running llama-server without specifying a model activates auto-discovery across the cache directory or a designated folder of GGUF files. In addition to on-demand loading and least-recently-used eviction capped by default at four models, the server provides endpoints for manual loading, unloading, and listing model statuses. Models inherit global configuration options or use dedicated configuration presets while also integrating directly into the built-in web UI.
Litestream VFS
Litestream VFS lets SQLite query a Litestream-backed database directly from object storage, including historical states selected with SQL pragmas, without first downloading the complete database. It is a loadable SQLite VFS plugin: Litestream v0.5 uses the LTX data-shipping format, whose compaction removes superseded page versions, while index trailers map database pages to remote file offsets. The VFS fetches only requested page ranges through S3, uses an LRU cache, and can poll second-level L0 backups to maintain a near-realtime replica. Writes remain handled by the regular Litestream Unix program, and the existing SQLite library is unchanged. The result is fast querying and instantaneous point-in-time recovery from arbitrary relative or absolute timestamps, while the optional VFS preserves Litestream’s conventional backup and restore workflow.
A visual editor for the Cursor Browser
Cursor has released a visual editor for its Browser that combines a web app, codebase, and visual editing tools in one window. Users can drag rendered elements across the DOM tree, inspect React component props, adjust styles and design-system color tokens, and interactively test layout, typography, and component variants. Point-and-prompt interactions let users select interface elements and describe changes such as resizing, recoloring, or reordering; agents run these prompts in parallel and make changes live within seconds. Once a visual arrangement is settled, the agent locates relevant components and updates the underlying code. The release positions the editor as a way to connect visual design and coding more directly, with features documented for Cursor 2.2.
Codex is Open Sourcing AI models
Hugging Face Skills equips AI coding agents like OpenAI Codex to execute end-to-end machine learning workflows. By reading AGENTS.md files and interfacing via the Model Context Protocol, Codex automates dataset validation, training script updates, and job submissions to Hugging Face Jobs. The workflow supports methods including supervised fine-tuning, direct preference optimization, and reinforcement learning for models ranging from 0.5B to 7B parameters. Throughout execution, Codex tracks live metrics via Trackio, records benchmark evaluations against baselines, and maintains Markdown reports. Once training concludes, Codex merges LoRA adapters, applies GGUF quantization, and publishes the resulting models to the Hugging Face Hub for local deployment.
LinkedIn Groups Guide: Find, Join, and Create
LinkedIn Groups bring professionals and businesses together around shared interests, industries, and goals, offering more targeted discussions than the main feed. The guide explains how to search for groups by keyword or name, filter results, assess activity and post quality, review rules, and join instantly or request approval from an admin. It also outlines group creation through the For Business menu, covering names, descriptions, images, industries, locations, privacy, rules, and member permissions. Public and private status is fixed after creation, while private groups can be listed or unlisted, with unlisted groups requiring an existing member’s invitation. To sustain participation, owners are advised to invite relevant connections, welcome members, respond promptly, moderate posts, and encourage valuable discussions; contributors should prioritize useful content, professional conduct, and relationship building.
Introducing Debug Mode: Agents with runtime logs
Debug Mode is an agent loop for coding bugs that combines runtime information with human verification, addressing issues that can stump conventional coding agents. After the user describes a bug, it reads the codebase, proposes multiple hypotheses, and instruments the code with logging statements designed to test them. The user reproduces the issue while the agent collects variable states, execution paths, and timing information, then uses those logs to identify a root cause and produce a targeted fix, often a two- or three-line modification. The user reproduces the bug again with the fix; if it works, the agent removes its instrumentation, while a failed verification prompts additional logging and refinement until the user considers the problem solved.
Versioning in Stripe Workflows: Ship workflow changes with confidence
Stripe Workflows previously required teams to edit live workflow definitions directly, leaving no draft state, historical definitions, straightforward rollback, or reliable way to inspect which configuration shaped an older run. Versioning addresses this with a dedicated draft for iteration, immutable numbered published versions, and version history that can include descriptions, authors, status, and run counts. Publishing creates a complete snapshot containing steps, branches, conditions, variable references, calls, and configuration; new runs use it immediately, while in-progress runs finish on the version they started with. Each run records its exact version and exposes the workflow definition, including taken and untaken branches, while a past version can seed a new draft for rollback; versioning is available in Stripe Workflows, where new workflows include a draft by default.
2026 customer service planning series: Vol. 04
After defining team roles, an operating model is needed to make progress part of customer-support work and keep an AI Agent improving over time. The stated goal is that “the first time you answer a question should be the last,” with each resolution improving the system so fewer issues repeat, quality compounds, and support scales. The post emphasizes clear ownership, risk-aware guardrails, feedback loops, and a culture that values improvement work; it identifies ambiguity as a common cause of performance plateaus. An AI ops lead, often located in support operations or developed from an existing role, owns performance and drives change, illustrated by Dotdigital’s dedicated specialist after resolution volume held at about 2,800 conversations per month for three months; lightweight governance is presented as a way to keep iterating without excessive bureaucracy.
Setting the standard for support: What Spain’s new customer service law signals
Spain’s proposed customer service law would impose stricter requirements on regulated providers and sufficiently large companies, covering response times, human access, complaint handling, accessibility, and auditability. It would require 95% of support calls to be answered within three minutes, free lines, 24/7 support for continuity issues in essential services, and complaints resolved within 15 days or five days for undue charges. The source also describes protections against spam calls, centralized complaint records, multilingual support obligations for some large companies, and simpler subscription cancellation. It presents AI Agents such as Fin as a way to reduce avoidable volume, answer calls, preserve human escalation, structure complaints, communicate outages, and support reporting. The stated conclusion is that early modernization may ease pressure on human teams while helping organizations adapt to rising regulatory and customer expectations.
Intercom achieves AIUC-1 certification: A new standard for trust in AI Agents
Intercom announces that it has achieved AIUC-1 certification, describing it as the first standard designed specifically for AI Agents. The certification complements broader frameworks such as ISO 42001 and addresses enterprise concerns spanning security, customer safety, system reliability, data and privacy, society, and accountability. Organizations seeking AIUC-1 undergo independent third-party audits and quarterly adversarial testing across more than a thousand enterprise risk scenarios, while the standard itself evolves quarterly through the AIUC-1 Consortium. Intercom says the certification extends its governance approach to Fin, its AI Agent, providing independent validation that its AI systems are safe, resilient, regularly tested, safeguarded, and enterprise-ready; it also identifies Intercom as a founding technical contributor to the standard.
MediaTek NPU and LiteRT: Powering the next generation of on-device AI
MediaTek’s diverse NPU hardware and specialized compilation requirements have made on-device AI deployment difficult, especially for sophisticated generative models. The LiteRT NeuroPilot Accelerator, described as a ground-up successor to the TFLite NeuroPilot delegate, provides a unified API over MediaTek NPUs and supports both offline Ahead-of-Time (AOT) and on-device compilation. Its workflow can compile models for target SoCs, package Android assets and runtimes for Google Play’s Play for On-device AI, and invoke NPU inference through LiteRT with GPU or CPU fallback options. A new C++ API and Native Hardware Buffer Interoperability enable zero-copy transfers from AHardwareBuffer and OpenGL/OpenCL buffers, supporting real-time camera and video pipelines. On supported MediaTek chipsets, listed Gemma and Qwen models receive NPU-specific optimizations; the post reports up to 12x CPU and 10x GPU acceleration, including over 1600 tokens/sec prefill and 28 tokens/sec decode for Gemma 3n E2B.
Tangle: An open-source ML experimentation platform built for scale (2025) - Shopify
Shopify introduces Tangle, an open-source, platform-agnostic machine-learning experimentation platform built for Search and Discovery workflows at commerce scale. It targets six stated failure modes, including repeated data preparation, poor reproducibility, slow deployment, unstructured notebooks, manual query tracking, and limited sharing. Users compose visual directed acyclic graph pipelines from reusable YAML components that wrap containerized or inline command-line programs in multiple languages, while file-based execution moves artifacts through storage. Tangle’s content-based caching reuses results when output content hashes remain identical, including artifacts from still-running executions, rather than relying only on lineage changes. Shopify reports a ten-hour pipeline completing in twenty minutes after one component changes, more than a year of compute time savings, and production use across ranking, semantic search, recommendation, and feature engineering workloads.
Introducing swift-huggingface: The Complete Swift Client for Hugging Face
Hugging Face released swift-huggingface, a dedicated Swift package offering complete Hub API integration, reliable file downloads, and inference provider access. The library addresses previous limitations in swift-transformers 1.0, where interrupted multi-gigabyte model downloads could not resume and cache structures differed from Python. To resolve cache duplication, swift-huggingface implements a Python-compatible content-addressed storage layout using symlinks and flock file locking. Authentication is standardized through a TokenProvider pattern supporting auto-detection, Keychain integration, static CI/CD tokens, and OAuth 2.0 sign-in with automatic token refresh. The package also provides URLSession-backed snapshot downloads with granular progress tracking and will soon replace the HubApi implementation inside swift-transformers.
PaaS + IaaS: Heroku and AWS for Cloud-Native Enterprise Agility
Modern enterprises can combine AWS IaaS infrastructure scale with Heroku’s managed PaaS to reduce operational work and developer cognitive load while retaining control for specialized workloads. Heroku supports Git-based deployment, managed services including Apache Kafka and Heroku Postgres, polyglot applications, and isolated environments such as Private Spaces and Shield Private Spaces. In Salesforce’s example, five applications serving more than 76,000 employees used Heroku to cut expense approval time from two days to two hours and recover $2 million in unused licenses. The architecture also combines Heroku AppLink, Heroku Connect, Heroku Fir’s OpenTelemetry support, and managed Dynos, while AWS remains the stated choice for highly specialized AI training requiring raw GPU access.
Improving Cursor’s agent for OpenAI Codex models
Cursor describes adapting its agent harness for OpenAI's latest frontier coding model, GPT-5.1-Codex-Max, by pairing model-familiar instructions with Cursor-specific tools and tuning against Cursor Bench. The Codex integration adopts a more shell-forward design, aligns tool names with commands such as rg, explicitly prefers tools over shell commands, and uses sandboxing to limit unauthorized file and network access. It also limits reasoning summaries to one or two sentences, gives literal guidance for invoking read_lints after substantive edits, removes mid-turn user-communication language, and biases the agent toward taking action unless a plan is requested. Preserving Responses API reasoning items is treated as critical: Cursor reports a 30% performance drop for GPT-5-Codex when traces were removed, compared with OpenAI's observed 3% SWE-bench degradation for GPT-5, while prompt-ordering lessons led it to remove wording that discouraged ambitious work.
Building production-ready Stripe subscriptions using Kiro powers
Kiro's Stripe power is presented as a way to build a production-ready SaaS subscription flow while avoiding the fragmented output common with generic coding assistants. Using a natural-language specification for three monthly tiers and a three-month one-time option, Kiro creates a React frontend, Node.js backend API, CDN-hostable static assets, and server-side Stripe Checkout Session creation. The integration includes Stripe-specific steering files, MCP servers, and hooks, while the webhook handler preserves the raw request body, verifies HMAC signatures with stripe.webhooks.constructEvent(), rejects invalid events with HTTP 400, and routes lifecycle events such as checkout completion and subscription cancellation. The post concludes that this provides a secure, scalable foundation while leaving teams to customize business logic, including access provisioning and deprovisioning, instead of building payment infrastructure from scratch.
Top topics
- Architecture834
- Performance816
- LLMs660
- Machine Learning622
- Open Source563
- AI Agents553
- AI470
- Developer Experience448
Weekly digest
The best engineering reads, once a week.