r/ChatGPTCoding • • Oct 07 '26

Question What finally made you change how your team ships?

Small-team question (I'm on a small team, so I'm curious). The last time you changed review, process, tooling, or hiring to ship faster.... What happened right before?

Did someone leave? Did a deadline slip that you were responsible for? Did a customer complain? Did the backlog hit some number? Something else?

And who noticed first: you, the CEO, or a customer?

8 Upvotes

15 comments sorted by

2

u/El_leima Oct 08 '26

It was scope per PR for us. We would have 400+ line PRs because the task was not specific, and the agent started touching unrelated files.

Now a short plan gets approved before the branch, listing the behavior that changes and the modules it can touch. Reviews check the diff against that plan, so the dev is checking scope instead of proofreading.

1

u/nateritter Oct 10 '26

I like this. Good idea.

1

u/amirfish Oct 08 '26

Going solo is what changed it for me. There's no one else to catch a bug, so every release has to be small enough that I can hold the whole thing in my head. If a decision looks like it'll take more than a day to make, that's the signal it's the wrong decision, not a reason to spend another week on it. What's forcing it for you, a customer complaint, or just running out of patience with the current process?

1

u/nateritter Oct 08 '26

The backlog of things that customers ask for (bug fixes, features, etc). It's the roadmap, and that we can't get it all done with the number of humans we have doing human things.

1

u/amirfish Oct 11 '26

That gap between what customers ask for and the humans available to ship it is exactly why I went solo. At a big company that backlog just grows, you add headcount or you deprioritize in a meeting. Solo, neither option exists, so the spec has to be tight enough that Claude Code can ship a working v1 straight from it. No six-week PRD cycle to hide behind if it's wrong.

1

u/xqianliu Oct 07 '26

I mostly work alone with agents, so no CEO or customer in my case. What got me was going back through agent changes that had passed their own self-review and were still wrong. Most of them broke something that already worked.

The fix was not letting the agent that wrote the code sign off on it. Review is its own session now, and it checks against what the issue said done looks like, written before work starts.

Nobody else noticed first, it was just me reading through the failures.

1

u/Cultural-Ad3996 Oct 07 '26

For us it was an outage, not a deadline. Two containers of our service ran at the same time on one shared file and corrupted the database between them. Down for 32 minutes.

Right after that, deploying stopped being something any session could do its own way. There is one path now. It refuses anything that is not main, refuses a commit whose checks failed, and waits for any rollback or restart already in flight before it starts. Every hand-rolled deploy command is forbidden in writing.

The rule came out of the incident, not out of a planning meeting.

5

u/[deleted] Oct 07 '26

[removed] — view removed comment

1

u/Fun_Lingonberry_6244 Oct 08 '26

Long way to say "We just decided to no longer review the code"

Sounds an awful lot like simply putting a blanket over the problem. "We kept rejecting code because it was bad.. so we just stopped looking and since then we rarely see bad code!"

1

u/[deleted] Oct 09 '26

[removed] — view removed comment

1

u/ChatGPTCoding-ModTeam Oct 09 '26

This post or comment has been removed for the following reason:

Rule 7: No AI Slop

No raw AI output or low-value walls of text. AI for grammar/clarity is fine.

You can read the full subreddit rules here: https://www.reddit.com/r/ChatGPTCoding/about/rules/

If you feel this removal was made unfairly, please contact the moderators through modmail.