Topic
Everything filed under Software Engineering, newest first.
RSS · JSON · All topics
An outsider's perspective on Scion and Mononoke
Varun Gandhi, who works on source control at Databricks, reviews Anthropic's post about its centralised version control system Scion against Meta's Sapling/Mononoke, arguing it presents established ideas as novel, goes wide rather than deep, and shares too little design detail to be a real gift to the community.
19 min · 4,363 words
PHP2Shell and AI Put Half the Internet on Edge
IEEE Spectrum's Dina Genkina reports on the PHP2Shell vulnerability and argues AI is forcing the industry to pay down decades of technical debt in legacy software that powers much of the web.
5 min · 1,083 words
How //go:embed Works: From Source Files to Binary
A guest post by Ainsley Clark on Internals for Interns that explains what the //go:embed directive is, how to use embed.FS, how the go command, compiler and linker carry embedded files into the binary, how the runtime reads them, and the tradeoffs involved.
24 min · 5,517 words
Our software engineering interviews are changing (a little)
Jane Street explains that with most of its engineers now using LLMs daily, it is adjusting its software engineering coding interviews, while more experienced candidates will continue to see varied formats such as system design and discussing prior work.
2 min · 549 words
What changed in how we evaluate AI SRE agents
Why a coding harness is not an AI SRE agent, and the expanded criteria One2N now uses to evaluate AI SRE agents: triggers, context, RCA quality, audit and guardrails.
15 min · 3,505 words
New context engineering challenges in late 2026
Harrison Chase surveys late-2026 context engineering challenges for agent builders: longer horizons, tool noise, memory tradeoffs, and why harness design now matters as much as the underlying model.
4 min · 892 words
Moment of Ruby: an argument for nothing
Chris Zempel of Aha! Engineering shows a tiny Ruby idiom using an undefined default object so a method can tell omitted arguments from explicit nil or false when acting as both getter and setter.
2 min · 442 words
Nyquist Limit: the frequency of changes in tech is invalidating our understanding
Ryan Prior argues that LLM-driven increases in the rate of software change outpace how fast humans can observe and understand systems, so teams end up measuring noise instead of signal, borrowing the Nyquist limit from signal processing.
3 min · 744 words
Kunal (knlb.dev) argues that uncritically accepting whatever coding agents produce is fast and seductive but erodes understanding, and lays out practical defenses: choosing a 'vibe limit', watching for automation bias, forcing yourself into the loop, demanding comprehensible output, delegating deliberately, and leaning on good design.
12 min · 2,731 words
Andrej Karpathy describes building HackerTube, a YouTube-style site made only from videos recommended on Hacker News, with Opus 5.5 in about two hours, with local-only recommendations and a data export.
1 min · 248 words
Trapped in the Technologist Factory
Zach Tellman reflects on being paid to use Clojure two years after its release at the startup Runa, and on how engineers learn judgment by adopting new technologies and failing, asking what happens to that path when junior engineers are told to stick to boring tools.
13 min · 2,940 words
Postgres 19 is late, and it's AI's fault
PostgreSQL committer Robert Haas explains why PostgreSQL 19 will likely slip to November or later: LLM-driven code review and bug hunting surfaced an unusual volume of defects in new features, forcing reverts and fixes, and he argues every developer will now need to raise their game.
4 min · 897 words
Designing a Multi-Agent Architecture Guided by Advanced Type Systems
An adversarial multi-agent design that splits development across Specifier, Implementer, Falsifier and Verifier agents, using advanced type systems in Python and TypeScript as proof engines to curb silent LLM hallucinations.
11 min · 2,578 words
Coding Agents, Starter Kits and pgledger
Paul Gross explains why pgledger, his double-entry ledger in pure PostgreSQL, is a starter kit of tables and SQL functions rather than a library, and how coding agents make it easy to adapt such hardened components into any stack, making thoroughly tested building blocks more important than ever.
4 min · 979 words
Avoid Public Functions Calling Other Public Functions
Alex Kladov (matklad) offers a small-scale rule of thumb: instead of having one public function call another, factor the shared logic into a private helper both call, because public functions serve different callers and their behaviour tends to diverge.
2 min · 529 words
Why are good developers so wary of agentic development?
Thoughtworks CTO Rachel Laycock argues that experienced developers’ hesitation about coding agents is less about loving code or job fears and more about knowing that built is not the same as working in production, and sets out a challenge for leaders to make room for experimentation and for developers to bring their judgment to it.
9 min · 2,002 words
Martin Fowler reflects on the growing feeling of reading prose that seems LLM-generated, why that 'LLM voice' makes him lose interest, why he is wary of AI-text detectors, and what it means when writing stops being communication between people and becomes communication with a process. He notes he did not use AI or LLMs in writing the post.
5 min · 1,115 words
Hunger beats tenure: Advice for junior engineers
Felix Rieseberg, an engineering manager at Anthropic, explains why he has stopped giving coding interviews and argues that with AI, engineers without years of tenure or social capital can outpace more experienced peers; he offers practical advice on ownership, taste, empathy and principled thinking for junior engineers.
5 min · 1,233 words
An update from Amazon engineering leadership on the role of the developer in the age of AI
Terk Terkowitz, VP and Distinguished Engineer at Amazon, publishes the memo behind Amazon's revised SDE role guideline: engineers are judged on customer, business and team outcomes rather than AI usage, tokens or lines of code; leaders should use AI hands-on and study the 10th and 90th percentile of adoption; work that AI doesn't help is 'a finding, not a failing'; and engineers should reconnect with customers in the era of the 'Renaissance Developer'.
7 min · 1,545 words
Software may be getting worse, but it used to be horrible
Jake Voytko grants that AI-accelerated code output is making software buggier, but pushes back on nostalgia: drawing on using computers since 1990, he recalls blue screens, lost work before autosave, no security, disk fragmentation, tiny memory, unreliable install media and the turbo button to argue that software in the Windows era was far worse.
11 min · 2,593 words