Programming Circlejerk

299 readers

1 users here now

Community to talk about enlightened programming takes

Rules:

read and follow the programming.dev code of conduct
no flamewars
mark your unjerks
only programming related content allowed
link to the original source
do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.

founded 1 year ago

MODERATORS

FirstMajesticComet@programming.dev

crmsnbleyd@sopuli.xyz

crmsnbleyd@programming.dev

143

Think. Experiment. Vibe to market (sopuli.xyz)

submitted 3 months ago by crmsnbleyd@sopuli.xyz to c/programmingcirclejerk@programming.dev

85 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] brygphilomena@lemmy.dbzer0.com 9 points 3 months ago (1 children)

I have an engineer that uses it heavily.

It adds so much extra and he'll push thousands of lines of code into a PR every week. He had one bug and tried to refactor it, he bloated that single file by 16%.

It's almost impossible to review.

[–] pivot_root@lemmy.world 5 points 3 months ago

It adds so much extra and he'll push thousands of lines of code into a PR every week.

This is just a waste of the reviewer's own time that could be better spent doing actual work. Is it at least split up into multiple commits, or is it one giant shitshow?