You can’t write software in a vacuum. To write good code, you need to understand the whole program (or at least a very substantial part of it), why certain dec

You can’t write software in a vacuum. To write good code, you need to understand the whole program (or at least a very substantial part of it), why certain decisions were made in the past, the potential ripple effects of a “simple” change, etc. This means that it’s impossible to just swap devs out like factory line workers, otherwise you’re just creating more bugs. For similar reasons, you can’t paint half a canvas and then hand it over to another painter and have him finish it...