hey uh what did you write? I got a notification
Very well put, LostMoon.
I have had pretty much exactly this quote as a conversation with interns/coops/freshly graduated hires: your code will be criticized. Itâs not personal - itâs a tool to exact the best solution. If anyone is being mean to you as a person, raise the issue with HR and your supervisor and letâs deal with it.
Also the CoC is more generous than some companies Iâve worked for, in that it explicitly limits public responsibility to times of official representation.
Considering that most kernel development is paid and not volunteer these days, this really shouldnât be hard or different than what these devs do at their offices off-list. In fact, when Iâve read the mailing list, it was mostly Linus himself that is guilty of any of these violations.
I think everything will be fine. Linus will come back and politely tell people that he wonât accept their code. I see nothing wrong with that.
Except it doesnât limit what that means. Do you go to a con, get done fore the day, and go have a beer with friends, and still represent the project? Do you get sick and bitch about it on facebook to your family and friends and still represent the project?
The ground rules are there,msure, but theres no limitations made anb I doubt there will be till some retard throws someone important out because of an above reason.
I imagine at that point it defers to the other rules: on issues of ambiguity, the maintainers ultimately decide. Much like English Common Law, our interest should be on the earliest âprecedent-settingâ cases that come up.
There should be definitions, not accidents.
Wot, you mean Iâm not superior because of my awesome toaster? Deflated
3rd party coc is not about conduct its is about (power to take over control.)
words are words nothing more and if a person is so sensitive about criticism they need to really take a good look at themselves.
it all comes down to how the offended translates what is said to them.
for example:
trans-located cognitive synaptic response syndrome (thinking with the wrong head), something most men do all the time!
atmospheric impaction cranial syndrome (air head) (most women can be accused of that)
and my favourite, Intra rectal cranial insertion (head up the arse)!
back to the topic at hand ask yourself this How many years has linus been at this?
how many years has he had to deal with substandard coding?
would you like your lifes work and the quality youvâe invested in it to be lowered to the point where you have to accept crappy code?
would you rather allow someone to use your code work in profiteering violating the GPL?
If a coder does not understand the standards required for coding they need to learn and follow them or expect harsh criticism.
for heavens sake they are adults heâs not there to babysit them!
and as to standards If you didnât follow the safety standards in my shop (electrician)
first time offence was a severe reprimand.
the second offence was a 1 month reduction in pay
and the third got you fired.
the point is those standards were set to keep you alive, but the simple fact is standards are set to be followed explicitly with out deviation.
So help them learn, rather than being a bully. There is nothing that says criticism is not allowed. What is unacceptable is harassment and abuse. There is a significant difference.
Thatâs totally fine. I would go through a reprimand and firing process (eventually) with a software dev in my company thatâs not cutting the mustard as well.
But I wonât call an all-hands meeting and berate the employee in front of their peers with personal insults. Itâs a private conversation about how the work is not up to the expected quality. And resources on expectations will be provided (if they havenât been already).
No one is saying that the new rule is that bad or wrong code will be accepted. The new idea is that you wonât be personally insulted for offering bad code - youâll simply be told your code is not acceptable for inclusion in the project.
Edit: âNo one is sayingâŚâ okay - there are people saying that. The type who wear tinfoil hats are going crazy trying to insist that this is the new reality.
Keep in mind the BBC is notorious for spreading technopanic, so take this with a grain of salt.
The main takeaway from Linus is this excerpt:
Iâm trying to get rid of my outbursts, and be more polite about things, but technically wrong is still technically wrong, and I wonât start accepting bad code just to make people feel better about themselves.
But if people at least realise that Iâm not part of the disgusting underbelly of the internet that thinks itâs OK to show the kind of behaviour you will find if you really have been reading up on the âdiscussionsâ about the code of conduct, then even that will be a really good thing.
I think this perfectly addresses the key points of the discussion. Of course, thereâs more where that came from so I recommend to read the whole thing.
Iâm trying to get rid of my outbursts, and be more polite about things, but technically wrong is still technically wrong, and I wonât start accepting bad code just to make people feel better about themselves.
Hey, thatâs how I take video engineering. Technically wrong is still technically wrong, like 1080p29.97 when the rest of the workflow is 1080i59.94.
"âBecause I may have my reservations about excessive political correctness, but honestly, I absolutely do not want to be seen as being in the same camp as the low-life scum on the internet that think itâs OK to be a white nationalist Nazi, and have some truly nasty misogynistic, homophobic or transphobic behaviour. And those people were complaining about too much political correctness too, and in the process just making my public stance look bad.â
What on earth was he hearing or were people telling him about how heâs viewed?
Is Linus taking a how to kill SJW course ?
âMale dominated communityâ
They do not want to start that fire.
For computers (and engineering in general), the measurement should be safety and functionallity, not âmuh, opressing meâ.
Jobs and who does them
It is a very fucking hard working jobs. Look at all those women who want to work with hot and cold tons of steel all their life!
Measly 1% if thatâŚ
Software engineer
9%
Crying âthey don´t take our codeâ when the chance of a female submitting code in the first place are between 8 and 15% in the first place is a rather cheap shot!
We need to fix male dominated countries and wars. Male dominated sports, Toilets and burger eaters !
Males canât be the only idiots that do physical stunts and break themselfs!
coding in any language there is grey areas where code may work but is not performing up to standard.
for example if anyone has ever coded in basica they would know that that its fussier than an uptight english teacher!
even the tiniest error flags as syntax error and will not compile or run!
with python, ruby, ocaml, perl, java and others you code in blocks and its easier the make faulty additions to the code.
while minor errors may not cause the program to crash it may adversely affect the expected outcome.
at my old job we had to program plcâs and slcâs a lot and often had to write the programs ourselves. while this may not sound like its crucial we were programming automated machinery that people had to work around. and someone getting hurt by a machine action meant your losing your job and paying their medical bills.
so to me coding is crucial and yes I would be quite a bear to deal with, I trained people to program these machines and if they gave me crap they would surely hear it from me.
maybe not in public but they would hear it well.
the point is linus bas been at this since linux inception more than 22 years ago! and yes he needs a break but he doesnât need a committee to slap his hands for being rude!
If you wantwto submit code, submit it. If its redundant, breaks shit, or does nothitg, fuck off.
Thats how development of what runs the planet works :33333
exactly ! either do it right the first time or expect it to get shit on!
to quote benny the kid on code monkeys
"I fart on your code!, I fart on your code!, i fart on your code!, I dont fart on your code It aint worth a fart!