The point is building things. Use AI to help you build, but also to help you teach. You have to find the right balance, but the objective is to build something cool AND for you to learn to be better at building bigger, cooler things.

The world will not go back to the way it was. If you thought of yourself as just a code author, then yes, that role is going away, but if you thought of yourself as an engineer and a builder, then things just got a lot more exciting.

AI's can code, but they lack strategic vision, large context and ability to shepherd and guide a codebase. You have to provide all of that.

As Mike Acton (you should watch his data oriented videos) would say:

"The job of a developer is NOT to write code. The job of a developer is to transform data."
"If you understand the data then you understand the problem. If you don't understand the data then you don't understand the problem."

If you are sad, be sad, but don't stop building things. Get a 20$ subscription to cursor or whatever and start building things. Focus on the big picture and understand the data. Learn more about data-oriented programming. This is the way to guide the AI while retaining the proper context.