The fact that we're slowly removing the apprenticeship layer and passing it off as "productivity gains" should be far more alarming. Just imagine. The kind of work that is best suited for AI, such as boilerplate code, simple CRUD endpoints, and basic component wiring, is actually similar to the work that helps in training junior developers. It was not that we were working on those tasks because th
Applicant Tracking Systems used to be boring. For most of the 2010s, an ATS was essentially a database with a careers page bolted on top: a place to dump resumes, push them through a pipeline of stages, and email rejections in bulk. The interesting work happened around it, not inside it. That has shifted in the last two years, and the shift is deeper than the marketing pages suggest. I have spent
The previous two posts covered how events flow from the SDK to the UI. This post focuses on visualizing one specific type of event: tool calls. Tool invocations are the most frequent operations in an Agent application. A typical task might call tools twenty or thirty times—reading files, writing files, executing commands, searching code. If every tool call renders as the same gray block, it's hard
Post 1 covered how AgentBridge converts the SDK's AsyncStream<SDKMessage> into [AgentEvent]. This post looks at what [AgentEvent] becomes — how TimelineView renders 18 event types, handles scroll behavior, and stays smooth when the event count gets large. TimelineView is the main body of the workspace, filling all the space between the sidebar and the input box. Its view hierarchy is shallow: Time