this post was submitted on 06 Feb 2024
384 points (100.0% liked)

196

16555 readers
1598 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
moss@lemmy.blahaj.zone
greembow@lemmy.blahaj.zone
moss@lemmy.world
queue@beehaw.org
funky_rodent@lemmy.blahaj.zone
PeachyMcPeachface@lemmy.blahaj.zone
threegnomes@lemmy.blahaj.zone
greembow@lemmy.world
remotelove@lemmy.ca
Roflmasterbigpimp@feddit.de
qaz@lemmy.world
A_Very_Big_Fan@lemm.ee
qaz@lemmy.blahaj.zone
qaz@lemmy.ca
A_Very_Big_Fan@lemmy.world
qaz@lemmy.dbzer0.com
Qaz@lemmy.ml
qaz@sh.itjust.works
qaz@lemmy.sdf.org
384
Code Rule (sh.itjust.works)
submitted 9 months ago by rambling_lunatic@sh.itjust.works to c/196@lemmy.blahaj.zone
19 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] Cypher@lemmy.world 44 points 9 months ago

noone there is learning

Wrong. Dead wrong.

In the email chain subsequent to this exchange Linus even addressed the fact that the contributor would be better off learning about kernel development by focusing on the removal of unnecessary code and clean up.

No one jumps into kernel development knowing everything.

Maintainers need to teach people, not just about the culture and ethos, but about best practices and Linus had taught people constantly.

He has also learned a lot from others. To suggest otherwise is to think that Linus knew everything about kernel development back when he first began Linux development.