Programming

17326 readers

234 users here now

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

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

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Tribal Knowledge (daedtech.com)

submitted 1 year ago by robjohnson@programming.dev to c/programming@programming.dev

3 comments fedilink hide all child comments

A great post by Erik Dietrich on how poor knowledge sharing is unintentionally rewarded.

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

[–] Jtskywalker@lemm.ee 2 points 1 year ago

Good article. I have worked as a dev for over 10 years and have seen a LOT of really complicated spaghetti code that was only maintained by individuals in silos. Some used to joke about "job security" but I would rather my life not be a living nightmare unable to take vacation without keeping my work phone on me at all times because I'm the single person that knows how to fix a mission critical system. I've been there. It sucks for new people but it also sucks for the keepers of the tribal knowledge. It's exhausting.

Training, documenting, refactoring and replacing to eliminate that is good for everyone. If you are a good dev you won't have to keep tribal knowledge to stay employed.