AI Dev Reads
AI engineering posts picked from company and developer tech blogs such as Toss, LINE, Anthropic and OpenAI, each with a short summary. Tap to read the original.
Last searched Oct 19, 7:44 PM KST
LY CorporationAdded Oct 19
Automating E2E regression tests with AI: turning one-click into a pipeline (LY Corp)
AI-generated E2E tests ran but checked the wrong things, so the team added spec tracing, gap questions, pre-run checks, deliberately wrong expectations to catch false positives, and human review packets. All 98 manual regression tests moved to Playwright, and coverage grew to 196.
Coding toolsCase studies
뱅크샐러드Added Oct 19
Why DDD matters more in the age of AI coding (Banksalad)
The more code AI writes, the more the structure around it matters. Banksalad split a Go credit service into business-level bounded contexts and four layers, and says coding agents now read several times less code per change and reviews stay narrower.
Coding toolsCase studies
LangChainAdded Oct 19
Open SWE: An Open-Source Framework for Internal Coding Agents
Built on Deep Agents and LangGraph, Open SWE gives teams the core building blocks for an internal coding agent, so they don't have to start from scratch to wire one into their own repos and tools.
Coding toolsAgents
CursorAdded Oct 19
Rollouts and Security Reviewer (Cursor)
Rollouts tracks a change from PR to production, writing a monitoring plan before merge and comparing post-deploy telemetry to the baseline. Security Reviewer checks every PR against the whole codebase with explanations and fixes; Cursor says it cut average review time from 4.8 to 3.8 minutes and raised acceptance to 60–70%.
Coding toolsSecurity
Improved token efficiency (Cursor)
Cursor reworked its agent harness to cut token costs 7% without hurting quality: about 66% less system prompt, rarely used built-in tools loaded on demand (60% fewer static tool-description tokens), and explicit prompt-cache breakpoints (20% fewer cold cache misses).
Coding tools
우아한형제들Added Oct 19
Rebuilding Baemin's e-contract screens: what we gave to AI and what humans kept (Woowa Brothers)
Most of the code for Baemin's new e-contract screens was written with Claude Code. AI handled view components and draft specs and tests; humans owned boundaries, lint rules and spec approval. It shipped about twice as fast with roughly 8.5x more test code per line, though four bugs surfaced in the first two weeks.
Coding toolsCase studies