Original post by Just JoshHey, sorry for not replying before, I don't really use this website anymore. You will most likely be fine, really. I'm just finishing second year now and the maths intensive modules that i've done (Advanced Algorithms and 3D Computer Graphics) are only for the vanilla computer science course. You will do something else, I think business law or financial accounting or something. If i'm honest, if I had my time again, I would have gone for the CIT course. Mostly because people tend to get better grades in them than in the CS specific modules, and also, the CS specific modules really suck. (Advanced Algorithms, 3D graphics, Computer Logic). I guess first year CS only students do a module in Android Development, which is also what we do for second year software engineering project. So those who did CS have a strong advantage with that. But apart from that, I can't think of any other issues and android is fairly easy to pick up.
As for what's employable, it's you that makes you employable and how you perform at the interview. I swear half the interviews i've been to, they don't even know what degree i'm doing, it was just a way of me getting filtered to get to the interview. I'm doing a software development placement at IBM, starting in a month or so. I'm pure CS, but many of the other people at the assessment centre were doing really bizarre things like operational management or media computing and even stuff not related to computing at all, all going for software development. I've also been to many other assessment centres, which I didn't get the jobs, where people not doing pure CS got the jobs and I didn't. So I really don't think it makes a difference. People in my year on both sides are getting good placements.
If you want to get ahead before you start (which there's no real reason to, if i'm honest), I would buy a book called "Head First Java". It's a simple introduction to Object Oriented programming, which can be a bit overwhelming when you first start. There are many guides out there who teach Java as a language but expect people to already know how to program. This is different as it's for complete beginners. It was a life saver for me (i did computing to AS level but got a D and dropped it), so had barely programmed before, and definitely not in object oriented. But apart from that, first semester first year modules in first year are more than manageable.
My main advice would be just to attend, something I should really have done more. It really does help, especially in first year.
There are 4 main ways of assessment I suppose. Written exams, practical exams, written coursework and practical coursework. In the first year programming, the exam is fairly easy, as you don't really have to think for yourself. It's more a case of "define this variable" "write a method that does this" "inherit the methods from this class". Whereas after first semester, you have to think for yourself. My experience here is that there is a lack of balance between modules - some modules are easy, some are ridiculously hard. Some have lecturers who give 80+ percent for courseworks. Other lecturers you have to battle to get 50 out of. I guess that's just uni education for you - every lecturer writes their own course, their own exams, and mark it in their own ways. As for how hard practical exams are, you should be fine. The one I did today (3D graphics) was probably my hardest practical exam so far - but that's CS only. You'll be prepared well for the practical exams.
There's loads of support for first years struggling with programming. When I was in first year, they ran extra classes specifically for people who were struggling with the programming. The lecturer I have had for that module was awesome, but he's now left. I think he's now replaced by Helen, who is also really good.
Feel free to mail me if you want to know anything more,
All the best, hope you make the grades.