If you model starves because of small context window (your described symptoms), then I would suggest: a) Split the job between agents, each with it's own context window; b) Use advanced model as orchestrator for multiple coding/testing/reviewing agents; c) Use code indexers like https://github.com/ory/lumen or/and https://github.com/defendend/Claude-ast-index-search d) Use planning and detailed specifications preparation before the coding phase.

What model are you running? With what settings?

Please don't post rants on Ask HN.

Worst negative pattern I've seen is hyper defensive programing. E.g.

  try:
    something_that_should_not_fail_and_if_it_does_our_assumptions_are_all_wrong()
  except:
    fallback_that_will_not_result_in_correct_behavior_but_make_failure_hard_to_detect()

But, of course, it depends a lot on which models you're using and how you instruct them.

My convention file says no mass rewrites. Plan. Assess. Spec. Code review. Depends on your model I guess

Sounds like more of a rant than a question and for that you get a ranty reply. Ask the AI how to improve your results.