Your question is Maintainable Code and Review Discipline. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You're working on a software engineering team shipping features continuously, and you're expected to both write production code and review peers' changes. You want to move quickly without letting readability, maintainability, or review quality slip over time.
How do you write clean, maintainable code while participating in thorough code reviews?