Your Clean Code Manifesto

Create a short, honest manifesto that captures how your team wants to write, read, and care for code together. This is not a slogan wall — it’s a set of real commitments that reflect who you are as a team and how you want to grow as developers and collaborators.

1. Write three principles that start with “We will…”, “We aim to…”, or similar action-focused language. Each one should connect technical practices (naming, testing, structure, reviews, etc.) with your team’s shared mindset or working culture.

2. Explain why each principle matters. For every point, add a few sentences justifying your choice: – Why is this important for your team specifically? – How does it relate to your strengths, challenges, or working style? – How will this principle help you support one another and improve your project?

3. Make it visible and living. Post your manifesto in your repository wiki or workspace wall. Revisit it mid-semester to reflect on how well you’ve lived up to it and whether your understanding of “clean code” has evolved through experience.

Your goal is to translate abstract clean code ideas into your team’s shared ethos — something you can hold each other accountable to, grow from, and be proud to sign your names under.