It's amazing that we can learn anything today.

As a builder, chatting with AI has become a daily check-in. I can learn anything, visualize ideas, and offload tasks. The shift has been massive.

But I'm grateful my computer science journey started before AI got this agentic. Back in university, I had to dig through Stack Overflow, Reddit, Google, or even mail someone. That friction pushed me to actually understand the infrastructure and what's happening underneath the code, not just the code itself.

We Can Build Anything Now

That's the message I keep coming back to: we can learn anything, and as builders, we can build anything.

So I'm learning something new: knowing when to stop.

Stopping doesn't mean giving up on goals. Stopping means rethinking the way we think. It means we don't have to build everything just because we can.

The Real Question for Builders

In software engineering, stopping looks like this:

I want to build something. Then I find out the same problem is solved by a $15/month subscription.

Now the real questions kick in:

• Is it necessary to build this myself?
• Yes, it's cheaper to build, but is it efficient?
• Will the maintenance burden outweigh the subscription cost?

If the answer points to "just pay for the tool," that's the right call. Building something custom isn't always a win. Sometimes it's just ego dressed up as engineering.

The Bigger Picture

This goes beyond software. In this agentic world where we can achieve almost anything, knowing when to stop is its own skill.

Build less. Think more. Choose what's actually worth your time.