|
|
|
|
|
by dxbydt
1112 days ago
|
|
> there shouldn't be any master in the team who holds the keys to the knowledge kingdom that's exactly what i'm disagreeing with. It sounds like a good feature on paper. In reality, it seldom is. Most east coast companies of significant size, if they do anything sufficiently complex, will have 1, sometimes 2-3 guys, who hold the keys to the kingdom & know everything. The kind of domain knowledge that cannot be transferred in kt sessions. In all the IBs I've worked at, there was always the point person who knows everything about one thing, & if he got hit by a bus, man you were in serious shit. Its just the cost of doing business in that domain, can't really derisk it by writing everything down.
otoh most Valley firms do very generic shit, with young troops recruited every so often, who stay just long enough to make the jump to the next faang. Even in the Valley, you have L8,L9s whose disappearance can cause significant damage. Its simply not possible to transfer all knowledge to rank and file. some things are just very hard. Code has a way of getting very convoluted very fast. End of the day, SWeng is a very young field. There are no rules like multiple people must know your codebase. There are actual prop funds in chicago running out of 1 big R file written by the cofounder. Whole fund runs out of a single R program! No joke. Big world out there. |
|