Topic
Everything filed under Engineering, newest first.
RSS · JSON · All topics
The Job Is No Longer Writing Code
AI coding agents automate well-specified implementation work; the remaining job is coordination, specification, and decision quality—and most orgs have not restructured for that shift.
8 min · 1,877 words
Meta Superintelligence Labs’ deep dive on Muse, their personal AI agent: how they designed a secure VM, connectors, a built-in sentinel, and privacy/safety controls so an agent that holds long-term personal context stays useful without becoming unsafe.
18 min · 4,062 words
So you want to use OpenRouter?Might seem simple on the face of it, but unfortunately it's pain all the way down.
Mo Moustafa shares operational lessons from running an iMessage AI assistant on open-source models via OpenRouter. Key takeaways cover provider variability, per-provider benchmarking, handling edge cases, and why the same model weights can behave very differently depending on which host serves them.
1 min · 230 wordsagent-written
Engineering trade-offs when building a multi-model AI gateway
Practical engineering notes on multi-model AI gateways: narrow common interfaces, request normalization, streaming, error handling, routing, cost tracking, and the limits of portability.
4 min · 979 words
AI handles incidents, engineers lose touch with their systems
Sylvain Kalache argues that as AI-powered incident response tools take over routine on-call work, engineers are losing the hands-on practice that builds system intuition. When a genuinely novel, high-severity incident eventually arrives, those engineers will be less prepared than their predecessors — a pattern Lisanne Bainbridge described in her 1983 "Ironies of Automation."
1 min · 262 wordsagent-written
The feedback loops behind Kubernetes
PlanetScale explains Kubernetes as nested feedback controllers—desired state, observe, act, repeat—and why that mental model clarifies controllers, operators, and day-2 operations.
30 min · 6,866 words
# No more issues Written on 2026-09-04 An interesting change at Laravel yesterday: they disabled the ability to create issues on a number of repositories and instead encourage people to create pull-requests instead: To be clear: this is only the case for Laravel packages like Soc
4 min · 919 words
This PCB is brought to you by Fable 5 — A6M-Zero
An experiment to design a cute PCB (without touching any tools) in plain English
5 min · 1,256 words
Dropping Swift entirely from our Bevy iOS crates
Rustunit explains dropping Swift from Bevy iOS crates in favor of objc2—why the Swift glue went away, what the new crates look like, and what it means for Bevy-on-iOS maintainers.
4 min · 988 words
A Million Agents Is a Distributed Systems Problem
Once you run thousands of AI agents, the hard part isn’t prompts—it’s scheduling, fatigue, overload, and coordination. InstaCloud frames agent fleets as a classic distributed-systems problem.
8 min · 1,877 words
Vibe Coding Is Easy. Production Isn't.
Andres Torres Russo argues that when AI makes implementation cheap, production still demands architecture, security, maintenance, integration, and experienced engineering judgment—not just a demo that compiles.
10 min · 2,311 words
Abandoning Scientific Linux Was a Mistake
Mohamed Elashri argues CERN and Fermilab undervalued Scientific Linux’s option value: after CentOS and RHEL source-access shifts, accelerator controls are now moving thousands of machines to Debian to keep old hardware alive.
9 min · 2,133 words
Extracting AI rules from an existing codebase
How Laravel Boost learns project conventions from an established app: why hand-written detectors fell short, and how an agent skill gathers evidence so developers can approve scoped rules.
6 min · 1,371 words
How I managed multi-agent worktrees in a large Rust codebase
Manuel Tumiati walks through six failure modes of running many AI agents across git worktrees in a large Rust repo—shared targets, locks, orphaned artifacts—and the fixes that made it workable.
18 min · 4,149 words
google.com/goto: Google's anti-scraping update
Google Search has replaced direct destination URLs in organic results with opaque google.com/goto redirect links, making it impossible to extract target URLs from the HTML without an additional network request. Autom explains the technical mechanism, why Google did it, and how their API handles it.
1 min · 255 wordsagent-written
There is more to code review than (automatable) detection
The abstract for article “The End of Code Review: Coding Agents Supersede Human Inspection” paints this picture for the reader… **Abstract** – Code review has been the primary quality gate in software development since Fagan formalised code inspection in 1976.
5 min · 1,129 words
Why Clay Has an AI Writing Policy
Clay engineer Sophie Alpert explains the company-wide AI writing policy: stand behind every sentence, treat writing as thinking, respect readers' time, and reject padded AI slop.
4 min · 993 words
There's no point at which turning your brain off will work
Dan Luu argues that turning off critical judgment while using LLMs fails in practice: when people let models take actions or produce analyses without verification, errors compound — there is no safe point at which you can stop thinking.
12 min · 2,831 words
You're Leaving Compute on the Table
Nishant Joshi tallies roughly 15 TFLOPS of idle GPU and neural compute sitting on his desk across a MacBook, Mac mini, iPhone, and AirPods, and argues product teams should push more work onto users' own devices while keeping identity, billing, and source of truth on the server.
5 min · 1,094 words
GenRec: Towards LLM-Native Recommendation at Netflix
Recommendations sit at the heart of the Netflix experience. Our current production models rely on thousands of hand‑crafted features over users, items, and interactions, along with specialized architectures for sequence modeling, feature interactions, and multi‑task objectives. This stack has evolved over many years to support diverse content types (movies, series, games, live, podcasts) and product surfaces, but its complexity makes it costly to onboard new use cases: adding a content type or surface can require significant feature engineering, architecture change,...
12 min · 2,813 words