Thanks for your in-depth response. > Why are you interested in CS in the first place? Computer _Science_ will not be affected by LLMs and other technologies at

Thanks for your in-depth response. > Why are you interested in CS in the first place? Computer _Science_ will not be affected by LLMs and other technologies at all. I haven't really had a chance to try out pure CS. In my own time I work on practical applications (though a current project involves lots of boolean algebra), and the curriculum at school is mostly things I already know (Sorting algorithms, and we'll do big-O at some point). The practical part of the school curriculum is heavily-OOP C#. > Now, if you want to go to CS just to get a programming job at some company and you are doing this for money, I would indeed ask you to reevaluate. If you like programming as a hobby, a good way to kill the passion is to turn it into a boring 9/5 job. Physics and engineering may use programming as a tool and that may be more interesting to you? I'm certainly not doing it for the money - I genuinely love it - but when I'm a 17 year old making pragmatic decisions about my future, "Can I get a job" is a pretty important one. I hope that programming as a job doesn't kill my passion, but that's certainly a concern. How frequent is that? I'd be interested in programming within other industries, but I'm not sure on a path to doing that. I've had a lot of comments suggesting I take physics/engineering courses at uni in addition, but I'm not really sure how much of an option that is in the UK. I'll ask. > That said, LLMs will not make a dent anytime soon. Yes they will plagiarize code and spit it out in a way that's similar to what you have requested – and for this very reason, have been banned at my Fortune company (Intellectual property is tricky). But they have no reasoning capabilities, there's still demand for solving actual problems. These days, writing code is a fraction of what I do, a lot of work goes into syncing with other teams and figuring out _what to write_. When I actually sit down to write code, that usually takes just a few days. That pales in comparison to all the architecture and coordination work that had to happen to reach that point. Yeah, I did a week's work experience with Microsoft research about a year ago. I definitely got that impression - I, the work experience kid with no internal access, given some small projects they hadn't had time to do, programmed far more than the actual programmers on the team because I was in less meetings. I enjoyed the meetings and thinking about how to make the tool practically useful, but I'm not sure if that would continue into a decades-long career. I'll probably be doing it again, so I'll have another opportunity to consider that. Part of my motivation behind going to uni is that I've had a pretty bad time at school due to bullies, violence, and a serious, ongoing concussion from an attack on me. Going to university and finding a good tech job appeals to me because it would (in theory) mean being surrounded by intelligent, motivated, decent people.