5 Subjects Every Computer Science Student Should Learn

[humble3d]

5 Subjects Every Computer Science Student Should Learn

I was fortunate this year to attend the Association for Computer Machinery’s SIGCSE (Special Interest Group on Computer Science Education) conference, where there was a good deal of conversation about what a modern computer science curriculum should include.

 

Technology changes quickly and it can be difficult for academic programs to keep pace. Still, if computer science students are to contribute meaningfully to the field in either industry or research jobs, it’s critical that they learn modern computing skills.

 

Here are five subjects I think every higher education institution should teach their undergraduate computer science majors:

 

1. Parallel Programming

The single, standalone server with one CPU has gone the way of the dodo bird, displaced by the cloud, server farms and multithreaded parallel processors.

Yet colleges and universities are still mainly teaching their undergraduates sequential programming—programs that execute instructions one after the other—as they have for decades.

 

Modern computing environments and massive data sets demand not just that we process multiple instructions simultaneously across multiple servers (distributed computing), but also that programs be written to process multiple instructions simultaneously on multicore chips within multiple servers and devices.

 

Too often, parallel programming is relegated to a single chapter in a textbook, easily skipped when time in the semester runs short.

 

To prepare students for high-performance computing, big data, machine learning, blockchain and more, we must teach them to both think and program in parallel.

 

2. Green Programming

With the ubiquity of battery-driven computers, energy efficiency is more important than ever. The more we ask our smart devices to do, the more energy they need to do it and the more quickly they exhaust their batteries.

 The same is true for massive server clusters, where fires related to energy-consumption are not uncommon as we demand faster and faster processing of more and more data.

 

How you architect a software program directly affects how much energy is needed to execute the program, yet few undergraduate programs teach students about this relationship.

 

In a fast-warming world, one in which we dream big dreams about all the ways artificial intelligence and high-performance computing will make our lives better, it is imperative that we write energy-optimized software.

Students will not be able to do that if we don’t teach them how.

 

3. Collaborative Development

 

Academia persists in trying to measure what individual students know.

 

In most programming classes, students start from a blank screen and write clean code independently or, less often, with a partner.

 

But this isn’t how software is engineered in the real world.

 

Professional software engineers almost always start with someone else’s code and work collaboratively in large groups to modify, improve and correct that code, which is then integrated with code written by other engineers in other groups.

    
It’s common for software development groups to include people from different countries, in different time zones.

 

Working effectively requires team members to communicate well in different languages and across different cultures.

 

It also means that someone else needs to be able to look at your code and know what it does, so following formatting standards and providing clear commenting are critical.

However, in our desire to ensure that each student understands every programming concept and rule of syntax, we overlook opportunities to teach collaborative software development and help students develop critical professional skills.

 

4. Hardware Architecture

 

In the minds of most college students, IBM, Intel and AMD—the inventors and developers of the multicore processor—are old news…old companies founded by old guys.

Mobile applications are where the action is.

 

But mobile apps are driven by data, usually by a lot of data, and they won’t be of much use without the processors, databases and networks that power them.

Computing works and advances based on the entire system, from the power source to the user interface, and students will be more successful if they know how to open the box and “kick the tires.”

 

They can then optimize for energy efficiency and write parallel code that makes use of new hardware architectures. They can manage caching, memory architecture and resource allocation issues. They can explain and explore quantum computing.

 

Computer science doesn’t stop at software or coding.

 

Students need foundations in hardware architecture, too, including electrical engineering and physics.

We need computer scientists who can test and push the boundaries of hardware just as much as they push what can be achieved with software.

 

5. Computer History and Ethics

 

Something I heard at the Turing 50th Anniversary celebration last summer has stuck with me: Computing is not neutral.

 

It can be used for good or evil.

 

It can be used to help people and it can be used to manipulate and harm them.

For several decades now, we have been making computing advances for the sake of computing, because what we can make computers do is cool, because the challenge of the next thing is too alluring to pass up, because there is money to be made if we can do “X.”

 

Just because we can do something with computing, however, doesn’t mean we should.

 

Computing power is so great that we need policies to regulate and manage it, in order to protect and benefit people.

 

It’s important for students of computing to understand its history and to take courses grounded in ethics so they can make responsible decisions and guide others.

 

They should know computing’s historical villains and heroes, its inventors and detractors and how it has been used to benefit and hurt people.

 

The old saw applies here: If we do not learn our history, we are doomed to repeat it.

 

Even in a crowded curriculum, we must ensure students are gaining the skills and knowledge they need to become technology innovators, business leaders and positive contributors to society in the coming decades.

This list is only a starting point.

 

http://partners.wsj.com/oracle/five-subjects-every-computer-science-student-learn/?