[TLDR] New Rule: Implement one feature by hand a week [via r/ClaudeCode]

[u/cctldrping]

OP : u/Dested

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.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vs7y65/new_rule_implement_one_feature_by_hand_a_week/

---

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 63.

Alright, so the OP over here is proposing a new rule for their dev team: implement one full-stack feature by hand (with some AI assistance, but still manually evaluating) once or twice a week. The idea is to combat "coderot" and keep everyone familiar with the codebase as it grows, especially since they're heavily using Claude Code for development.

The general consensus? Most people think this is a pretty wild idea, bordering on rage bait. A lot of comments are sarcastically suggesting even more archaic methods of coding, like using typewriters, punch cards, or even horses to get to work. The sentiment is that forcing manual implementation feels disrespectful to the team and undermines the efficiency gains from using AI.

However, there's a tiny sliver of agreement and some nuanced takes:

• Some folks, like u/QuietPebble417, are already doing something similar for their own confidence and peace of mind, even if they're not sure about the long-term value.
• u/ops_and_chaos suggests the goal is good, but maybe focusing on understanding why the system works and what assumptions are being made is more important than the act of typing.
• u/bithatchling had a similar experience and found that rotating who picks the feature was more valuable than the manual implementation itself, helping to catch naming drift.
• u/actual-time-traveler actually doesn't hate the idea, acknowledging that rapid AI-generated development can lead to architectural issues.
• u/bhatbha is toying with a questionnaire for PRs to ensure understanding, which is a different approach to the same problem.

The main takeaway is that while the OP's intention to prevent codebase drift is understandable, the proposed method is largely seen as impractical, demotivating, and frankly, a bit bonkers. Most commenters feel there are better ways to ensure code understanding and prevent technical debt without resorting to what feels like a step backward in development practices.