In the Engineering of the Self - You are both the User and the System. You are directly programming the Self, or you are facilitating that programming. Your choices, behaviors, reactions, experiences, are the result of the programming you practice, or permit.
Every moment of every second of every day, the thoughts we process, the words we say, the ideas we consider, the sounds we hear, are levels of (in many cases unconscious) self-programming. The instructions embedded in our core make up who we are and how we process the world around us.
In the programming (coding) world, Code Reviews can recognize issues in the code and revise them before the finished product (app, website, game) is released. The vetted code is documented (captured) and can be iterated (reused in other ways).
In the enduring Journey of the Self, when last did You perform a Code Review?
"You must learn a new way to think before you can master a new way to be."
-- Marianne Williamson
To Begin - our engagements throughout our days – things we see, hear, experience - they echo and reverberate through our minds and hearts. They enable, reinforce, and impact our fundamental selves.
The only way to change the programming is to first consciously be aware of what it is, and then consciously (and over time) effect (incremental) change.
How about a base level code review? Such reviews are usually held with a Team. But for now, let’s do this one Solo. Unless you have a trusted, considerate, insightful, character person you want to include, and you are willing to listen to. Be Objective. Remember Rumi – In all communication, make sure it passes through 3 gates: Is it True? Is it Necessary? Is it Kind? And don’t forget the added gate incorrectly attributed to Socrates – Is it Useful?
In other words – Are your findings objectively accurate? Is it necessary for them to be communicated to you? (By you?) Are they shared in a considerate, compassionate way (also to you, by you)? Are they helpful? In supporting you in your goals and objectives. You want this process to be sustaining. You may need to do an incremental review in the future. You want to come out of it feeling encouraged. With an awareness of your Self and what you may wish to adjust or adopt.
Before starting, prepare Your Self. This code of the Self, long written, long committed, long executed, can be unexpectedly scary when unpacked (revealed).
§ Begin from a place of calm Reflection. Start with the Breath. Recognize your own Greatness. Not as a replacement for Character (Integrity) – as an indicator of it. Remind yourself (daily) of what the world seeks to remove – your Humanity. Your Reason. Your Insight. You Are, You Do, You Belong. Don’t doubt. Dedicate.
§ Plan when you will sit with this. Take your time. You don’t have to do it all at once, all in one sitting. You can do it in sections (layers). Especially if it is triggering or draining.
§ Take breaks when you need them. Journal (capture/record), and protect, your observations.
§ On the Review itself, Focus on key issues. Things you’ve noticed. Things others have pointed out. Specifically, things impacting your esteem, motivation, performance, effort, wellness.
Start with these questions:
1. What is in your core programming at present? [What is fundamental to who you are? - What you value? What you are drawn to? What you pull away from? What motivates you? What sustains you? What drives you? What discourages you?]
a. Follow-up - whom has (regular) access or input to that core programming?
2. Can you follow (understand) your core programming? Do you know/recall the original source(s) of this programming? Even if you created some of this, was it based on a higher-level programming from an external source? (i.e. did someone (something or some event) affect you at a core level?)
3. Are you consistent in adjusting your programming? (i.e. do you consciously make adjustments or are you driven by, or reactive to, external triggers?)
4. Do you have any contradictory code? (i.e. internal code which works against other internal code)
5. Can you easily and accurately unpack your code programming to understand and determine the root cause? (i.e. do you understand how you got here, and even where here is?)
6. Is this code package (layer) sustainable? (i.e. is this programming something that works for or against your personal goals and core values?)
7. Is this code package (layer) scalable? (i.e. is this programming something that you can continue to use as your commitments, needs, responsibilities evolve?)
8. What features have you recently removed or internalized? What triggered the change(s)? It only takes a thought. Or a (thoughtless) word. Example: An image of something you covet but you (or something that represents you) is not in the image. A subtle suggestion you don’t belong in that tableau. A barrage of these thoughts or images is a continuous programming and reprogramming that we may not be consciously aware of.
As you identify programming that serves you well, consider how you can iterate (reuse) that programming in other areas of your Self. As you identify programming that you determine needs to change, first ensure you can explain (to your Self) the purpose and motivation (reasoning) for that change. Critically important that you can be intentional with this practice and not reactive. We know we can impair as easily as repair as we try to affect change.
There is a DRY aspect to code review, exalting Do not Repeat Yourself. In this code review of the Self, repeated code may be ok. However, consider that you needing to repeat (verbally or behaviorally) your internal programming (core values) to someone with direct access to you is a flag. That is a person who isn’t listening or observing or honoring or accepting who you are. And may be indicative for you of their core programming. Something to consider.
When you have identified necessary change (key word!). Stay objective, stay with Rumi’s 3 Gates, stay kind to yourself. But when you have identified useful, necessary, compassionate, objective change, begin by targeting small, incremental, and clear changes.
· Bundle changes that are related to each other. Connecting changes connects the ideas and behaviors around the changes. Helps you commit and stay on track.
· Mentally Walk-through your approach and Measures. - How would you know if your changes are working?
· What are the Dependencies (Needs or Obstacles) to these changes being put in place?
· Can you make (any of) these changes now? And if not, what do you need to start?
You do not need to Fight your programming. In fact, it is unhealthy when done over a lengthy period. Never Fight who you are. That said, if you are causing harm to yourself or to others, if any aspects of your programming are not serving you, are not in line with your goals and objectives, are in opposition to who you want to be, then ferret them out, and change or remove them. Authenticity is the quest to be our best authentic Selves, not a license for selfish or mean-spirited behavior.
The code review can be the longest, deepest aspect of this Journey of the Self. The length of time it took you to be programmed by the external world and your internal processing of that world, is how long it could take you to adjust that programming. The time shortened by the depth of your commitment, and the consistent, daily effort. No matter how small.
The proverb goes: The day you plant the seed is not the day you eat the fruit.
Start today. #TodayIsTheDay