Debugging

As programmers,
it’s easy
to conflate debugging
with problem solving.

Yes,
when debugging is complete
the problem
is solved.

But while debugging,
we spend most of our time
trying to see
the code
alive.

The code
that describes a living system.
One comprised
of parts,
their relationships,
and their impact
on one another.

Seeing the code alive
is akin to comprehending
what is really going on.

Once we comprehend
what is going on
problem solving
is often
straightforward.

We often forget to do the same
when not programming.

Especially
with people.

Instead,
we jump
to problem solving.

To Reflect

What does it mean
to reflect?

Stand in front of a mirror.

The mirror
will reflect.

By mirror,
I mean a relationship
from which we can receive the choice
to see ourselves
from an interfacing
perspective.

By an interfacing perspective,
I mean a perspective
from which we can receive the choice
to see ourselves
as an “other”
with which we can empathize
without hyper-empathizing.

Go ahead.

Look into the mirror
and see yourself as an “other”
with which you can empathize
without hyper-empathizing.

Now,
by look,
I mean receive the choice
to recognize,
acknowledge,
and appreciate
parts of your “self”
by recognizing,
acknowledging,
and appreciating
parts of
the “other.”

Parts you forgot
or did not know
to recognize,
acknowledge,
and appreciate.

I mean give these parts
the choice
to feel seen.

The choice
to matter.

And by giving this choice,
may you realize
that this
is a loop,
where giving
does not constitute losing,
and receiving
is not predicated on lacking.

A loop,
where fear and shame
can make way
for flow.

Whether we reflect
through journaling,
through coaching,
or otherwise…

May this be a guide.