That creates negative incentive for creating things

based Alberto

>>25619213 Yeah, basically you end up having bunch of cowboy coders who vomit buggy features and then rest of the team has to fix em because "collective code ownership :) t. scrum master"

>>25619213 That's a good thing.

https://softwareengineering.stackexchange.com/a/446627 This is a great answer. Basically you will have _no idea_ who is the productive dude and who is not unless you encourage weak code ownership. Yet, all the lefties are losing their mind because "my feelings are hurt when I get blamed for my bugs bohooo".

Code monkeys are obsolete. You can do productive work now like delivering pizzas or picking up garbage.

>>25619444 Blame creates defensive atmosphere and isnt healthy

>>25619521 No need to blame, just don't let the cowboy coder ride his cowboy horse. He will get bogged down under his own bugs and won't bother anybody else. Life will be good :).

Observing how coding is written. It’s funny. It is the complete opposite of what he says.

>>25619534 Just wait till you are the last man standing

Context? In general seems reasonable.

>>25619521 Let's rename "git blame" to "git you are a beautiful person"

>>25619597 All of the top comments believe in collective code ownership meaning that they want push their own bugs to somebody else while they pretend to be le productive programmer by implementing half-baked features.

>>25619608 From my experience it kind of depends on the situation. Sometimes it is faster to just fix the bug than explaining the other guy how to fix it. Especially if it's not a clear-cut bug but an architectural fault or a potential vulnerability or something like that.

Software development is a giant bureaucracy.

>>25619617 I agree but I like how Jimmy explains it. It is completely bonkers to actively push other people's bugs onto others. But I think most of the people in IT are just pretending to be useful.

Useless people now do all kinds of bullshit like style checking, code of conduct, whether your fucking line is too long to view comfortably in their text editor, that you say please and thank you often enough, etc.

How the fuck do you code niggers manage to get paid if you all are leaving your mistakes to the commune to fix? No wonder everything tech related has gone to complete shit

>>25619653 In Europe if you work for over six months, it is pretty much impossible to get fired.

>>25619634 > style checking, whether your fucking line is too long to view comfortably in their text editor That's done automatically nowadays.

>create something >it's broken <WHAT THE FUCK DO YOU MEAN I HAVE TO FIX IT? OMG THIS IS SO PROBLEMATIC, UH HELLO HR DEPARTMENT?!

>>25619653 If you can leave bugs to the community, you're obviously not getting paid

>>25619710 No, it's not done automatically when I save with my text editor.

>>25619724 You can set it up to do that. Or set a pre-commit hook. Either way, the formatting check is in the CI so there's no need for human involvement.

>>25619734 >Yes, just do this, this and that and that and that and you'll be allowed to do this single commit to this repository! Fuck off, you gay soyboy cringelord.

>>25619800 If it's too hard for you to run a formatter, or set in your editor to run it automatically, I don't want your commits anyway.

>>25619807 You're a snob.

>>25619813 No, it's just experience. Uniformly formatted code is easier to read. Imagine if you had a book where every paragraph had a different offset, different line length, and different font size. With big codebases every small readability change leads to huge time savings and less bugs. Not to mention that a person who can't do a simple action like that cannot be trusted to make any kind of complicated code changes.

>>25619832 Then you can go and format it yourself but don't push your crap on others.

And in books every paragraph has a different length. The lines at the paragraph are automatically broken by the text editor. The same way you can enable visual line wrapping in any text editor that doesn't suck.

And fuck everyone who uses spaces for indention.