Aspire to make every codebase look like it has been written by a single expert developer. You will fail dismally at this, but that shouldn’t stop you trying.
Great post Andy. I feel this principle along with the previous post is about getting the team to consider the code as 'our code'. Taking shared ownership and responsibility for the entire codebase (in the archetype of this single expert developer) rather than individuals contributing or detracting from the body of work they are responsible for building and maintaining.
A great leader will provide that vision and then the right amount of space to discover ways to improve flow
Certainly shared ownership is a key part of this. As you say, reaching an understanding that this is "our code" is important, but also that it will eventually become "their code", with recognition of unknown future states of the team is also vital, especially when balancing how many variations of "X" we want to consider healthy within the codebase.
Thanks for coming back to me Andy and apologies for the late reply.
My mind has shifted with your "their code" comment - this gets the team thinking about the future developer and bringing them in as a stakeholder in the present.
Great post Andy. I feel this principle along with the previous post is about getting the team to consider the code as 'our code'. Taking shared ownership and responsibility for the entire codebase (in the archetype of this single expert developer) rather than individuals contributing or detracting from the body of work they are responsible for building and maintaining.
A great leader will provide that vision and then the right amount of space to discover ways to improve flow
Certainly shared ownership is a key part of this. As you say, reaching an understanding that this is "our code" is important, but also that it will eventually become "their code", with recognition of unknown future states of the team is also vital, especially when balancing how many variations of "X" we want to consider healthy within the codebase.
Thanks for coming back to me Andy and apologies for the late reply.
My mind has shifted with your "their code" comment - this gets the team thinking about the future developer and bringing them in as a stakeholder in the present.