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

Cut Token Costs by 95% with OpenClaw's Seven Optimization Techniques
A comprehensive guide detailing seven techniques to reduce AI agent token consumption by 95%+, including tree-structured boot files, AI auto-compression, local model offloading, and cron-based CPU tasks.
Craft Coding: Let AI Review, Not Write, Your Code
Peter Bloem argues that vibe-coding is a dead end. Instead, have AI review your code while you do the writing. This keeps skills sharp and avoids the trap of unchecked AI output.

A Solo Developer's Two-Phase Prompting Method for Large Projects with Claude AI
A solo developer shares a workflow using Claude Chat as the architect and Claude Code as the builder, with a two-phase prompting method that includes failure mode analysis and verification gates.

Practical Guide to Creating Claude Skills: Structure, Triggers, and Scripts
Claude Skills are instruction manuals that automate repetitive tasks, stored as folders with a SKILL.md file in ~/.claude/skills/. The guide explains YAML triggers, script integration, and multi-skill orchestration rules.