One-Soup One-Dish: A Japanese Cooking Principle for AI Fatigue

Developer and creator Takuya, writing on his blog Devas Life, draws a parallel between the Japanese cooking principle Ichiju Issai (one soup, one dish) and the overwhelming pace of AI tooling. The core idea: strip away the unnecessary to maintain mental health and creative focus.
The Problem: AI Fatigue
New AI services emerge daily, and major releases from big companies change workflows weekly. Chasing every hype doesn't increase security — it clouds the essential skills developers need. Takuya calls this AI fatigue.
The Solution: Ichiju Issai for Tech
Ichiju Issai is a meal style centered around rice, one soup, and one side dish. Chef Yoshiharu Doi proposed it to free home cooks from the pressure of creating elaborate meals. Takuya applies this to software: treat your core development environment (editor, AI coding agent, or framework) as the rice — the constant that never changes — and allow yourself only one primary tool and one secondary tool. The goal is to create a rhythm where you can return to a comfortable, heart-centered place.
Practical Takeaways
- Decide what NOT to do. Doi says: “By simplifying meals to Ichiju Issai, cooking becomes free of stress.” Your tech stack should follow the same rule.
- Find tools you never get bored with. Just as a parent’s cooking brings comfort through familiarity, your core tools should feel like home.
- Avoid tracking gossip or drama. Social media algorithms try to grab attention; Takuya advises deliberately ignoring them to preserve calm.
- Direction over strategy. Moats can be flexibly changed; the important thing is knowing where you want to go as a developer and artist.
Takuya’s article includes a video version and references Doi’s book 一汁一菜でよいという提案 (The Proposal for One Soup, One Dish).
📖 Read the full source: HN AI Agents
👀 See Also

Research Shows Effective AI Prompting Is Cooperative Communication, Not Engineering
Peer-reviewed research indicates that effective prompting with AI models follows the same cooperative communication principles humans use, with Lakera's analysis showing most prompt failures stem from ambiguity rather than model limitations.

OpenClaw setup checklist: six critical steps for new users
A Reddit post outlines six essential configuration steps for OpenClaw users: change default model from Opus to Sonnet to reduce costs, lock gateway host to 127.0.0.1 for security, create SOUL.md for agent personality, avoid installing skills initially, don't create multiple agents, and use /new command to manage conversation context.

Structuring Claude Code Agents with CLAUDE.md and .claude/ Directory Patterns
A developer shares their approach to running multiple AI agents using Claude Code, with each agent having its own directory containing a CLAUDE.md file and a .claude/ directory with rules and skills. The key insight is separating always-on context from on-demand workflows to optimize token usage and response quality.

Building a serverless AI agent platform on AWS for $0.01/month with Claude Code
A developer built a complete AWS serverless platform running AI agents for approximately $0.01/month using Claude Code over 29 hours, eliminating expensive components like NAT Gateway ($32/month) and ALB ($18/month). The project includes 233 unit tests, 35 E2E tests, and deploys with a single cdk deploy command.