Totally agree to this! When writing code in teams, keeping the codebase understandable for everyone (not even just on a line-by-line level but more on an architectural level) is a challenge that should be kept in mind at all times. Keep your colleagues informed and also invested in the patterns and standards you want to pursue, review and discuss code to achieve this. My company has a weekly meeting with all devs for this exact purpose.
In a way this also relates to this 3-step process I've read somewhere on Twitter (and I unfortunately can't find the source anymore) — it goes something like this: