From Womb to Tomb

All of life has a beginning, middle, and end. A start and finish. The beginning is when we leave the womb. The middle contains the experiences we have while we are alive. The end is the tomb we all eventually arrive at.

Zoom out as far as you can see, and you will see the entire duration of your life on a timeline.

Zoom in, and you will start to see the segments that make up our days. Each day is a 24 hour segment. Each year is 365 days. Each decade is 10 years. A century is 100 years, and most of us won't live out an entire century.

Sequence

Our experience of life can be viewed a sequence of events. The sequence is a succession, each moment a waterfall into the next. If we want to produce a particular outcome 'downstream' all we can do is make a change 'upstream' and witness the result. If the outcome is not what we wanted, then we make another change and let the sequence run again.

In the movie industry, a sequence refers to a particular scene. It's one scene in a movie that we can talk about, for example 'The underwater scene.' What directors do is choreograph smaller events that ultimately make up the entire scene. It's one segment of the whole.

Every event concludes at a specific point in time. If we pre-define the point in time, it's called a deadline. But a deadline also requires a clear definition of what is defined as complete. Open loops only exist in our life to the extent that we have failed to define the criteria for completion.

Our minds create models to define every abstract idea in our mind. Stories are what we make up to understand something that only exists in our minds as an abstract idea. Unknowningly, we tell ourselves stories to explain everything:

  1. The story of a programmer making changes to the program and rerunning the program which runs in a sequence. In order to produce a different outcome, the programmer must insert a new instruction in the sequence, and then that sequence must be rerun.
  2. The analogy of health. To have good health, we must take preventative measures to prevent poor health. Exercise now strengthens our bodies to ward off illness later. If you are already weak by the time the disease is determined, it's too late. We can't go back and change the decisions we made in the past to change what's happening now. Choose health over wealth. The programmer analogy is a powerful once to illustrate the concept of right now. To explain why we are who we are, why we do what we do, why others do, why the world is as it is. It's Karma in action. Who we are is the result of karma. Karma is the underlying intelligence of all experience. Our experience is the result of the programs we run. The program is defined by a set of instructions predefined before they are run. Indeed, our programs have intelligence. They are able to respond and learn from those responses to respond more effectively.

    Sequence

    The sequence is a key concept to grok. Changes downstream are the result of changes upstream. In order to produce a different outcome, different inputs are required. Frustration is created when the outcome is something different than we expected. The error in our ways was expecting a different result than we got. To expect is to assume. The result we get is the result of the output created by the programming that precedes it. Imagine you want a flat tummy. Many people do. The act of imagining doesn't make it so. What we need to imagine is becoming the program that produces a flat belly. Myself, I've given the program the title 'Look Good Naked.' It's only to the extent that I am willing to put my effort into the LGN program, that the outcome I seek becomes possible. Anything is a hope and prayer. The importance of that outcome to me is what gives the spark to make the changes to the program (my habits) possible. Getting clarity into why it's important to me is key. What is the real reason I want a flat belly? Is it to gain the response of someone specific? Feel better? Please my father? Have more energy? Gain respect from my peers? <Looking at something here... do I unconsciously judge others who have a pot belly? Do I judge others who do not value the LGN programming?>

    Point 'Be'

    There's where we are, and where we want to be. Where we are is point a. Where we want to be is point be. We crave a sense of be longing.

    Chords: Belonging

    When playing scales, we only play one note at a time. Yet many notes sound good when played at the same time. The definition of a chord are notes that sound good when played simultaneously. What if we were all notes? It's where we feel a sense of belonging that a chord is strum. Programs: What if we were just one sequence being run by a master programmer? Our program runs in an instant. When it kicks back errors (as it will), the programmer makes some tweaks. HACKS the program, and runs it again. The program feels no pain, it just runs. An output is produced. That is all it is. Nothing personal. Nothing but the meaning we give it. Zoom in: It's 5:30am. I am leaving for yoga in 15 minutes. I write down some subroutines that I will run IN SEQUENCE before I get into my car and drive to SLO: Dress. Yoga Mat. Postacios. Carrots. Bannana. Pants not shorts. Smart and final later. Mangos & Avocados & Banannans as Smart and Final. You are walking so bring you umbrella! OMG: it's the subrountines we run. And we can PLAY IT OUT before it happens in our mind. Debi can't sleep at night because her mind is running the program - playing it out. Testing the hypothesis. The event she is worried about is the outcome. The sequence is the key! 25 postacious max per day. You need to be conscious of your actions. What if point 'Be' folded into the concept of 'Be' that I have written about before, but expanded the idea further to non-duality. "Our thinking is grounded in concrete experiences and that even what seem like quite abstract concepts are linked to our bodily experiences through analogy and metaphor." ~Edward Slingerland Trying Not to Try. What if the key to breaking through dualistic thinking (the cause of much of our confusion in the world) were to 'grok' to concept in my Be chapter? Working on my critiki. Where's my writing on Effort? Consider LESS IS MORE. What am I trying to say? Truly what? I am not sure what is on my agenda today. Oh yea - Franchise Tax & client work. How are you organizing client work? Can I start with a 450 word brief synopsis?


    Life is not a rehearsal. There is no first draft. There is only the 'live' edition of your work.

    When you write as if every word is being read by a million people, you will write better. Your life is being executed according to the program that has been written. The 'code' that makes you who you are is constantly adapting. By design however, you are kept in the dark. You are in the dark every step of the way. Your only objective is to get from point 'A' to point 'Be.' Point A is where you are in this instant. Point 'Be' is where you will be in the next moment. We may buzz with antcipatoin about getting to Point 'Be.' In order for the program to run, it light up the circuit it's on. It's all there really is. Everything in the future is yet to be executed, and everything in the past is no longer relevant to right now. Electricity can explain how it works. Like a program, our awareness is constantly expanding. Like a flashlight filling the room, to see further you must step further. As you step into the light, the darkness is behind you. The past is a chapter that's already been read. You can go back and read it again, but you won't move further through the book when you do. Life is a one-way street. You can only stop or move forward. Stop too long and your liable to get hit. Life is a one-way ticket, you get on at the womb and get off at your tomb. The purpose of your program is simply to get from point a to point 'be.' Seeing where we are (the her and now) and the actions we are taking is the path we are on. Life is a one-way journey from womb to tomb. So what's the point of it all? What's point B? It's where you will 'be.' Where you will be is defined by how you are 'being' right now. Point B is actually Point 'Be.'


    It's the artifacts we leave behind that define who we were. It's the obstacles we overcome that define who we become. Artifacts are great, but will we be here to enjoy them? The process is simply to make progress. To move from a space of unknown to known. The process is permanently impermanent. Change is part of the design. The challenge is the point. If it's not challenging, we'll find ways to make it so.

    Driven by frustration

    Frustration is evidence the process is working. As programs designed to solve problems, frustration is what drives us. To resolve the frustration is the carrot. You may fail 10x for every success, and that's why success deserves to be celebrated. You will hit obstacles that require education. Education followed by experimentation. Knowledge without application means little. Frustration, obstacles, setbacks, failures, mistakes - they are all part of the process of progress. The only real failure is failing to learn from our mistakes. <You can break the process down with 8 UP. Can I use a form of 8up to create a template for Ukulele chords?> we need templates to ... In the absolute simplest terms, the purpose of our 'program' is to produce an outcome. To move from point A (where we are) to point B (where we need to be). In the process, we will encounter obstacles. The obstacles must exist for the program to work. Without obstacles, we are only a witness to the world. Obstacles require us to engage. To resolve and think.

    Decode the program

    A program is written to produce a particular outcome. It's less about discovering our 'life' and more about finding our 'immediate' purpose. Knowing your life's purpose is like trying to write a business plan before you've run a business. It doesn't work. I once asked a very successful brewery owner if he ever looks back at the business plan he wrote. He said he only looks at it to see how ignorant he was about running a brewery! As it is with our life. We can't see any further ahead that the steps taken. When you look back on your life, you may laugh at how ignorant you were about life. Software developers (and even pharmaceutical companies) often create a product, fully knowing that they don't know exactly how their solution will be utilized. Often the actual use is far different. You can build it for one purpose, only to find it's true value lies in something completely different (read the history of Viagra).


    Only by breaking down the process, can we see what it takes to achieve a desired outcome. Frustration occurs when we expect a different outcome. Insanity is doing the same thing expecting a different outcome. Thus frustration is an indicator that the process is unfolding. Where we get tripped up is when we demand the outcome without respecting the process we must go through to produce the outcome! Overcoming Obstacles are part of the process! Getting frustrated because you aren't producing the result you desire? If the outcome is $1mil, then what is the process? Break it down. Look for the tools. Run the program. Fix what is causing the errors. An ease about the system the life runs within. Accepting the framework is a huge relief. Knowing that system is there! To make a million bucks, you will no doubt have to overcome obstacles. Many are internal, many are external. You are exactly where you need to be. Trust in the perfection of the moment. I often beat myself up for the things I didn't do (i.e. the course on Udemy). But what if the reason you didn't is so that you would NEED to take PubWriter further?

    # Errors as indicators Errors are obstacles we are required to overcome before we can run the program. There's absolutely nothing wrong with errors! If not for errors, we wouldn't have a clue on how to resolve them. Obstacles are part of the process. Our program was written to overcome the obstacle. By design. There'd be no purpose to the program if there were not obstacles to overcome. Overcoming obstacles are the purpose of the program! Running the same program twice... and errors pop up. Something was thrown in that we missed. Living skillfully is all about paying close attention to the creation now so that errors are less likely later. Let's look at real life errors: Whenever someone responds differently than we expected, we have just made an error. Maybe we said something they took to mean something else. Maybe it was a way we looked at them that triggered a subconscious memory resulting in an emotion even they couldn't see coming. Maybe we made an assumption, and in doing so, failed to consider an important aspect of the process. It's about being able to resolve the errors quickly when they do arrive. It's about seeing the err in our ways - how we created the error. How we were the cause. Pause and look for the cause. Nothing is ever wrong, we just need to adjust our inputs according to the outcome produced. There are no insurmontable errors, only challenges ahead. # Checklists Ode to Yoga The key to equanimity (keeping cool under pressure) is understanding that the obstacles are simply there to challenge the program. The obstacles exist to give the program something to respond to. I view my Yoga practice as preventative maintenance. I have seen that yoga helps prepare me for the unseen obstacles ahead. Maybe it's not so much preventative maintenance, as much as it's programming. When I really do Yoga, I am installing subroutines that better equip 'my program' to overcome the obstacles ahead. I feel that without yoga and meditation, I am ill prepared for what lies ahead. When I work too much, I suffer pings of burnout. Too much 'self-care' also has it's consequences. We must keep an eye on many different areas of our life. It's an ongoing balancing act. With this understanding, the phase of our life called 'retirement' is something quite different. I feel it's a greater freedom to do what we want, assuming we've been fortunate to set ourselves up financially, but we still must balance our selfish motives with 'problems' we are programmed to solve. Finding a healthy balance is the key aspect to running a program with error free outputs.