Why can I fix batteries but not predict how they fail?

You can open a battery, diagnose a fault, replace a cell, close it up. That skill is real and it took work. Don't dismiss it. But degradation and heat are different animals. They don't happen at a moment you can watch. They happen slowly, inside the cell, or they happen fast and invisibly as heat moves through a pack you can't see into. No amount of bench time teaches you to read something you can't observe directly. So stop waiting for more hands-on hours to close this gap. They won't. What closes it is learning to treat the data — voltage sag, temperature spread, charge cycles — as the battery speaking to you in the only language it has. That is a skill you can build on purpose, starting now.

◆ How this problem reads on the two dials

GuidanceKnowledge

Coaching

More to learn

1:1 with AureliusWith others (a Pod)

Mostly you & the coach

A little with peers

There's a real conceptual gap to teach first (how degradation and thermal behavior actually show up in data), then the habit of reading it has to be coached into practice.

How the two dials adapt to you →

What’s really going on

Your hands have outrun your eyes. Degradation and heat don't announce themselves at the bench — they leave traces in data, across time, that you haven't yet learned to read. The fix isn't more repair work. Choose to study the traces: voltage curves, temperature logs, cycle history. Build the model deliberately, then test it on real packs.

🔒 What you’ll build togetherUnlock by starting

A movePick one battery you've already serviced. Pull its full data log, not just the fault code, and read it start to finish before touching the hardware again.

A moveFor every pack you work on this month, write down what the temperature curve was doing in the ten minutes before any anomaly. Look for the pattern, not the event.

A moveChoose three degradation signatures — capacity fade, internal resistance rise, voltage recovery lag — and learn to name which one you're looking at before you guess a cause.

A moveStop diagnosing from symptoms alone. Build a simple rule for yourself: no conclusion until you've checked both the thermal history and the cycle history.

A moveWhen a pack confuses you, don't move to the next job. Sit with the confusion and write down exactly what you don't understand yet. That list is your real curriculum.

What changes unlock by starting

You can look at a voltage and temperature log and state, in plain terms, what the battery has been through.
You stop treating degradation as random bad luck and start treating it as a readable process with causes.
You catch thermal problems earlier, from patterns, instead of only after a failure forces your hand.
You build a working mental model you can apply to packs you've never seen before, not just the ones you've already fixed.

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.