What is a Product?

Product
is another word
for “outcome.”

The product of
4 and 4
is 16.

When a designer designs something
the product
from the designer’s perspective
is the outcome
of their design.

When someone buys something
the product
from their perspective
is the outcome
of their purchase.

The product
people are buying
are not always
the product
we’ve designed.

My Fault

There are times
when it seems so clear
that the fault
is ours.

I raised my child poorly.

I lead my company to bankruptcy.

I failed to support my spouse.

This often happens
when there are two things
equally clear
if you’re willing
to see them.

First,
is that you’re someone
who is willing
to take
responsibility.

Second,
is that you have
emotional needs.

Perhaps the need
to be forgiven.

Upon seeing these two things
clearly,
may you learn the choice
to take responsibility
for fulfilling
your own emotional needs
as well as worrying
about the emotional needs
of others.

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.

Perspective, Where Art Thou?

We often assume
we can take
someone’s perspective.

Until we realize
that the perspective we took
wasn’t theirs
or that it wasn’t the one
we needed.

To make up for this
we sometimes think we can get
their perspective
by asking.

Until we realize
that people aren’t always aware
of the whereabouts
of their own perspectives.

At which point
we realize
that the only way forward
is to discover
their perspective
together
until
we realize empathy.