This discussion is now closed.
Spoiler
Spoiler
•
Programming in about 8 different languages
•
Cisco IOS (nobody I know from my old CompSci course has even seen that)
•
Microsoft SQL Server, MySQL Server (how they work, how to maintain them and the differences in the SQL syntax for each)
•
Thinking about the UX from the user's perspective
•
Knowledge of computer architecture
•
How to construct and maintain a secure networking infrastructure, albeit on a small and controlled scale
•
In depth knowledge of computer security and how to defend against real world threats
•
Digital forensics and how to conduct a forensically sound investigation of a suspect system
•
In-depth knowledge of computer networking and the associated protocols
•
Software development methodologies (I don't want to be a software engineer, but the skills and methods are transferable and generic)
•
The ability to write complex technical reports to a very high standard
•
How to conduct academically sound research in a constructive and organised fashion
•
Death by Java
•
A load of poorly explained, high level theory regarding data structures which most working programmers don't care about... because .Net and Java will do it all for you
•
Functional complexity - you can get the same information, explained more clearly, with 5 minutes of basic Googling
•
The basics of computer architecture
•
Formal Logic - I'm not joking when the lecturer teaching it was the only person in the department who understood it, most of the academic tutors were stabbing in the dark trying desperately to figure it out let alone us. Poor choice IMO and should have been replaced with something else
•
Everything explained through either code or maths - there was very little hands on learning and a chance to try these things out, and the assessed labs consisted of "Use Java to implement the theory you've been taught in lectures". Uninspiring and dull.
Spoiler
•
Programming in about 8 different languages
•
Cisco IOS (nobody I know from my old CompSci course has even seen that)
•
Microsoft SQL Server, MySQL Server (how they work, how to maintain them and the differences in the SQL syntax for each)
•
Thinking about the UX from the user's perspective
•
Knowledge of computer architecture
•
How to construct and maintain a secure networking infrastructure, albeit on a small and controlled scale
•
In depth knowledge of computer security and how to defend against real world threats
•
Digital forensics and how to conduct a forensically sound investigation of a suspect system
•
In-depth knowledge of computer networking and the associated protocols
•
Software development methodologies (I don't want to be a software engineer, but the skills and methods are transferable and generic)
•
The ability to write complex technical reports to a very high standard
•
How to conduct academically sound research in a constructive and organised fashion
•
Death by Java
•
A load of poorly explained, high level theory regarding data structures which most working programmers don't care about... because .Net and Java will do it all for you
•
Functional complexity - you can get the same information, explained more clearly, with 5 minutes of basic Googling
•
The basics of computer architecture
•
Formal Logic - I'm not joking when the lecturer teaching it was the only person in the department who understood it, most of the academic tutors were stabbing in the dark trying desperately to figure it out let alone us. Poor choice IMO and should have been replaced with something else
•
Everything explained through either code or maths - there was very little hands on learning and a chance to try these things out, and the assessed labs consisted of "Use Java to implement the theory you've been taught in lectures". Uninspiring and dull.
Spoiler
•
Programming in about 8 different languages
•
Cisco IOS (nobody I know from my old CompSci course has even seen that)
•
Microsoft SQL Server, MySQL Server (how they work, how to maintain them and the differences in the SQL syntax for each)
•
Thinking about the UX from the user's perspective
•
Knowledge of computer architecture
•
How to construct and maintain a secure networking infrastructure, albeit on a small and controlled scale
•
In depth knowledge of computer security and how to defend against real world threats
•
Digital forensics and how to conduct a forensically sound investigation of a suspect system
•
In-depth knowledge of computer networking and the associated protocols
•
Software development methodologies (I don't want to be a software engineer, but the skills and methods are transferable and generic)
•
The ability to write complex technical reports to a very high standard
•
How to conduct academically sound research in a constructive and organised fashion
•
Death by Java
•
A load of poorly explained, high level theory regarding data structures which most working programmers don't care about... because .Net and Java will do it all for you
•
Functional complexity - you can get the same information, explained more clearly, with 5 minutes of basic Googling
•
The basics of computer architecture
•
Formal Logic - I'm not joking when the lecturer teaching it was the only person in the department who understood it, most of the academic tutors were stabbing in the dark trying desperately to figure it out let alone us. Poor choice IMO and should have been replaced with something else
•
Everything explained through either code or maths - there was very little hands on learning and a chance to try these things out, and the assessed labs consisted of "Use Java to implement the theory you've been taught in lectures". Uninspiring and dull.
Spoiler