Should every failed test trigger git reset --hard?
No. Preserve user work and inspect the failure first. A destructive reset is only appropriate inside a disposable, recoverable environment whose contents are understood.
Answered in
Context Rot and Coding-Agent Loops: Recovering Without Losing WorkLong contexts and repeated failed edits derail coding agents. Bounded retries, useful summaries and recoverable checkpoints help, without guaranteeing success.
Read the full analysisOther questions this article answers
More development best practices questions
- How much faster does AI help developers write code?
- What is code churn and how has AI impacted it?
- Why did developer PR throughput increase by only 7.76% despite a 65% increase in AI tool usage?
- What are the security risks associated with AI-generated code?
- How does AI impact the Total Cost of Ownership (TCO) of software?
- Does a larger context window prevent agent loops?
- Do agent applications require a modular monolith?
- Can one database transaction roll back an entire agent workflow?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.