Integration failure
Outside systems break. Always handle errors and retries.
Difficulty 2/5
Short
Plain English
Outside systems break. Always handle errors and retries. Picture it like this: The supplier was late — have a backup plan. In the apps you ship (Agentify, wedding portals, CRM), you will bump into this on almost every screen — name it clearly when you prompt your coding agent.
Analogy
The supplier was late — have a backup plan.
Go deeper
Outside systems break. Always handle errors and retries.
Common mistakes
- Letting the AI rename this concept three different ways in one PR.
- Building UI before you can say what is stored and who can change it.
AI-agent trap
Agents may invent jargon here. Ask them to explain the concept in plain English first, then map it to your schema and one real screen.
Summary
Outside systems break. Always handle errors and retries. The supplier was late — have a backup plan. Ask yourself: where does this live in the database, which function changes it, and which screen shows it?
Confidence: