I have a new rule im am thinking about implementing for me and my dev team: You are be required to implement one full stack feature by hand once or twice a week per project. Nothing too massive, something that would be one good opus prompt worth. It forces you to evaluate if there has been any major drift in the architecture, anything you didn’t realize changed, refamiliarize yourself with the codebase, etc. It should take you 30 minutes, but would pay years of dividends in coderot. The reality is we are building all features and fixing all bugs with claude code, “reviewing” and deploying. And it has worked surprisingly well for us, but I fear we will lose scope of the codebase as it gets bigger. I trust my team to handle this appropriately, but I feel like enforcing something like this as a rule keeps us all more accountable. Any thoughts on this? Anyone doing something like this? Am I way off base? Edit: to be clear, when I say by hand, I of course mean with some sort of copilot/inline ai with small bulk code changes and stuff, more just forcing you to visit the stack and evaluate it. submitted by /u/Dested
Originally posted by u/Dested on r/ClaudeCode
You must log in or # to comment.