Hacker News Reader

I'd like to flip this around for a second. A note to management/leadership:

1) Never assume the person(s) writing the code will be available in the future.

2) Any given sprint should auto-add task/time for documenting and such. An hour or two now could save 5x, 10x or more later.

3) The more critical the feature/functionality, the more important #2 becomes.

View on HN

True, it really depends on what kind of project manager you have in your team. Many are very particular about this, they ensure a thorough transition when an individual quits and make sure knowledge transfer happens properly. On the other hand, I've also met those who have no idea what all systems their project is owning!

#2 is a systemic problem in most environments. Especially in the engineering/enterprise space, many things exist only as "tribal knowledge". This is not just a cs problem, but a general problem that all managers should be aware of.

Agree. But if new person is marketing misses something nbd. If transaction system X or Y stop then continuity is essentially.

With that said/in mind, I couple probably take the stand that this is because (e.g., marketing or finance) believe app dev/IT is identical to them. Bad assumption. Very bad assumption.

Reply on news.ycombinator.com