AI / CrewAI Interview Questions
Why does CrewAI recommend YAML configuration over direct instantiation for new projects?
YAML configuration separates the description of agents and tasks, their roles, goals, and expected outputs, from the orchestration logic that assembles and runs them.
- Makes it fast to iterate on wording, personas, and task descriptions without touching Python code
- Keeps configuration readable for non-engineers who may want to tune an agent's persona
- Still supports upgrading to full programmatic Python APIs when advanced orchestration or custom logic is genuinely needed
Direct instantiation remains available and useful for quick prototypes or highly dynamic agent generation, but YAML is the more maintainable default for projects expected to grow.
What does YAML configuration separate from orchestration logic?
Is direct instantiation still available alongside YAML configuration?
More Related questions...
