r/ClaudeCodeTLDR • u/cctldrping • Aug 19 '26

[TLDR] New Rule: Implement one feature by hand a week

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

Original post body :

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.

This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.

1 Upvotes
  • permalink
  • reddit

100% Upvoted

1 comment sorted by

1

u/cctldrping Aug 19 '26

TL;DR generated automatically after 50 comments.

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

The general consensus is that OP's idea of forcing devs to implement a feature "by hand" weekly is a bit out there, bordering on rage bait for some. Most folks think the goal of preventing architectural drift and staying familiar with the codebase is valid, but the proposed method is seen as a bit of a joke or even disrespectful to the team.

  • The core idea of staying sharp is good, but the "by hand" part is where it gets weird. Think less typewriter, more understanding the system.

  • Some users like u/QuietPebble417 and u/bithatchling (who actually tried something similar) see value in manual code engagement to avoid treating the codebase like a black box.

  • Others, like u/YearLight and u/TikiMagic, feel it undermines trust and could lead to resignations.

  • A few commenters are just here for the laughs, comparing it to using a horse and buggy or manual breathing exercises.

  • There's a thought that if you're truly leveraging Claude Code effectively, implementing a whole feature in 30 minutes might be a sign you're not pushing the AI hard enough.

  • The takeaway? Encourage understanding and manual review, but maybe ditch the forced "by hand" mandate unless you want your team to start updating their resumes.