Earlier quoted context omitted.
In my experience, if you're working on a green-field project, you're working long hours, making very little visible progress, you have to write a lot of code, make important decisions. All the while management is breathing down your neck and asking 'why isn't it ready yet'. Once the thing is shipped, then all the important people come out of the woodwork, who were surely there all along, 'supporting' you from behind…
> 'But only I can fix that complex race condition, that popped up half a year after development' - well if it was good enough with the bug for people not to notice it for half a year, it's going to be good enough for another half, until the new devs can fix it. From my time at AWS, and in light of the recent DynamoDB dns race condition bug, this is a line of thinking that is problematic. There is so much complexity i…
Long stays in most companies are practically non-existent these days, apart from a few folks who are present for long, unfortunately these people are often called lifers, coasters etc.
Simply put, no one person can say they contributed most to the building of a system. Barring very few rare projects.
So you already need the runbook, documentation model to run things, for the reason people themselves work along those lines.