Desmond File

Blog archive

Your Turn: Is Computer Science Dead?

Last week, I noted an article that took a dim view of trends in the programming arena. And readers had a thing or two to say about it all.

Reader Joel runs a skewer through the argument with this incisive response:

Of course not. It's a great hallmark of progress that most people can work and live their lives at much higher levels of abstraction than before. I for one don't want to make my own clothes or catch my dinner.

There will always need to be a handful of people writing microprocessor code for the assembly programmers, a few hundred assembly programmers writing compilers for the C/C++ programmers, several thousand C/C++ programmers building frameworks like Java and .NET for the application programmers, and finally, millions of application programmers building the apps that 99 percent of the world actually uses. If Mr. McBride can point to a single time in computer history when there were more software developers, more (or better) development tools, or more programs in existence, I could take his concern seriously.

Did automotive science die when mass production put 99 percent of the tinkering machinists out of work? Or did it encourage even more investment because the ones who remained multiplied their innovations by 10 million cars instead of one? Yes, someone somewhere needs to know how to write the assembly language code that makes all the levels above it possible, and I hope those people are getting paid handsomely. But the other 99.9 percent of us should take a quiet moment to be thankful it isn't us, then get back to writing our applications instead of worrying about the death of the field.

Mr. McBride correctly states that computer science curricula need to be more relevant and vocational, but I hope he understands that if that isn't done, it will be computer science departments that die, not computer science.
-Joel, New York

Laura is not as upbeat, but she makes a similar argument.

It's the computer scientists who make the "era of visual programming languages where 8-year-old kids can program robots with a drag-and-drop interface" and other wonderful things possible.

Computer science is certainly not dead. But let's be realistic: Job opportunities in this country are simply not what they were. At least, that is the present perception. The world isn't flat, as one author has famously preached; it is cone-shaped, everything sliding down a slippery slope.
-Laura, Connecticut

Do you agree with these counterarguments? Was pundit/humorist P.J. O'Rourke right when he wrote that those who pine for a perfect era in the past are forgetting about the pain that past produced (including *shudder* painful dentistry)? Let me know at mdesmond@reddevnews.com.

Posted by Michael Desmond on 03/21/2007


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube