4 ms·
It just means people leaving are not that critical. If they were, you would have that documentation or you would be SOL pretty often.
by luckydata 7y ago
It just means people leaving are not that critical. If they were, you would have that documentation or you would be SOL pretty often.
- woutr_be 7y agoI don't think it "just" means that people are not that critical, it's a much deeper issue. All the way from individual engineers to managers to product owners to the company in general. At least in my team, is see: - Managers allowing people to only take on specific work, therefore people are becoming highly specialised - Individual developers don't push others to write documentation, instead they wait until somehow they have to do a task, spend 2 weeks to figure it out, and then write some documentation around it - Individual developers who force themselves to only work on specific pieces. (I think mostly to fuel their ego so they're needed) - The company not encouraging knowledge sharing, or simply not providing good tools for it - Product owners who don't really care about the product
- kortilla 7y agoNo, you can still be critical and not have it hurt the company with just a two week absence. Say a product like Uber ceases new development because of a critical developer leaving who knows how to fix the home grown CI. The company isn’t going to go under in two weeks but it doesn’t mean the dev isn’t critical.