Rules help when you remember them. Commitments help when you do not. A personal code works because you wrote it, you can see it, and you can be held to it by the person who matters most: you.
01Why a personal code works
- Decisions made early are easier. It is much simpler to follow a rule you set last week than to invent one at 11 p.m. before a deadline.
- It filters shortcuts. If a tempting option breaks your code, the choice is already made.
- It is shareable. Clients and collaborators can see what you stand for, and teams can adopt a common standard.
- It grows with you. Revisit it every quarter and add what real projects taught you.
Many professions publish codes of ethics for the same reason: shared standards make trust easier. Yours is not a legal document and creates no legal obligation. It is a practical promise to the people who will rely on you.
02Write your Builder's Code
Five promises
Your words are saved in this browser, and in your account if you are signed in. Empty lines show an example on the card.
Go deeperNeed ideas? Examples from each lesson
- Ask first: "I will always ask before I use any image, font, music or code I did not make, and I will keep the license."
- Prove it: "I will only claim a result I can document, and I will tell people what is typical."
- Disclose: "I will always disclose when I am paid or gifted to recommend something."
- Protect people: "I will collect only the data I need and delete it when I do not."
- Write it down: "I will put scope, price and ownership in writing before I start."
- Own mistakes: "I will tell the person affected within a day, and fix it before I explain it."
03Your card
Your card builds itself as you type. Print it, copy the text, and keep it where you will see it when a shortcut starts to look tempting.
Builder's Bastion · My Builder's Code
- I will always ask before I use
- I will only say something is true if
- Before I collect or share
- On every project,
- When I make a mistake, I will
04Your first 30 days
A code only matters if it shows up in your work. Choose the habits you will actually start this month.
Saved automatically Saved
05Your certificate of completion
Still to complete: .
You have completed every lesson. Enter the name you want on the certificate.
has completed The Builder's Code: ten lessons on reputation, ownership, licenses, trademarks, honest claims, privacy, agreements and repair, and has written a personal Builder's Code.
This is a certificate of completion from an independent course. It is not an accredited credential, a professional qualification or legal advice.
06Finish Module 1
Ready to finish?
Mark Module 1 complete to save your progress. You can come back and edit your Code any time.
Key takeaways
- A personal code is a decision made in advance for moments when you are rushed.
- Write promises you can keep, and keep them visible.
- Turn the code into habits: a license log, claim audits, disclosures, a data inventory and written agreements.
- Revisit your Code every quarter and update it with what real projects teach you.
This lesson is general education, not legal advice. Laws and platform rules differ by place and change over time. For a specific situation, talk to a qualified professional and read the terms of each platform you use. Last reviewed 2026-11-02.