Change Is the Only Constant: Why I Stopped Reinventing the Wheel and Started Building With AI

This is a more personal post than usual. There is no code in it, just something I keep coming back to in my own work.

"AI will take your job"#

You have heard it many times by now: people who use AI will take the jobs of people who do not.

I am tired of the line, and I also think it is half right. Nobody can predict exactly who loses and who wins. But I do see one pattern clearly: the people who dig in and say "the old way is the real way" are having a harder time staying relevant than the people who experiment.

So here is the version I actually believe. If you do not want AI to take your job, give AI one job.

Not your whole workflow. One task. The caption you write every week, the monthly plan, the summary of a long document. Let a tool do the first pass, and you do the judging. You are still the one deciding what is good. You have simply stopped doing the part a machine can do in seconds.

Forget "from scratch"#

The mindset change that mattered most for me is this: ask "how can I build this?", not "how can I do this from scratch?"

Think about building a car. If you needed a wheel, would you say, "I will reinvent the wheel, and then build every other part myself"? Of course not. You would use parts that already exist and build on top of them. Nobody is impressed by a car with a hand-forged bolt.

Yet that is exactly how a lot of us work. We want to prove we can do everything from the ground up, and we call it craftsmanship.

I ran into this on my own project. When our AI costs ran out on a content calendar, my first instinct was to set up my own local language model. It is a clever idea, and it would have meant running and looking after a model on a machine that had to stay on all the time. The better answer was to build on what already existed: connect the app to Claude through MCP, and let the calendar do the saving while Claude did the thinking.

The same thing happened with trade show research. Writing and fixing my own scrapers was the "from scratch" route. Using a tool that could already search the web was the builder's route.

Change is the only constant#

If there is one thing I would put on the wall, it is this: change is the only constant.

It will keep happening in your life, in your career and in your field. You cannot avoid it. You can only decide how you meet it.

So I try to run every decision through one question: am I acknowledging the change, or am I fighting it? A new tool, a new way of working, a new kind of problem: each of them is usually pushing you toward growth, and most of them are good for you, even when they are uncomfortable.

If you are afraid of change, you will find it hard to grow. That is not an insult. It is simply how it works: you cannot get to somewhere new without leaving where you are.

Conflict is the sign#

There is one more part, and it is the part people like least.

Conflict is necessary. Conflict with yourself, and conflict with the people around you.

When you try a new way of working, part of you will argue for the old way. When a teammate sees it differently, you will disagree. That friction is uncomfortable, and it is also what growth feels like from the inside. A new idea has to push against an old one before it wins.

If you are never in conflict, with yourself or with your peers, it is worth asking whether you are trying anything new at all.

I do not mean fighting for the sake of it. I mean being willing to have the argument, rather than avoiding it to stay comfortable.

Where I come from#

I know this from my own path. I was hired as a graphic designer, and ended up building software and automations, because I kept asking why something was being done by hand. None of that was in the plan. It happened because I kept saying yes to change, and kept using whatever tool made the next step possible.

What to do this week#

1. Pick one task and give it to AI. Just one. Review its work and see what you learn.
2. Next time you start something from scratch, stop and ask: what already exists that I can build on?
3. Notice what you are avoiding because it is new. That is usually where the growth is.
4. Do not run from a disagreement that comes with a new idea. Have it.
5. Do it again next week. Change is a habit before it is a skill.

The point#

Nobody can promise you which jobs survive. But I would rather be the person who kept building, kept changing and kept arguing with myself, than the person who kept perfecting a method the world had moved on from.

Give AI one job. Build on what exists. Expect change, and be ready to disagree with yourself.