[rantwasp]

true, but redundancy is hard to build on critical or under-documented parts of the code. It’s also hard to build when the knowledge needed is not something you can just sit down and do a brain-dump in an afternoon (ie you need a lot of context to see the light).

So, you can help people grow and keep your skill polished while you build up job security and hoard critical knowledge. I’m not saying it’s the right thing to do - just saying that I’ve seen it done and it worked for the persons doing it.

[pooya13]

Having a codebase that is so convoluted that only you can work on is really not a skill you should risk your career on. It might work for those people you have seen in a short period, but long term they fall behind as they not only not develop generally valuable skills (because they are constantly working on that project), they also lack the skills to write clean collaborative code, which makes them less employable. So they would be in a very bad situation when that code base loses its value. (due to company going bankrupt or the project being shelved) My argument is not against hoarding critical knowledge. I am saying that by doing so you will be the single person responsible for that area, and therefore won’t have a chance to grow and diversify your knowledge base. I can only imagine a scenario when you are working in a hostile environment with really dumb management where that attitude could be rewarding and protect you. But in that scenario I would be looking for a new job and try to quit anyways. You don’t want to base your career goals on a specific position/employer.