Professional architect sharing high‑quality architecture insights. Topics include high‑availability, high‑performance, high‑stability architectures, big data, machine learning, Java, system and distributed architecture, AI, and practical large‑scale architecture case studies. Open to ideas‑driven architects who enjoy sharing and learning.
When AI‑assisted coding is introduced, teams often struggle to preserve the hidden engineering expertise of top performers, so the article proposes turning that tacit know‑how into reusable, inspectable, and trim‑able Agent processes that can be documented, run, and continuously improved.
The article analyses Claude Code’s four loop types—turn‑based, goal‑based, time‑based and proactive—as a four‑level control‑delegation ladder, explains how each level shifts responsibility from human to system, and offers a gradual adoption path with timely downgrade strategies to keep automation reliable.
Anthropic’s Claude Code team reports an eight‑fold increase in engineer code output, but the article explains that the real shift is from writing code to verification, with specs stored in repos, routines that merge feedback, PRs and metrics, a bad/sad quality taxonomy, six concrete interfaces, and new challenges around context switching, accountability and role boundaries.
The article analyses Claude Code's Loop feature for night‑shift automation, breaking the workflow into four hand‑off points—checking, stopping, waiting, and authority—while showing how turn‑based, goal‑based, time‑based and proactive loops can be combined with concrete Skill definitions, /goal, /loop and /schedule commands to keep engineering boundaries clear and auditable.
To make AI loops work in an enterprise, you must first make the surrounding work system explicit by documenting five engineering objects—goal, state, evidence, permissions and feedback—so that loops run on low‑risk, verifiable paths before scaling to more complex automation.
The article analyses the emerging "Skill Hell" problem where an ever‑growing set of Agent Skills makes routing, context handling, execution and maintenance fragile, and proposes a three‑layer design, explicit routing contracts, progressive disclosure, evidence‑driven steps and disciplined pruning to keep skills stable and auditable.
The article analyzes Andrew Ng’s three‑layer Loop Engineering framework—agentic coding, developer feedback, and external feedback loops—explaining how accelerating AI‑driven coding requires stronger, slower human‑managed feedback to keep product vision aligned with real‑world needs.
The article explains how to transform AI agents from single‑prompt responders into reliable night‑shift workers by defining clear goals, state files, evidence, and permission boundaries, using /goal, /loop and scheduled tasks, and provides concrete steps, examples, and a scheduling template for stable unattended execution.
This article explores Claude Code's /loop feature, showing how it can act as an in‑session observer to automate repetitive checks like CI status, deployments, and PR comments, while providing evidence, handling failures, and integrating with broader scheduling tools for reliable engineering workflows.
The article presents a structured set of 27 Claude Code techniques—organized into three phases of context setup, process control, and automation—that transform the tool from simple code generation into a reliable, verifiable component of engineering workflows, emphasizing isolation, verification, and evidence collection.
