A delayed shipment isn't all that different from that check-engine light. A system can tell you that a shipment is late, but that's only the warning. The more important questions come next. Why is it late? Is it the carrier, an appointment, paperwork, the dock, or something else entirely?

And what happens next? A delay rarely stays contained to where it started. It can affect delivery promises, increase costs, interfere with other loads, and eventually reach the customer. The delay is what you can see. The harder part is understanding what caused it and what it might affect next.

That's something I saw much more clearly while working on TRUKR, Smartlinks' Transportation Management System. Smartlinks describes itself as an AI-enabled supply chain execution platform building toward a broader vision of an autonomous supply chain, where technology can recognize what's happening, understand its impact, and help people respond with less manual intervention.

The part I experienced was one piece of that larger vision, but the idea behind it was the same: Don't stop at the warning. Understand what's underneath it.

When I joined Smartlinks, I'd worked with GitHub and codebases before, but never anything at this scale. I was moving between multiple repositories, trying to understand code I hadn't written, and figuring out how different pieces connected. At first, the amount of information could be overwhelming.

My own warning light was pretty simple: I don't understand this. And Claude made it incredibly easy to make that warning disappear.

I could give it the problem, get an answer, make something work, and move on. But getting something to work and understanding why it works are two very different things. So I started using AI differently.

There were days when I'd spend almost the entire day going back and forth with Claude on a single concept. I'd ask question after question, explain what I thought was happening, let it challenge or correct my understanding, and then ask again.

Why is this function here? Where is this data coming from? How does this connect to another repository? Is my understanding of this right? What am I missing?

Sometimes one answer created three more questions. Sometimes I'd explain my understanding and Claude would show me exactly where I had gone wrong. Other times, the thing I thought I didn't understand wasn't actually the problem at all. There was another concept underneath it that I needed to understand first.

In a way, Claude became less like something I went to for answers and more like a consultant I could keep questioning. A consultant can simply hand you the recommendation, or they can walk you through how they reached it. One gives you an answer. The other leaves you with an ability.

I wanted the second. I wasn't trying to make my warning light disappear. I was trying to understand why it had turned on.