标签 · Software Engineering

Recent picks

5picks · chronological

08-11

What Is an AI Engineer?

A concise role introduction to AI engineering, drawing on Latent Space's 'The Rise of the AI Engineer.' It draws the line at the API boundary: AI Engineers orchestrate models to build applications, while ML Engineers build the model APIs themselves. The post argues newcomers don't need linear algebra or pretraining experience; instead they need strong software fundamentals, evaluation frameworks, and feedback loops. It also distinguishes AI Engineers from AI-assisted developers who merely use tools like Copilot. Web developers are presented as well suited for the transition, and TypeScript is called a fast-growing fit. The article is accessible but conceptual, with a promotional block for the author's AI Hero skills system.

www.aihero.dev · 4 min · AI Engineering · Career Advice · LLM

08-08

Cloudflare ADLC: Workflow-based CI/CD for agent software factories

Cloudflare argues the bottleneck in software development has moved from implementation to every other SDLC stage, now that AI makes code generation cheap. Their answer: let agents drive more of the lifecycle, not just codegen. The post introduces @cloudflare/ci, local OTel traces for Wrangler, Agent Traces, and a set of primitives meant to turn the SDLC into an 'Agent Development Lifecycle' for software factories. It includes Workflow code that parallelizes lint/test/typecheck/build and then deploys, plus guidance that CI/CD is just one kind of Workflow—workflows can spawn containers, agents, and browsers and persist state for days. The article also lists seven platform requirements for agent-driven delivery: programmatic, horizontally scalable, reproducible, push-based, atomic, permissioned, and self-improving. Useful for engineers building agent infrastructure on Cloudflare or exploring autonomous delivery pipelines.

blog.cloudflare.com · 14 min · Agent Engineering · AI Agents · Cloudflare

08-03

When Coding Is Not the Bottleneck: Three Levels of Software Autonomy

This article adapts a position paper by UC Berkeley RDI researchers, proposing a three-level framework for autonomous software development: code autonomy, pipeline autonomy, and demand autonomy, plus three orthogonal dimensions—specification granularity, temporal autonomy, and oversight mode. It contrasts a concrete win (16 parallel Claude agents building a working C compiler for under $20k) with the observation that frontier agents still degrade sharply on benchmarks that test continued evolution rather than isolated tasks. The authors argue that the immediate industry risk is skipping levels: teams claim level-1 review but merge AI code unchecked, or adopt pipeline autonomy without the needed verification and governance. As coding stops being the bottleneck, requirement specifications, agent audits, and accountability mechanisms displace raw coding skill. Useful for engineers and engineering leaders thinking about agent-driven development and governance.

www.pingwest.com · 8 min · Agents · AI Engineering · LLM

07-11

Agentic test processes: from chip design to AI workflows

Drawing from his experience at chip company Centaur, the author compares test processes that scale well with LLM agents: no code review by default, heavy reliance on fuzzing, and a dedicated test team. He argues that while LLMs are poor at writing tests directly, directed fuzzing with LLMs can find real bugs in minutes. The article highlights the high variance of LLM outputs—benchmark rankings often flip with minor task changes—and cautions against over-reliance on aggregated metrics. Through examples like building a superhuman board game AI, he advocates systematic data-driven iteration over prompt tricks. Targeted at engineers interested in AI-assisted development, testing, and agent workflows.

danluu.com · 91 min · AI Engineering · Benchmarks · Developer Tools

06-30

How To Make Codebases AI Agents Love

This article argues that codebase structure matters more than prompts or AGENTS.md files for AI agent output quality. The core idea is applying 'deep modules' from A Philosophy of Software Design: each module exposes a simple interface controlling lots of implementation. The author introduces 'grey box modules'—developers own and test the interface, AI owns the implementation inside. This improves feedback loops (tests are feedback), navigability (filesystem mirrors mental model), and reduces cognitive load (developers only track 7-8 module boundaries). The article notes TypeScript's difficulty enforcing boundaries and recommends the Effect library. For engineers optimizing AI coding workflows.

www.aihero.dev · 5 min · Agent Architecture · AI Engineering · Code