Learn to See: course introduction · Lesson 1 of 3
You Already Live by a Code
Learn to recognize a rule behind an ordinary decision before trying to change it.
You say the work matters. You put time aside. Then the time arrives, and you wait to feel ready. Perhaps there is a practical obstacle. Perhaps you are following a rule you have never examined: “I should begin only when I feel confident.” This lesson gives you a way to investigate that possibility.
What we mean by a code
A code is a rule you use to guide a decision. It might be deliberate: check your work before submitting it, keep an agreement, or ask for clarification when a task is unclear. It might also be something you have come to follow without naming it: avoid looking inexperienced, agree quickly to keep the peace, or wait until failure seems impossible.
A useful way to state a possible rule is: “When this happens, I should do that, because…” The first part names the situation. The second names the response. The last part names what makes that response seem sensible to you.
For example: “When someone asks for help, I should say yes immediately, because a good friend never disappoints anyone.” That rule explains more than the single word “helpful.” It identifies a situation in which someone may agree before checking whether they can keep the promise.
A code is not the same as every feeling or every habit. Feeling uncertain is an experience. Opening your phone can be a familiar habit. “Uncertainty means I should postpone this task” is a possible rule connecting an experience with a decision. Do not assume the rule is present until you have examined the situation.
Why the distinction matters
When you describe yourself only as disciplined, lazy, kind, or selfish, you have little guidance about the next decision. A specific rule gives you something you can examine. Is it accurate? Does it fit these circumstances? What happens when you follow it? Where does it stop helping?
“Prepare before you act” can prevent avoidable mistakes. “Prepare until all uncertainty disappears” can make an ordinary first step impossible to begin. The issue may be the scope of the rule rather than the value of preparation itself.
You also need to distinguish a value from the method you use to express it. You can value reliability and discover that saying yes to every request makes you less reliable. Keeping the value may require revising the method.
Christ-centered study, expressed in conduct
In Matthew 7:24–27, Jesus distinguishes hearing his words from putting them into practice. ChristMastery takes that relationship between understanding and conduct seriously. Studying a teaching should lead us to examine how we act when the relevant situation arrives.
The Demigod Code is our contemporary training approach to that examination. Calling a decision rule a code is our teaching language. The passage does not prescribe these lesson stages, and one unfinished task does not measure your faith or worth.
A worked example: the promise you cannot keep
This is an illustrative scenario. Morgan wants to be dependable. On Monday, a colleague asks for help with a report. Morgan has two existing deadlines but immediately promises to finish the extra work that evening. The report is not finished, and the colleague has to make a different plan.
Start with the event: Morgan accepted a request before checking available time. A possible rule is “If I am dependable, I must say yes immediately.” Another explanation is that Morgan misunderstood how long the report would take. Both deserve examination.
Ask what Morgan expected at the moment of agreeing. Was there a fear of disappointing the colleague? An inaccurate estimate? A genuine emergency? The answer matters. We cannot inspect Morgan's motives merely by looking at the missed deadline.
If Morgan confirms the immediate-yes rule, a more usable alternative could be: “When someone requests my time, I will check my existing commitments before promising a deadline.” That preserves the value of dependability while changing how it is practiced.
Guided practice: describe before judging
Choose a small, ordinary decision. You can use Morgan's example if you prefer. Keep your answers private.
Write the situation in concrete terms: what was requested, planned, or encountered?
Write what you actually did. Leave character labels out of this sentence.
Ask what you expected your action to achieve or prevent.
Draft a possible rule: “When ___, I tend to ___, because I expect ___.”
Write one other explanation that could fit. If you do not know what governed the decision, say so.
Example: “When a colleague requested help, I agreed before checking my calendar. I expected that saying no would disappoint them.” This is more workable than “I have no boundaries.” It also leaves room to discover that your expectation was mistaken or that the circumstances were unusual.
Check your understanding
A learner says: “I feel nervous about asking a question, so I must not be ready to learn.” Which part describes an experience, and which part states a possible rule? Write your answer before reading the comparison.
Compare your answer
Feeling nervous describes an experience. Treating nervousness as evidence that learning should not begin is a judgment. A possible rule is “I should learn only when I feel confident.” The scenario does not prove that rule governs every decision the learner makes.
Now try a second case: someone waits to use equipment because the required safety training is incomplete. Is waiting necessarily a harmful code? No. A valid requirement can justify waiting. The purpose of examination is to understand the rule and its conditions, not to label all hesitation an excuse.
What to take into the next lesson
Before continuing, you should be able to describe one action and propose a rule without treating the proposal as proven. If you can only write “I am lazy” or “I am a good person,” return to the situation and name a decision instead.
In Lesson 2, you will examine repeated choices, look for contrary evidence, and distinguish a pattern from a story you have attached to it.
Continue to Lesson 2: What Your Repeated Choices Can Tell You →