Chasing the Southern Cross: Discover — Using "Energy Archaeology" to Find Your Inner Truth

This is the second article in the series on finding the Southern Cross, and the first D of the 4D framework: Discover.

During that period, I clocked in on time every day and delivered work step by step, but I always felt like a quietly running machine. I did a lot of work, yet I couldn't say what I actually enjoyed doing. Let alone any "vision" — the word even felt hollow to me.

Then one night, while fixing bugs for a new hire and ordering takeout, a message from a friend hit me: "You're this busy over it — does the company even know?"

I replied: "They don't, but I do."

It turned out that some things, even without KPIs or rewards, made me unconsciously willing to spend more time on them.

Those things that no one evaluates, no one likes, and others even consider not worth the effort — they are the signals most worth my own attention.

Later, I gave it a name: energy traces.

Many people look for a career direction by first asking "What am I good at?" "What does the market need?" "Which position should I choose?"

But I discovered that a true sense of direction is often not calculated, but rather unearthed from the energy traces we leave behind.

Not an interest list, but an "energy map"

Traditional methods of finding direction often make people more confused, because we are too prone to making things look good on paper:

Interest lists all look passionate, MBTI results feel like fortune-telling, and even ChatGPT can list a bunch of career suggestions. But why do we still feel empty after trying them?

Because these methods bypass a key question: Where exactly are the moments when a person truly experienced a "high-energy state"?

I later switched to a different approach: doing an "energy retrospective" every quarter.

Looking back over the past three months, were there any things that made me clearly feel time flying by, still had energy after finishing, and even wanted to review and do them again?

For example:

After explaining Code Review logic to a junior engineer, I found that I explained it even more smoothly than I wrote it.
Refactoring a piece of legacy code late at night, with no one pushing me, yet I couldn't put it down.
Turning a technical solution into an FAQ document and sending it out, only to find that others' understanding efficiency doubled.

These emotional high points in the moment are our energy clues — a compass more honest than any interest list.

[Method] Use the Energy Quadrant to locate your inner true preferences

This method is simple. I call it:

"Energy Trace Quadrant":

Plot the projects, tasks, or moments you've been involved in over the past 3 months on the following coordinate system:

Horizontal axis: Whether it was externally recognized (KPI, reported, exposed)
Vertical axis: Whether you would be willing to experience it again (after finishing, do you feel drained, or still energized?)

Then you'll find that some things fall in the upper left corner — no one knows about them, but you especially want to do them again.

Those might be the true fragments of our Southern Cross.

There's another energy signal called "anger"

Don't get me wrong — I'm not talking about losing your temper, but about examining in which situations we can't help but feel angry or complain.

I've found that the most valuable beliefs of technical people are often hidden in anger.

For example: "Why does no one ever write the interface documentation?" "Why do users have to click three times to submit?" "Why does the boss always talk about process standards, but no one actually debugs them?"

Behind these complaints is actually an inner desire for clarity, smoothness, and honest feedback — that's what we truly care about.

I once did an exercise: I wrote down all the "so annoying," "here we go again," and "what the hell" things I said over a week, then analyzed the standards behind each one. In the end, I arrived at a statement of my value preference:

What I want to build is a system that users don't need to think about, not a high-complexity product that engineers use to show off.

That sentence became the anchor for many of my later technical decisions.

[Practice] Three steps to build an energy archaeology notebook

If you want to try this method, I recommend starting with this small exercise:

Record the most recent piece of work you "couldn't stop doing"

It doesn't have to be a big project — it could even be polishing a document, an internal discussion, or refactoring a piece of code.
Recall how you felt after finishing: satisfaction? exhaustion? or wanting to do it again?

The point is not how well you did it, but whether you would be willing to do it again.
Write down the part of it that felt most "alive"

Was it making independent decisions? Conveying clarity? Helping others? Controlling boundaries? Pushing through chaos? What we want to capture is the moment when your emotions were most active.

After completing these three steps, go back and organize the most frequent "energy peaks" and "energy funnels" over the past six months, and you will gradually see your preference map.

This is "energy archaeology."

Those things without KPIs are your real KPIs

We spend too much time aligning OKRs, filling in progress sheets, and doing Sprint Reviews, but rarely stop to ask:

In places where no one is scoring, where am I willing to put my effort?

Technical people easily fall into a trap: only when results are produced, seen by leaders, and written into weekly reports is it worth affirming.

But much of the sense of direction that truly grows comes from those unobserved nights, from a spontaneous process of writing documentation, from seemingly useless visions.

Our Southern Cross is often not found, but quietly walked out by ourselves, step by step.

True high-energy moments often fit the CAP theorem:

Consistency (consistent with your values)
Availability (always ready to invest)
Partition tolerance (not disturbed by external evaluation)

Ending: Where to next?

You may not yet know where this "star" will take you, but you can start now, continuously calibrating it through action.

And next, we will continue to talk about: how to turn these energy clues into a direction statement that can stand on its own.

Because "I like it" is not enough — you need to find the reason you are willing to carry even if you fail.

See you in the next article: "Rejecting Correct Nonsense: How to Write a Flesh-and-Blood Engineer's Manifesto"