3 ms·

Same. Someone we brought on that worked for about a month and vibe coded to hell caused a lot of damage in terms of tech debt and that list shows. Looks like he

by dawnerd 7mo ago

Same. Someone we brought on that worked for about a month and vibe coded to hell caused a lot of damage in terms of tech debt and that list shows. Looks like he managed 124 commits in a single week. The same repo, our top dev only has around 500 in its entirety. Also important to have a plan for code review and merges when a lead is out of town. I found out I needed to reevaluate how that's handed when I was gone for two weeks.

michaelcampbell 6mo ago
Not to diminish your lived experience, but this is sort of a management issue, no? There should be some expectations set and/or gates that need to be opened during PR about commit expectations. Some teams like a lot of commits to be a (messy) reflection of actual reality/history, others want the well-curated "story" with a bunch of squashes and rebases.