You are thinking in the right direction; a lot of experienced developers are also thinking the same way.
The goal is not to become specifically a buggy-whip manufacturer or a specialist mill-worker; the goal is to have enough mental faculties and critical-thinking skills to adapt to any situation and be able to use any tool at hand to achieve your own goals and that of the employer.
Being a software architect means you actually need to gain depth in certain aspects of software development and computer science/engineering, and understand how an LLM works, what its weak points are, and to stop it from making mistakes. The point of double-majors is to expand your breath, not your depth.
You need both, depth and breadth, and thankfully LLM tools can help you in gaining both a lot quicker.
For some reason, I had the opposite effect due to AI - previously I enjoyed building things but hated the actual writing of code part. Now that AI can do that for me, I can keep my focus on the more important problems, and let AI deal with the lower-level stuff.
Your focus should be on gaining enough competence to solve hard problems by yourself, and in teams; and to learn how to learn. I would not worry too much about semantics of job roles - roles might change, but work (whatever that might be) will always be there, and you need to know how to do difficult types of work well.
The goal is not to become specifically a buggy-whip manufacturer or a specialist mill-worker; the goal is to have enough mental faculties and critical-thinking skills to adapt to any situation and be able to use any tool at hand to achieve your own goals and that of the employer.
Being a software architect means you actually need to gain depth in certain aspects of software development and computer science/engineering, and understand how an LLM works, what its weak points are, and to stop it from making mistakes. The point of double-majors is to expand your breath, not your depth.
You need both, depth and breadth, and thankfully LLM tools can help you in gaining both a lot quicker.
For some reason, I had the opposite effect due to AI - previously I enjoyed building things but hated the actual writing of code part. Now that AI can do that for me, I can keep my focus on the more important problems, and let AI deal with the lower-level stuff.
Your focus should be on gaining enough competence to solve hard problems by yourself, and in teams; and to learn how to learn. I would not worry too much about semantics of job roles - roles might change, but work (whatever that might be) will always be there, and you need to know how to do difficult types of work well.