Although certainly intentionally not sharing knowledge can be unintentionally rewarded I don’t think the author’s issue is with poor knowledge sharing so much as unintuitive code that requires knowledge sharing.
Well, you’re right in that it’s a bit more than just “poor knowledge sharing”. But I’d say it’s more specific than unintuitive code that requires knowledge sharing, too - it’s code that is unintuitive primarily because its main reviewers are blind to the exactly how unintuitive it is, and thus a vicious circle persists. We can see this in the author’s recommendation to have such code be reviewed by newcomers as well in order to break the loop.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
Although certainly intentionally not sharing knowledge can be unintentionally rewarded I don’t think the author’s issue is with poor knowledge sharing so much as unintuitive code that requires knowledge sharing.
Well, you’re right in that it’s a bit more than just “poor knowledge sharing”. But I’d say it’s more specific than unintuitive code that requires knowledge sharing, too - it’s code that is unintuitive primarily because its main reviewers are blind to the exactly how unintuitive it is, and thus a vicious circle persists. We can see this in the author’s recommendation to have such code be reviewed by newcomers as well in order to break the loop.