Tag
A tweet explains that sharing AI prompts is challenging because prompts now involve references, skills, and examples, often requiring integration with multiple AI tools and repositories.
The article analyzes 'katamari architecture' as a metaphor for haphazard AI-assisted software development, examining how LLM agents lead to feature bloat without proper composition, drawing parallels to the 'Big Ball of Mud' concept.
The article discusses using lines of code as a metric for evaluating Ruby gems, suggesting it helps understand implementation complexity and encourages a design philosophy focused on clarity and maintainability through 'breezy reads'.
Kent C. Dodds advises improving the primitives used by AI agents to reduce low-quality outputs instead of relying on cleanup, illustrating the point with a linked thread.
The article explores how shared notes files in AI agent setups track actions but lose the reasoning behind them due to context window constraints, highlighting gaps in current workarounds.
Boris Cherny emphasizes the need for higher standards and guardrails when using AI models like Claude for production code to maintain quality and avoid maintenance issues.
The article explains that AI review loops in code development can become unstable due to inconsistent AI opinions, scope creep, and hallucinations, as shown in a test with Opus 5.
The article clarifies the differences between AGENTS.md, SKILL.md, and related files in AI agent development, emphasizing their roles in cost efficiency and context management to prevent drift.
Addy Osmani discusses practical loop engineering for AI agents, covering goals, autonomous feedback cycles, and the use of tools like Claude Code and Codex for managing parallel agent tasks.
The article describes how a skiing accident incapacitated the Tech Lead on a project, testing the team's development practices and underscoring the importance of documentation and knowledge transfer in software development.
Nolan Lawson argues that AI coding assistants can be used to write high-quality code slowly by employing multiple models for thorough code review and bug detection, improving codebase health rather than maximizing output speed.
Compares two AI agents handling skill reuse: one rewrites extraction logic from scratch each session while the other packages it into a dedicated, documented file, highlighting the need for agent skill persistence.
The article argues that teams should choose boring, well-understood technology for reliability, while being free to innovate in development practices like TCR (test && commit || revert), which are easier to adopt and abandon without long-term maintenance burden.