Programming languages should fulfill the foreign language requirement
Written by Zachary Frank|
January 20, 2014
As Dean of the Faculty of Arts and Sciences Kate Conley told William and Mary News, “Our faculty have moved carefully, precisely, and boldly to design a liberal arts curriculum that’s right for our time and looks to the future.” Ms. Conley, I trust that the faculty has proceeded with the best interest of the undergraduate student body in mind, but I am hard-pressed to believe that four semesters of Italian is a more forward-looking alternative to four semesters of the three basic programming languages of website design.
Ms. Conley, you say that COLL is right for our time, and it would be platitudinous for me to say that we live in an increasingly digital world — one in which computing power increases exponentially and wherein a rudimentary understanding of web design would prove useful on the job market — yet, the faculty has not moved to arm students with perhaps the greatest boon it could afford them: technological literacy.
Beyond the financial advantages a student would gain from learning programming languages, there is a more immediate, practical concern that ought to be addressed: Students who do not care to take foreign languages will not care to learn them. It’s important to remember that languages take a tremendous amount of time and effort to learn. This is by no means a reflection on the terrific language professors teaching at this school, but no rational student will devote precious time to four semesters of a language that he or she does not care about. Students will prioritize other classes and extra-curriculars before the language, hastily study for tests at the last minute, and watch their GPAs fall bit by bit. But give those students something of immediate and practical value, something from which, on their laptops’ monitors, they can see the immediate results of their efforts — and the faculty will see language students rise to the challenge.
Email Zachary Frank at firstname.lastname@example.org.