From ccf776bc0cb7a7b1ab0a5644c0da1ebaf6a9d956 Mon Sep 17 00:00:00 2001 From: Zachary Huang <33015448+zachary62@users.noreply.github.com> Date: Sun, 16 Mar 2025 01:01:34 -0400 Subject: [PATCH] Update guide.md --- docs/guide.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/guide.md b/docs/guide.md index 8de0f2d..9cc1a06 100644 --- a/docs/guide.md +++ b/docs/guide.md @@ -68,11 +68,12 @@ Agentic Coding should be a collaboration between Human System Design and Agent I 5. **Implementation**: Implement the initial nodes and flows based on the design. + - 🎉 If you’ve reached this step, humans have finished the design. Now *Agentic Coding* begins! - **“Keep it simple, stupid!”** Avoid complex features and full-scale type checking. - **FAIL FAST**! Avoid `try` logic so you can quickly identify any weak points in the system. - Add logging throughout the code to facilitate debugging. -6. **Optimization**: +7. **Optimization**: - **Use Intuition**: For a quick initial evaluation, human intuition is often a good start. - **Redesign Flow (Back to Step 3)**: Consider breaking down tasks further, introducing agentic decisions, or better managing input contexts. - If your flow design is already solid, move on to micro-optimizations: @@ -84,7 +85,7 @@ Agentic Coding should be a collaboration between Human System Design and Agent I >
{: .best-practice } -7. **Reliability** +8. **Reliability** - **Node Retries**: Add checks in the node `exec` to ensure outputs meet requirements, and consider increasing `max_retries` and `wait` times. - **Logging and Visualization**: Maintain logs of all attempts and visualize node results for easier debugging. - **Self-Evaluation**: Add a separate node (powered by an LLM) to review outputs when results are uncertain.