Skip to content

Commit e51d85f

Browse files
committed
Refactor the 'Why go non-agentic with CWC?' section with concise, benefit-driven points
1 parent 7b89db1 commit e51d85f

1 file changed

Lines changed: 4 additions & 7 deletions

File tree

README.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,10 @@ Available in VS Code, Cursor, and other forks.
1717

1818
### Why go non-agentic with CWC?
1919

20-
While coding agents are an impressive addition to the sphere of programming tools, they're backed by a powerful, yet limited technology that only creates the illusion of producing informed decisions—a characteristic fundamental to software engineering.
21-
22-
- **Great software is a chain of carefully considered decisions.** Because LLMs can't truly reason and don't know their own limitations, over-delegating decision-making may create hard-to-debug weak links and impair our own abilities in creating strong ones.
23-
- **Programming is about building mental models.** Knowing ins and outs of the codebase makes context selection efortless and AI outputs predictable.
24-
- **Single-turn interactions with the model save time.** With CWC, there is no orchiestrated planning or file lookups for automated context collection—a single response from the model contains all the changes to complete the task.
25-
- **Context once polluted, won't recover.** When the model isn't getting your intent on a first try, a conversation only makes it more confused and erroneous. You're always better off adjusting context, instructions and starting afresh.
26-
- **Coding agents become expensive and get lost.** Although they seem a joy to work with in smaller projects; with ever-increasing complexity of real-world codebases, they start requiring excessive context lengths, the biggest, pricey models and may still arrive at dead ends.
20+
- **Non-agentic is predictable.** Granular control over context let you scope the model appropriately to the task and build intuition for its outputs.
21+
- **Non-agentic is blazing fast.** Eliminate the need for long-running planning and file lookups. A single prompt generates a complete set of changes across all necessary files in a single response.
22+
- **Non-agentic avoids context pollution.** When the model isn't getting your intent on the first try, you just adjust the prompt and resend without distracting the model with previous attempts.
23+
- **Non-agentic is cost-efficient.** Choose the model type according to the complexity of the task, not the overall codebase.
2724

2825
### Guiding principles
2926

0 commit comments

Comments
 (0)