Blog

  • Helping People See Who They Already Are

    Years ago, while I was working at a growing consumer-products company, one of my coworkers said something about me that I have never forgotten:

    “Erich makes everyone 10% better.”

    At the time, I received it as a generous compliment. I did not yet recognize it as evidence.

    Recently, while thinking about identity, personal development, and the kind of work I want to do in the future, I remembered that statement differently. I began looking back over my life for patterns—not just things I hope are true about me, but things demonstrated through real events, repeated behavior, measurable results, and the testimony of other people.

    A sentence emerged:

    People are more able after working with me than they were before.

    That does not mean I am responsible for their success. I do not perform their work for them, make their decisions, or possess some magical ability to transform anyone who comes near me.

    It means I often help people see something in themselves that they could not previously see, translate their existing experience into a new possibility, and build enough structure for them to act.

    Recovering a Lost Professional Identity

    One woman I knew had previously been a nurse, but addiction had cost her nursing license.

    The professional loss was not the only loss. She had also lost her belief that she could ever be a nurse again. Her past failure had become the defining evidence she used to understand herself.

    I could not restore her license. I could not study for her, take an examination for her, or rebuild her life on her behalf.

    What I could do was help her see that losing the ability to practice nursing did not erase the person who had become a nurse. The training, intelligence, care, experience, and calling had not disappeared. They had been buried under addiction, consequences, and shame.

    I helped her see herself as a nurse again.

    She did the work.

    When she was given permission to retake the examination, I was the first person she told. When she passed, I was also the first person she told.

    Her restoration was hers. But I had helped her believe that restoration was possible before she could fully believe it herself.

    Turning an Ambition Into a Plan

    Another person wanted to become a full-time YouTube creator.

    He had the desire, but he did not have a plan. More precisely, he did not know how to make a plan.

    A dream such as “I want to become a full-time creator” can feel clear while remaining almost useless as an operating instruction. There is no obvious task called “become successful on YouTube” that someone can complete on Tuesday afternoon.

    I helped him add structure to his thinking.

    We broke the ambition into stages, translated those stages into tasks, and created review cycles through which he could evaluate what was working and decide what to do next.

    I did not make his videos. I did not develop his talent, attract his viewers, or endure the repetition required to become successful.

    He did the work.

    He followed the plan, created the videos, and eventually became a full-time YouTuber. Later, he told me that the systems we developed had made a major difference in his life.

    I did not give him the dream. I helped him build a bridge between the dream and his daily behavior.

    Translating Experience Into a New Career

    A third person had once worked as a programmer but had been let go and no longer wanted to continue in software development. When I knew her, she was living with her mother and trying to support herself through part-time photography work.

    Her résumé did not obviously say “marketer.”

    But her experience did.

    Running a photography business required her to understand visual communication, customer needs, technology, branding, and social media. I helped her frame that experience in language a business could understand, and she was hired into a marketing role.

    Later, I helped her make another transition.

    Much of the work she had been performing in marketing was also business-analysis work: understanding needs, organizing information, navigating systems, and helping people turn business requirements into action. We reframed what she had already done so that she could accurately present herself as a business analyst.

    That transition required more than my recommendation. She had to believe the interpretation herself. She then had to communicate it credibly through multiple interviews until other people believed it too.

    She got the job.

    More than a year later, she wanted to move again, this time into the Salesforce ecosystem. I helped her think through the interview questions and position her prior experience. She got that job as well.

    She later referred her husband to me.

    He was a middle-school mathematics teacher who wanted a sales position at Shopify. He had no formal sales title and assumed that meant he had no sales experience.

    I helped him understand that much of teaching is persuasion.

    Every day, he was already trying to gain attention, explain value, overcome resistance, adapt a message to an audience, and persuade children that mathematics was worth learning. He had been selling. The product was mathematics, and the customers were reluctant middle-school students.

    The underlying capability was already present. The title was missing.

    He learned how to describe that capability, Shopify recognized it, and he was hired.

    In both cases, the work was not inventing a false identity. It was finding truthful evidence that the desired identity was already emerging.

    Reasoning Up From Existing Assets

    Another woman came to me while feeling fragmented across several different roles.

    She was consulting for a local clothing retailer, working for a construction manager who operated a wedding venue, doing wedding planning on the side, and carrying the history of a clothing company she had previously started.

    She did not know how the pieces fit together.

    We began by looking at her assets rather than her confusion.

    She understood clothing, branding, events, business operations, communication, and public presentation. Instead of beginning with the question, “What completely new person should you become?” we asked, “What could be built from what is already here?”

    Over time, she decided to relaunch her clothing brand with a larger purpose: helping young women learn about business. She became a real estate agent. She briefly served as a spokesperson for a national beverage brand. She then started a podcast connected to her business vision.

    I did not choose her final direction for her. I helped her reason upward from the evidence of what she had already built, learned, and demonstrated.

    Helping My Wife Think Bigger

    The original inspiration for much of this work was my former wife.

    When we started building businesses together, she was a stay-at-home mother. Over the years, I helped her begin and operate several ventures, including affiliate businesses, a knitting company, a photography business, and eventually a property-management company.

    I helped name the businesses. I funded them. I provided ideas, guidance, marketing support, technology, and encouragement.

    But she operated them.

    Years later, she acknowledged that I had helped her start the property-management company and had encouraged her to think bigger about what it could become.

    That matters to me.

    Long before I had language for identity development, coaching, evidence reviews, or business systems, I was already trying to help someone I loved see that her current role did not exhaust her potential.

    When Someone Does Not Change

    Not every story ended with a career transition.

    I once met a woman who had spent her entire working life in restaurants. At the time, she was working in the kitchen of a gourmet coffee shop. We became acquainted when she advertised that she was beginning to clean houses for additional income.

    I hired her.

    During our conversation, she admitted that she did not understand the business side of what she was trying to start. I told her that I loved talking about business and offered to help her.

    She agreed, then hesitated. I pursued the idea, and she eventually accepted.

    When we began meeting, I discovered that she did not truly want a house-cleaning business. She wanted more money and had a partial desire to enter the business world outside of restaurant work.

    I offered to help her over a series of weeks in exchange for her helping me develop a personal-growth program I was building. I paid her for that work partly because I wanted her to experience evidence that she already could perform business work.

    She learned a great deal and made meaningful contributions.

    But she did not change careers. She continued working at the same coffee shop, and our relationship eventually ended.

    For a long time, I could have interpreted that story as a failure—hers, mine, or both.

    I now see something more precise.

    I helped her encounter and practice a different possibility. But I was more committed to her transformation than she was. Her initial hesitation was information I should have taken more seriously.

    A person must not only want the result. They must want the change and accept ownership of the work required to produce it.

    I can recognize potential. I can translate experience. I can create an opportunity, build a structure, and offer encouragement. I cannot provide another person’s desire, consent, perseverance, or agency.

    That story does not disprove my ability to help people. It puts a necessary boundary around it.

    Development Is Not the Same as Rejection

    This realization also helped me understand why I have sometimes felt frustrated with people who wanted support but did not want to change.

    Growth is one of my deepest values. I instinctively look at people, businesses, and systems and see unrealized capacity. When someone tells me about a problem, I begin imagining what could be clarified, repaired, practiced, or built.

    But not everyone who wants support is asking for transformation.

    Some people want to be understood. Some need companionship while they grieve. Some are exhausted. Some are afraid. Some are not ready. Others genuinely do want the discomfort of their situation relieved without accepting the cost of changing it.

    Those are not all the same condition.

    My gift becomes unhealthy when I assume every person wants the future I can see for them. It becomes controlling when I treat another person’s reluctance as a problem for me to overcome.

    An invitation to grow must remain an invitation.

    A Biblical Pattern of Development

    The Bible does not present human beings as static.

    Paul writes in Romans 5 that suffering produces perseverance, perseverance produces character, and character produces hope. Character is not merely declared. It is formed through repeated responses to reality.

    Luke writes that Jesus grew in wisdom and stature, and in favor with God and people. Jesus was not morally defective, yet his human life still included development. Identity and growth are not opposites. A person can truly be who they are while still growing into a fuller expression of it.

    Jesus’ parable of the talents also describes people receiving something of value and being held responsible for how they steward it. The faithful servants do not bury what they have been given. They put it to work.

    Many people bury their abilities without realizing it.

    Their gifts are hidden beneath shame, an inadequate job title, a lack of structure, a painful failure, or a belief that their experience does not count. Sometimes all they need is for someone to help them examine the evidence differently.

    Jesus also taught that what comes from within a person is what ultimately comes out into the world. Elsewhere, he said that trees are recognized by their fruit.

    That suggests that identity should not be built only from desire.

    It should also be examined through evidence:

    What do I repeatedly produce?

    What kinds of problems do I instinctively solve?

    What do other people consistently experience around me?

    What has remained true across different jobs, relationships, businesses, and seasons?

    What evidence challenges the story I would prefer to tell?

    Planting, Watering, and Letting Go

    Paul gave perhaps the clearest boundary when he wrote that he planted, another person watered, but God gave the growth.

    Planting matters.

    Watering matters.

    Neither is the same as creating life.

    I can help someone recover a professional identity, but I cannot study for her.

    I can help someone construct a plan, but I cannot create his videos.

    I can help someone translate her experience, but I cannot interview on her behalf.

    I can help someone see that teaching contains the foundations of selling, but I cannot make a company hire him.

    I can help someone see a possible future, but I cannot make her want it.

    My contribution is real, but it is limited.

    That is not a disappointment. It is freedom.

    The Identity I Can Honestly Claim

    After looking at these stories, I can say something more grounded than “I want to help people.”

    I can say:

    I help people recognize capabilities they already possess and build structures through which they can act on them.

    I can also say:

    People are more able after working with me than they were before.

    Not every person. Not in every circumstance. Not because I possess the power to change them.

    The pattern appears when a person has real capacity, wants a different future, is willing to examine the evidence, and accepts responsibility for doing the work.

    My role is to see, translate, structure, equip, encourage, and sometimes provide an initial opportunity.

    Their role is to choose and act.

    God gives the growth.

    That is the kind of work I have been doing for much of my life.

    It is also the work I want to become more deliberate about doing next. And it’s the work I’m doing at 4-Year U.

  • Emotional GTD: How to Process Feelings Instead of Acting on Them

    One of the most helpful insights I’ve had recently is that emotional maturity is a lot like Getting Things Done.

    In GTD, David Allen teaches that your mind is not for holding vague, unresolved inputs. Your mind is for having ideas, not storing stress. So you capture what is on your mind, clarify what it is, organize it into the right place, and then decide what, if anything, needs to be done.

    I realized emotions work the same way.

    For much of my life, I did not know how to process emotions. I did not have the vocabulary. I did not have the categories. I had feelings, impulses, longings, fears, griefs, attractions, disappointments, and hopes running through me, but I did not know how to sort them.

    So they all went into giant buckets.

    “I feel bad.”

    “I want her.”

    “I’m angry.”

    “I’m rejected.”

    “I need to do something.”

    Those buckets were too big.

    And when your emotional buckets are too big, you cannot process what you are actually experiencing. You either suppress it, act on it, overthink it, fantasize about it, spiritualize it, or try to solve it immediately.

    But not every feeling is a command.

    Some feelings are just inbox items.

    Feelings Are Inputs, Not Orders

    Let’s say I see an attractive woman.

    The old route might have been:

    Attraction → fantasy → lust → emotional escape.

    But recently I started practicing a different route:

    Attraction → awareness → classification → respect → release.

    Instead of immediately imagining being with her, I pause and ask, “What am I actually feeling?”

    That question matters.

    Because attraction is not one thing. It is a bundle.

    Attraction might include physical desire. It might include appreciation. It might include curiosity. It might include longing. It might include loneliness. It might include grief. It might include hope. It might include a nervous-system response that feels like urgency, even when nothing actually needs to happen.

    When I only had one bucket called “I want her,” everything went there.

    But “I want her” might actually mean:

    • I notice beauty.
    • I admire her discipline.
    • I am curious about who she is.
    • I want to be chosen.
    • I want a wife.
    • I want closeness.
    • I feel lonely.
    • I feel physically attracted.
    • I am projecting a future onto someone I do not know.
    • I am looking for emotional relief.

    Those are not the same thing.

    And because they are not the same thing, they do not require the same response.

    Emotional Granularity Is Emotional Maturity

    A person with poor emotional granularity has only a few labels:

    “I’m mad.”

    “I’m sad.”

    “I’m attracted.”

    “I’m stressed.”

    “I’m fine.”

    But a person with growing emotional maturity learns to say:

    “This is disappointment.”

    “This is grief.”

    “This is longing.”

    “This is lust.”

    “This is admiration.”

    “This is curiosity.”

    “This is fear.”

    “This is shame.”

    “This is loneliness.”

    “This is appreciation.”

    “This is attachment.”

    “This is hope.”

    That precision changes everything.

    Because once you accurately name the feeling, you are no longer trapped inside it. You can relate to it. You can bring it before God. You can decide what kind of response fits reality.

    If it is lust, I need to interrupt it and stop using someone’s image for my own gratification.

    If it is appreciation, I can simply say, “That is beautiful,” and release it.

    If it is curiosity, I can notice that I am drawn to someone without needing to build a whole future in my mind.

    If it is longing, I can feel the ache instead of trying to medicate it with fantasy.

    If it is loneliness, I can care for my heart without assigning a stranger the job of saving me.

    If it is grief, I can let myself mourn without turning the pain into a mission.

    The Emotional Inbox

    This is where the GTD analogy becomes useful.

    In GTD, an input lands in your inbox. You do not immediately act on every input. First, you clarify what it is.

    Is it actionable?

    Is it reference material?

    Is it trash?

    Is it someday/maybe?

    Is it waiting for someone else?

    Is there a next action?

    Emotions can be processed in a similar way.

    “I saw a beautiful woman” is an inbox item.

    Then I clarify:

    What kind of attraction is this?

    Is it appreciation?

    Is it physical desire?

    Is it curiosity?

    Is it longing?

    Is it loneliness?

    Is it lust?

    Is it grief?

    Is it fantasy trying to start?

    Then I organize it.

    Appreciation goes in the “bless and release” bucket.

    Lust goes in the “interrupt and do not feed” bucket.

    Longing goes in the “feel this with God” bucket.

    Loneliness goes in the “care for myself and reconnect with real life” bucket.

    Curiosity goes in the “notice without forcing action” bucket.

    Grief goes in the “make room to mourn” bucket.

    Hope goes in the “hold lightly” bucket.

    Not everything requires a next action.

    That sentence alone is freeing.

    Why the Buckets Matter

    I have noticed that when my categories are too broad, my reactions become too intense.

    This has been true not only with emotions, but also with relationships.

    For example, if the only categories I have for women are “friend” and “wife,” then every interesting woman becomes overcharged. If I enjoy her presence, if she is kind, if she is beautiful, if she is spiritually thoughtful, if she laughs at something I say, if there is a spark of curiosity, my mind tries to file her under “potential wife.”

    That puts too much pressure on the moment.

    It puts too much pressure on her.

    It puts too much pressure on me.

    A better filing system has more categories:

    • acquaintance
    • friendly person
    • woman I admire
    • woman I am physically attracted to
    • woman I am curious about
    • woman I enjoy but should not pursue
    • woman who is emotionally unavailable
    • woman who is spiritually aligned but not relationally available
    • woman I could intentionally ask out
    • woman I am actively dating
    • woman I am discerning for marriage

    That gives reality more places to go.

    And when reality has more places to go, I do not have to force every meaningful interaction into a marriage narrative.

    The same thing is true emotionally.

    If every ache becomes “I need a woman,” then I will use women as emotional containers for things that need to be processed elsewhere.

    Maybe I do not need a woman in that moment.

    Maybe I need to feel grief.

    Maybe I need to pray.

    Maybe I need to go for a walk.

    Maybe I need to sleep.

    Maybe I need to acknowledge loneliness without panicking.

    Maybe I need to create something.

    Maybe I need to remember that desire is not an emergency.

    Desire Is Not the Enemy

    None of this means desire is bad.

    Desire is part of being human.

    Attraction is not automatically lust. Longing is not automatically weakness. Appreciation is not automatically obsession. Curiosity is not automatically a calling to pursue someone.

    The problem is not that I feel.

    The problem is when I do not know what I am feeling, so I let the feeling drive.

    That is where fantasy, impulsivity, rumination, and emotional overreach come in.

    A mature response is not suppression.

    A mature response sounds more like this:

    “I feel attraction.”

    “My body is awake.”

    “My heart feels longing.”

    “My mind wants to create a story.”

    “She is a person, not a solution.”

    “This feeling does not require immediate action.”

    “I can bring this to God.”

    “I can bless and release.”

    That is not passivity. That is self-leadership.

    Learning What I Was Never Taught

    Some people grow up in homes where emotions are named, welcomed, and guided.

    Others grow up in homes where emotions are ignored, mocked, punished, stifled, or treated as inconvenient.

    If you were never taught how to process emotion, you may think the problem is that you feel too much.

    But maybe the real problem is that you were never given enough categories.

    You were handed a junk drawer and told to keep the room clean.

    So now the work is not merely to “control your emotions.”

    The work is to learn how to identify them, classify them, feel them, and respond wisely.

    That is emotional stewardship.

    That is emotional GTD.

    A Simple Practice

    The next time you feel something strong, try this:

    1. Pause.
    2. Name the broad category: “I feel attraction,” “I feel anger,” “I feel sadness,” “I feel fear.”
    3. Get more precise: “This is longing,” “This is disappointment,” “This is loneliness,” “This is appreciation,” “This is lust,” “This is grief.”
    4. Ask what it is asking for.
    5. Ask whether it requires action.
    6. If it does not require action, feel it without obeying it.
    7. Bring it to God.
    8. Return to your life.

    That is the practice.

    Not every feeling needs to be solved.

    Not every attraction needs to become a fantasy.

    Not every longing needs to become a plan.

    Not every ache needs to become a text message.

    Not every beautiful thing needs to be possessed.

    Sometimes the faithful response is simply:

    “I see what this is. I feel it. I honor what is true. I release what is not mine. I return to God and to the life in front of me.”

    Final Thought

    Emotional maturity is not becoming less emotional.

    It is becoming more precise.

    It is learning to say, “This is what I am feeling. This is what it means. This is what it does not mean. This is what I will do with it.”

    That precision creates freedom.

    Because once a feeling has been named, it does not have to rule you.

    And once an emotion has been placed in the right bucket, your soul can stop treating every internal signal like an emergency.

  • What If AI Imagined a New Way to Compute? I Asked It To.

    What If AI Imagined a New Way to Compute? I Asked It To.

    An experiment inspired by Nick Bostrom’s Superintelligence

    In Nick Bostrom’s book, Superintelligence, one of the ideas is that a sufficiently advanced AI might not just improve upon our existing computational paradigms — it might invent entirely new ones. Ones we haven’t thought of yet. Ones that don’t look like chips, transistors, or binary logic at all.

    That got me wondering:

    Could today’s AI — not a superintelligence, just the models we have now — start sketching out what those new paradigms might look like?

    So I ran an experiment.

    I asked both ChatGPT and Grok to think seriously about novel approaches to computation (and at the end having them talk directly to each other). I asked them to start with philosophy, but then ground the ideas in physics and mathematics we already understand. I wanted to see what they would come up with – if there was any way to exploit untapped areas for computing purposes.

    What came back surprised me. They converged on an idea rooted in topological physics — the same branch of math that earned a Nobel Prize in 2016.

    Here’s what they proposed: Topological Field Computation: Programmable Hamiltonians in Metamaterials.

    The Big Idea: Topology as a Foundation for Computation

    In physics, certain properties are “topologically protected” — meaning they’re robust against small disturbances, imperfections, or noise. Think of the difference between a donut and a sphere: no matter how you stretch or deform a donut, it still has a hole. That hole is a topological invariant. You’d have to tear the thing apart to change it. In quantum and photonic systems, analogous invariants protect certain physical states from falling apart when things get noisy.

    For computation, this is a very attractive property. Our current computers spend enormous energy on error correction and precise control precisely because standard physical states are fragile. What if you could build computational states that were inherently hard to disturb?

    The AI models proposed using a specific model from condensed matter physics — the Su-Schrieffer-Heeger (SSH) model — implemented in photonic waveguide arrays as a testbed for this idea.

    Grok: Towards Topological Field Computation

    Grok took a broad, visionary approach. It lays out a full conceptual framework for what it calls topological field computation, built around three core ideas:

    Memory as stable curvature. Rather than storing information in a bit that’s either 0 or 1, imagine storing it in the shape of a field — a topological configuration like a vortex or soliton. These configurations are stable not because you’re actively holding them in place, but because the mathematics of the space they live in makes them hard to destroy. Grok calls this “stable curvature in configuration space.”

    Addressability as landscape navigation. To read or write information, you don’t flip a switch — you navigate an energy landscape. You tune parameters to move between valid topological states, like hiking between valleys in a terrain. Crucially, if the terrain is topological, the paths between states are more reliable and the states themselves are more distinct.

    Intelligence as Hamiltonian sculpting. The most speculative and interesting idea: what if a system could adaptively reshape its own governing equations (its Hamiltonian) in response to feedback? This would be a form of hardware-level learning — not software running on static hardware, but the physical substrate itself adapting.

    To test whether any of this is real and not just beautiful theory, Grok proposed a minimum viable demonstration (MVD): build a small SSH photonic lattice in a silicon-on-insulator chip (a mature, manufacturable technology), and compare it against a topologically trivial lattice with identical specs.

    The key falsifiable claim:

    The topological system should maintain high routing fidelity with fewer control inputs and less energy than the trivial one.

    If it doesn’t, the theory needs revision.

    Grok also honestly addresses the hard problems — sensitivity to cross-talk between waveguides, partial observability (you can’t watch every part of the system at once), and the challenge of scaling beyond a handful of unit cells.

    ChatGPT: Topology as Control Compression

    ChatGPT’s approach is narrower and more rigorously experimental in its framing, but it homes in on what may be the most important single question hiding inside Grok’s broader vision.

    The central hypothesis:

    Topological protection compresses control dimensionality.

    Here’s what that means in plain terms: Any real physical computing system drifts. Temperature changes, fabrication imperfections, and environmental noise all push your system away from where you want it. To compensate, you need feedback control — sensors that detect drift and actuators that push back. In most systems, as you add more components, the number of control inputs you need scales up roughly linearly. This becomes a serious bottleneck.

    ChatGPT’s asks: does topology break this scaling? If a topological system’s important states are inherently stable, maybe you need far fewer “nudges” to keep the system on track. The approach formalizes this as a control-compression curve: plot routing fidelity against the number of effective control degrees of freedom, and see if the SSH lattice reaches high fidelity (>90%) with a smaller control rank than a matched trivial lattice.

    The experimental setup is elegant in its fairness: fabricate both systems on the same chip, subject them to identical drift protocols (±10°C thermal ramps with spatial gradients), and give them identical actuator budgets. Any difference in performance is attributable to topology, not experimental conditions.

    ChatGPT also introduces a clean mathematical handle for the comparison: the condition number of the sensitivity matrix — essentially, how efficiently does a unit of control effort translate into a unit of useful correction? A lower condition number means better-conditioned control, less wasted effort, and more stable feedback loops. The prediction is that the topological SSH system should show meaningfully better conditioning.

    Importantly, ChatGPT maps out all three possible outcomes honestly:

    • If SSH wins: topology is a genuine control-theoretic resource, not just a curiosity.
    • If SSH ties: topology helps with static disorder but not dynamic stabilization — still useful, but the stronger claim fails.
    • If SSH loses: the advantage only appears in nonlinear regimes, and the linear test is the wrong arena.

    This kind of pre-registered, falsifiable structure is exactly what makes a proposal scientifically credible rather than speculative hand-waving.

    Where the Two AI Models Agree (and Where They Differ)

    Both approaches agree on the core physical setup: SSH lattice in silicon photonics, compared against a trivial baseline, with the key metric being how hard it is to maintain functional behavior under drift. They agree that the interesting question isn’t just “does topology survive disorder” (that’s already known) but “does topology reduce the cost of control.”

    Where they differ is in scope and emphasis. Grok builds a grander intellectual framework — the memory/addressability/intelligence triad gestures toward a full paradigm for field-based computation, with implications for neuromorphic hardware, analog optimization, and even quantum simulation. ChatGPT drills down into the control-theoretic machinery, giving you the specific matrices, metrics, and statistical tests you’d need to actually run the experiment and publish the result.

    They’re complementary. Grok gives you the why, ChatGPT gives you the how to test it.

    Why This Matters

    If the core hypothesis holds up experimentally, the implications are significant. Right now, scaling programmable photonic or analog systems is limited not primarily by fabrication — silicon photonics is mature — but by the exploding complexity of the control layer. Every component you add potentially requires new sensors, new actuators, new feedback loops. Topology, if it genuinely compresses control dimensionality, could change that scaling relationship.

    That’s not a path to replacing digital computers. But it could be a path to a new class of hardware that’s particularly good at analog optimization, physical neural networks, or robust signal routing — and that does it with substantially less overhead than current approaches.

    And at a more philosophical level: this is exactly the kind of thing Bostrom was pointing at. Not magic, not science fiction — but a serious engagement with physical principles we already understand, applied in ways we haven’t fully explored. Today’s AI didn’t invent topological physics. But it did ask a question about it that researchers haven’t fully answered yet.

    That seems like a reasonable start – and a big leap from where we were in 2016.

  • Velocity, Acceleration, and Safety: Why Humans React to Change, Not Motion

    Velocity, Acceleration, and Safety: Why Humans React to Change, Not Motion

    Human conflict is often a response to changes in tempo rather than to the actions themselves.

    • We argue morality when the issue is tempo.
    • We argue legality when the issue is acceleration.
    • We argue intent when the issue is predictability.

    By naming acceleration as a distinct variable, we gain something valuable: the ability to describe discomfort without immediately assigning blame.

    Instead of asking:

    • Is this right or wrong?
    • Is this allowed or forbidden?
    • Is this good or bad?

    We can first ask:

    • Has the rate of change exceeded the system’s capacity to adapt?

    That question is calmer.
    More precise.
    And often more honest.

    Humans implicitly assume continuity unless signaled otherwise.

    We expect the world to proceed tomorrow at roughly the same pace it did yesterday. We assume people, institutions, technologies, and environments will behave with some degree of temporal consistency. This assumption is so deep that we rarely notice it – until it’s violated.

    And when it is violated, we don’t experience it as “a change in velocity.”

    We experience it as threat.

    Not moral threat.
    Not legal threat.
    Not even intentional threat.

    Just instability.

    In physics, there’s a principle so basic it’s often overlooked: constant velocity is indistinguishable from rest.

    According to Newton’s First Law, an object moving at a constant speed in a straight line experiences no net force. From inside the system, nothing feels like it’s happening. There is no signal. No disturbance. No information.

    Only when velocity changes, such as when an object accelerates or decelerates, does force become detectable.

    Acceleration is motion made visible.

    This distinction matters far beyond physics, because humans operate the same way.

    Speed Itself Isn’t the Issue — Speed of Change Is

    People notice when things are moving faster or slower than they are comfortable with, but they have blunt, imprecise words to objectively measure what they are feeling:

    • “Things are moving too fast”
    • “Progress is too slow”
    • “Technology is accelerating”
    • “The government is overreaching”
    • “This relationship is going nowhere”

    Speed alone is rarely what’s being perceived:

    • If something moves quickly and has always moved quickly, it feels normal.
    • If something moves slowly and has always moved slowly, it also feels normal.

    What humans detect (emotionally and immediately) is acceleration: A sudden increase or decrease in tempo is the signal that something has changed, and that signal is interpreted first as a safety question, not as a value judgment.

    Imagine a car at rest next to you. You likely pay no attention to it. But the moment it begins to move towards you, you notice.

    That’s safety at rest and risk in motion.

    Acceleration as a Universal Disturbance Signal

    Across domains, the same pattern appears.

    Relationships

    • A relationship that escalates steadily often feels safe, even if it moves faster than average.
    • A sudden jump — declarations of love, commitment, or permanence without ramp-up — feels aggressive or destabilizing.

    Conversely, a relationship that stalls after steady forward motion triggers discomfort. The issue isn’t slowness. It’s deceleration without explanation.

    Law and Governance

    • Laws that exist but are enforced predictably fade into the background.
    • When enforcement accelerates abruptly — raids, sweeps, sudden crackdowns — the reaction is fear and resistance, even among people who accept the law itself.

    The disturbance comes from rate change, not legality.

    Technology and AI

    • Gradual capability improvements are absorbed without panic.
    • Sudden leaps — systems doing in days what humans expect to take years — trigger unease, even when no explicit harm occurs.

    The system hasn’t become immoral.
    It has become temporally discontinuous with human expectations.

    Physical Space and Machines

    • Robots that move at consistent, human-scaled tempos feel safe.
    • Robots that jerk, hesitate unpredictably, or suddenly accelerate feel dangerous or uncanny.

    Not because of intelligence — but because acceleration breaks continuity.

    Humans Instinctively Know Physics

    Newton’s laws describe physical systems, but they also reveal something about perception.

    Force is only detectable through acceleration.
    Humans respond to the world the same way.

    When velocity is constant, we relax.
    When velocity changes, we pay attention.
    When acceleration exceeds our ability to predict outcomes, we experience danger.

    This is not emotional.
    It’s structural.

    It’s how biological systems maintain orientation in time.

    Why This Matters

    Acceleration is not inherently bad.

    • Emergency response requires it.
    • Innovation sometimes depends on it.
    • Stalled systems occasionally need a jolt.

    But unacknowledged acceleration (change without signaling), without ramp-up, or without context – is what breaks trust.

    Humans don’t fear motion. They fear unexplained force.

    Call to Action

    We need a new, additional dimension of thinking objectively about problems and I believe that dimension needs to be “velocity and acceleration”.

    By naming acceleration as a distinct dimension of analysis, we gain a way to examine instability before it is moralized, politicized, or personalized.

    When we call out the velocity, it makes implicit emotions explicit and gives us a lever for change.

    Instead of just saying, “Stop doing that, it’s wrong,” we can be more specific and say, “You’re moving faster than the rest of the group. The rate of change is too great. In order for me to feel safe, I need you to slow down.”

    Some people already do this. Others can learn to use the tool.

  • The Room of Requirement: Why Hidden Spaces Appear in Stories, Organizations, and Real Life

    The Room of Requirement: Why Hidden Spaces Appear in Stories, Organizations, and Real Life

    In Harry Potter, the Room of Requirement is one of the most powerful ideas in the entire series – not because it’s magical, but because it’s true.

    The room appears only when it’s genuinely needed.
    It takes the shape of whatever solves the immediate problem.
    And it exists outside official authority, yet quietly makes survival possible.

    It doesn’t show up because the school planned well.
    It shows up because the institution failed to provide something essential.

    That pattern turns out to be everywhere – in movies, in organizations, and in real life.

    The Room of Requirement in Harry Potter

    At Hogwarts, students don’t use the Room of Requirement because they’re rebellious or sneaky.

    They use it because:

    • the curriculum doesn’t prepare them for real danger
    • authority figures are constrained, compromised, or absent
    • open discussion would expose vulnerability or incompetence

    Dumbledore doesn’t officially sanction it.
    Umbridge would destroy it instantly.
    Yet without it, the students would be helpless.

    The Room exists because truth, practice, and preparation needed somewhere to live.

    The Rooms in The Goonies

    In The Goonies, the kids don’t operate from city hall, the police station, or their parents’ living rooms.

    They operate from:

    • basements
    • tunnels
    • hidden pirate ships
    • off-the-map spaces adults don’t control

    Why?

    Because the official system has already decided:

    • their homes are expendable
    • their voices don’t matter
    • efficiency matters more than people

    So they build their own operating space – informal, risky, collaborative – and save what the system was willing to lose.

    That’s not childish fantasy.
    That’s an accurate model of how under-supported groups survive.

    Rooms of Requirement in real organizations

    This isn’t just storytelling. It happens in real companies all the time.

    First example: inventing leadership when it isn’t allowed

    At one agency I worked at, there was a clear need for a function the company didn’t want to formally support. The work still needed to happen — so a small group of us created a private space where we could:

    • talk honestly about how to run projects
    • share what actually worked with developers
    • cross-pollinate ideas without fear

    It worked extremely well.

    Morale improved.
    Outcomes improved.
    Leadership emerged naturally.

    Eventually, the space grew visible enough that someone tried to expose it to management. Leadership shut it down.

    Not because it was wrong – but because it proved something uncomfortable:

    The organization worked better when truth had a place to exist.

    The Room of Requirement returns

    Years later, the same pattern reappeared.

    Public discourse about how to do work was constrained – not maliciously, but structurally. Visibility was risky. Admitting uncertainty was punished. Narrative control mattered more than shared understanding.

    So intelligence routed itself sideways again.

    A private Slack channel emerged – half jokingly called a “Room of Requirement.” Inside it:

    • communication was fluid
    • people shared real practices
    • leadership happened without titles
    • morale went up

    No rebellion.
    No gossip.
    Just people solving the problems the formal system couldn’t acknowledge.

    And once again, it worked.

    The uncomfortable lesson across all of this

    Rooms of Requirement don’t appear because people want to hide.

    They appear because:

    • a critical function exists
    • the system won’t name it
    • the work still has to happen

    When that gap opens, one of two things occurs:

    • reality degrades openly
    • or intelligence moves underground

    Most organizations choose the second – at least for a while.

    What Rooms of Requirement are actually good for

    Used well, these spaces can:

    • preserve morale in rigid systems
    • allow learning without exposure
    • prototype better operating models
    • help people lead before they’re allowed to

    They are:

    • relief valves, not replacements
    • labs, not final answers
    • bridges, not destinations

    They buy time.
    They keep things alive.
    They prevent collapse while everyone pretends nothing is wrong.

    A practical recommendation

    Rooms of Requirement are most useful when they are:

    • small
    • voluntary
    • clearly informal
    • focused on learning, not power
    • treated as temporary scaffolding

    They should help people think, connect, and survive – not carry the entire structure on their backs.

    When they become load-bearing, something else needs to change.

    Closing thought

    Every time a Room of Requirement appears — in fiction or in life — it’s telling you the same thing:

    There is a truth this system cannot yet afford to see.

    The room isn’t the problem.
    The room is the signal.

    And learning how to read that signal – without confusing it for the solution – might be one of the most important leadership skills there is.

  • Authority, Winning, and the Cost of Staying Adjacent

    This morning clarified something I’ve been circling for years but never named plainly: I have optimized for system impact, not personal authority.

    I’m very good at building, fixing, and stabilizing systems. I improve organizations, help leaders think more clearly, and quietly make things work. But I’ve done this while standing adjacent to power instead of occupying it:

    • Advisor instead of owner
    • Architect instead of authority
    • Reliable #2 energy instead of explicit responsibility with upside

    That pattern used to make sense, but it is no longer congruent with who I am.

    Earlier in life, staying adjacent gave me flexibility, safety, and moral insulation. I could contribute without exposure. I could help without risking visible failure. I could preserve an identity built around service, intelligence, and restraint. It worked—until it didn’t.

    What’s changed is not my capacity, but the gap between who I am and how I’m positioned. That gap is now emotionally expensive. It shows up as frustration, quiet resentment, and the sense that I’m under-leveraged. At this stage, capability without outcomes doesn’t read as humility anymore—it reads as incongruence.

    The hardest realization is that not winning has been an emotional strategy. Losing—or at least not fully claiming victory—kept me morally clean and relationally safe. But the cost was real: borrowed authority, capped upside, and leadership that I donate instead of own.

    What once looked virtuous is now avoidance wearing a service costume.

    Here’s the reframe that landed hardest for me: for someone like me, winning is load-bearing.

    When capable people refuse authority, less capable systems stay in charge and entropy increases. Responsibility without power becomes the norm.

    Winning, rightly defined, isn’t dominance or ego—it’s stewardship. It’s aligning authority with responsibility so systems actually stabilize (instead of limping along).

    This internal shift then let me connect directly to recent geographic and social friction. A regional analysis made it obvious to me that I’m trying to regulate myself in environments that don’t reward execution or ownership. La Crosse and similar Driftless towns prioritize values, relationships, and moral signaling over outcomes. That’s not wrong—but it’s costly for someone wired to build, ship, and take responsibility.

    Madison and Rochester stand out not because they’re glamorous, but because there competence carries weight. Execution is expected. Outcomes matter. Accountability is normal. The insight isn’t “I need to move tomorrow,” but that I need periodic immersion in consequence-dense environments to recalibrate my nervous system and expectations. Without that, resentment builds and clarity erodes.

    The through-line is uncomfortable but clean: this isn’t a motivation problem. It’s an identity lag. I was still operating with rules designed for an earlier season—rules that prioritize safety and flexibility—while my calling now requires ownership, visibility, and measurable outcomes.

    At this point, refusing to win isn’t neutral. It quietly undermines authority, credibility, and self-trust. Winning isn’t about ego anymore. It’s about accepting stewardship of the systems I’m already capable of carrying.

  • Formation Over Validation: Living Forward Without Waiting

    I’m starting to see the shape of the season I’m in more clearly now. It’s quieter than I expected, slower than I wanted, and far more formative than I realized at the time.

    A lot of what I’ve been wrestling with isn’t about failure, or even missed opportunities. It’s about tempo, identity, and ownership.

    I’ve been carrying an unspoken fear that life is happening somewhere else—that the real future is in California, in offices full of important people, in rooms where decisions get made. That if I’m not physically there, I’m slowly becoming irrelevant. That one day I’ll wake up older and realize I waited too long to matter.

    But when I look honestly, that fear isn’t rooted in truth. It’s rooted in a narrow story of what “serious work” is supposed to look like.

    I didn’t get trapped near my kids. I chose to stay present. And the resentment I sometimes feel isn’t because the choice was wrong—it’s because I don’t always re-own it consciously. When I forget that I chose this path because it aligns with my values, my mind rewrites the story into one where something was taken from me. That’s the seed of bitterness, and I don’t want it growing.

    At the same time, I can see that I’ve been conflating visibility with location, and approval with progress. I’ve been too focused on where my body isn’t, instead of where my thinking could be.

    What’s becoming clearer is that my real work right now is formation, not validation.

    I’m learning that moving fast socially or emotionally often backfires—not because I’m dangerous or wrong, but because humans process safety and effort on delayed timelines. Politeness doesn’t mean alignment. Warmth doesn’t mean consent. And by the time discomfort surfaces, it’s already too late to correct. That doesn’t make me defective; it means the lever is earlier to see, not later to explain.

    This applies far beyond dating. It applies to life.

    I’m also seeing how much unused energy I’ve been carrying—how excess capacity with no clear direction turns into rumination, longing, scrolling, and obsession. When I’m physically exhausted, mentally engaged, and creatively focused, those patterns quiet down. Direction dissolves obsession. Creation beats distraction.

    Masculinity, for me, isn’t about force or dominance. It’s about restraint, discipline, and dignity under stress. About not outsourcing identity to approval. About metabolizing anger into strength instead of letting it rot into resentment. Sometimes withdrawal isn’t avoidance—it’s wisdom.

    There’s something deeply grounding about realizing that this season isn’t a punishment or a stall. It’s groundwork.

    Jesus didn’t chase acceptance. He moved with clarity, withdrew without bitterness, and measured success by obedience, not outcome. “Shake the dust off” isn’t about contempt—it’s about refusing to carry residue forward.

    I can see now that framing life as “later” is a trap. If I tell myself my real life starts after the kids are grown, or after some imagined permission is granted, I’m training myself to wait. And waiting corrodes the nervous system. Parallel advancement—not deferred living—is the way through.

    I don’t need to be everywhere. I need to be visible where it counts. Ideas compound. Synthesis matures. Presence matters more than proximity.

    This season is quiet. Restrained. Intentional.

    It isn’t failure.

    It’s formation.

  • I’m Ok, It’s Alright

    Alright, I’m going to make up a song now from scratch. I know the first couple chords to it. It’s A minor, C, G, and I don’t know what the lyrics are, but I’ll figure it out.

    I’m Ok, It’s Alright


    Am C G
    G Am C
    Well I don’t know where I’ve been going or where I’m going to
    G
    But I’ve arrived, I’ve arrived
    Am C
    And I don’t know where this old road goes, but I know how this old plant grows
    G
    I survived, I survived
    Am C
    And winters coming soon, but it’s still fall in this old room
    G
    And I’m alive, I’m alive
    Am C
    And spring will come around and we’ll plant ourselves in the ground
    G
    And then we’ll thrive, and then we’ll thrive

                  D                         C          G

    There’ll be summer in these woods again
    D C G
    It’ll be summer in these woods again

       Am               C                G           D

    But right now it’s quiet in the morning
    Am C G
    And I drink my coffee with a little bit of cream and a touch of sugar
    Am C G D
    That’s okay, that’s okay. It’s just fine, I’m alright.
    Am C G D G
    It’s okay, it’s just fine, I’m alright. I’m okay, I’m okay.
    G C D G
    I’m okay, I’m okay. I’m okay, I’m okay.

                  D                         C          G

    There’ll be summer in these woods again
    D C G
    It’ll be summer in these woods again

  • Every Hour

    All right, this is a song I’m working on. It has no name, but anyway, let’s get into it. Okay, here we go.

    Every Hour

    If I were a flower, I’d bloom for you. All right, still practicing, just bear with me here. If I were a flower, I’d bloom for you.

    Wow, okay, let’s try this one more time. If I were a flower, I’d bloom for you. Every hour, I’d bloom for you.

    If I were a blue jay, I’d fly for you. This song is called Every Hour. If I were a flower, I’d bloom for you.

    If I were a flower, I’d bloom for you. Every hour, I’d bloom for you. If I were a blue jay, I’d fly for you.

    All right, one more time. If I were a flower, I’d bloom for you. Every hour, I’d bloom for you.

    If I were a blue jay, I’d fly for you. Every hour, I’d fly for you. Okay, I made it through the first verse.

    If I were a tree, I’d grow for you. Gosh. Every hour, I’d grow for you.

    Grow for you. Every hour. Okay, wow, all right.

    If I were a table, I’d set myself for you. I’d put all the plates out and all the food. If I were a flower, I’d bloom for you.

    Every day, I’d bloom for you. If I were a kayak, I’d swim for you. Every day, I’d swim for you.

    If I were a fish, I’d swim for you. Every day, I’d swim for you. If I were a fish, I’d swim for you.