You seem to be getting a good technical education. As long as you know one computer language well it is not all that hard to pick up additional languages. Since you already know more than one language I wouldn't be overly concerned about not knowing lower level (closer to hardware) languages like C and Assembly.
Of course you need a strong grasp of software engineering fundamentals and this should include knowledge of: data structures, algorithms, compilers, operating systems, object oriented programming, AI techniques, architecture (both sw & hw) etc.
Beyond the standard curriculum here are a few things that I consider important:
Writing Skills: Clear and crisp writing whether it is technical doc or email.
Presentation Skills: Speak with clarity and poise. Be effective in using presentation technology. (A facility with powerpoint, in spite of all its limitations, can be invaluable. It can help organize and the audience understands the approach).
Group Interaction Skills: Can you work effectively in a group? What do you bring to the group? Possible choices: organization, communication, humor, fun...
Communicational Skills: How well can you interact with your peers, managers, subordindates, customers and others in the environment that you work in.
I believe that each of these soft skills can be acquired just as well as the technical knowledge that you are picking up. One of the good things about being a student (and as your post indicates) is that you know you have much to learn. If you can maintain this willingness to learn later in life you will have a successful career whatever you do.
I am currently trying out a tool from Lattix (http://www.lattix.com/) to create a Dependency Structure Matrix(DSM) to represent the software. Lattix LDM will generate the DSM from the output of "Doxygen" or from the output from "Understand for C++". It scales well - I had no trouble with applying it to a code base of 5m loc. I find DSM to be very useful in understanding the overall architecture.
Slashdot Mirror
You seem to be getting a good technical education. As long as you know one computer language well it is not all that hard to pick up additional languages. Since you already know more than one language I wouldn't be overly concerned about not knowing lower level (closer to hardware) languages like C and Assembly.
Of course you need a strong grasp of software engineering fundamentals and this should include knowledge of: data structures, algorithms, compilers, operating systems, object oriented programming, AI techniques, architecture (both sw & hw) etc.
Beyond the standard curriculum here are a few things that I consider important:
I believe that each of these soft skills can be acquired just as well as the technical knowledge that you are picking up. One of the good things about being a student (and as your post indicates) is that you know you have much to learn. If you can maintain this willingness to learn later in life you will have a successful career whatever you do.
I am currently trying out a tool from Lattix (http://www.lattix.com/) to create a Dependency Structure Matrix(DSM) to represent the software. Lattix LDM will generate the DSM from the output of "Doxygen" or from the output from "Understand for C++". It scales well - I had no trouble with applying it to a code base of 5m loc. I find DSM to be very useful in understanding the overall architecture.