My perspective weights towards industry, not academia. That is an important thing to acknowledge up front; note that almost everyone you talk to on a university

My perspective weights towards industry, not academia. That is an important thing to acknowledge up front; note that almost everyone you talk to on a university campus has the opposite perspective and many of them are unaware of it. It is far more important that you actually write code than the specifics of what you study, from the perspective of a career in industry. This attitude is very not shared by academia. I would bias towards a course of study which included the opportunity to work on longer-than-a-lab meaty projects. Some schools offer courses where the primary thing that you do is a single semester-long project on a team; that is a useful thing to have done. University is also a good time to low-consequence graze across a variety of fields to expose you to things you _could_ do in your career without necessarily needing to commit to them. One undergrad course on AI, for example, costs you ~2% of your units of study effort and, while it probably has negligible real-world utility, will give you a feel for whether it is an energizing topic for you. Does your school have a strong internship program? I would expose myself to opportunities to do an internship, particularly if it were an internship at a company with a strong engineering culture. Bonus points if it is one you'd consider working at after school