Is time to pivot

I know—it is really late to say this. The wave is already here.

1. The realization: It is time to pivot

I have been a software engineer for around 11 years, working with people across the globe at startups, small companies, and big tech companies.

That experience cannot be erased. What is done is done. But I no longer think this is the same path it used to be.

For some reason, I have been doubting myself a lot lately.

2. The evidence: Even with evidence, the future is scary

Even though I have evidence of what I can achieve, I still struggle to understand how I will add value once most software can be built by AI.

I know I can solve complex problems. I have evidence.

I know I can lead teams. I have evidence.

I know I can communicate effectively. I have evidence.

But I do not think these abilities will be useful in exactly the same way they were before. What I know for sure is that continuing down the same path is not the answer.

You can ignore reality if you really want to, but reality will not ignore you.

Software engineering as we know it is over.

3. The next steps

I have adapted to the market before, so I know I can confidently move into an AI-related role.

I remember being a backend engineer trying to center a div and thinking:

“Man, I suck at this. I am going to be a backend engineer for the rest of my life.”

Two years later, I was working as a lead frontend engineer.

I know I can adapt.

For now, I want to create a path forward for my career—even if that path is not completely clear yet—and then start building cool things.

So, the plan is:

1. Find good resources for creating a career path.
2. Create the first draft of that path.
3. Educate myself using reliable sources.
4. Revisit and refine the path.
5. Create projects and share them.
6. Find opportunities through networking.
7. Keep repeating the process until it leads to new professional adventures.

For now, writing this is enough.

Now comes the hard part.

Happy hacking!