Skip to main content

Change, Not for the Better

There are colleges and universities moving towards 120-semester-unit bachelor's degrees, down from 132 or more in many cases. Others are seeking ways to offer "accelerated" degrees in three years instead of four. Of course, the not-so-secret truth is that many students take much longer than four years to graduate as it is — for a variety of reasons.

Nationally, the four-year graduation rate from our state and regional public universities is 31 percent, according to Jeff Selingo, editorial director for the Chronicle of Higher Education. Private universities graduate a slight majority of their undergraduates, 53 percent, "on schedule" based on their degree plans.

Consider the following example, which is representative of graduation at state institutions nationally:
June 11, 2012. — Middle Tennessee State University is making efforts to increase its graduation rate, but still just over half its students are completing college within six years.

According to the Tennessee Higher Education Commission, 53 percent of MTSU students who began in fall 2004 graduated by 2010. That was fourth best among the state's four-year public universities. The University of Tennessee, Knoxville, was tops with 67 percent. Tennessee Tech had a 55 percent graduation rate, and UT-Martin's rate was 54 percent.

Nearly half of students enrolling at MTSU don't graduate, and nearly a fifth don't make it past freshmen year.
— The Republic; Columbus, Indiana (http://www.therepublic.com/)
Cutting the unit requirements, shifting to eight-week rolling enrollments, and other changes meant to make college "more convenient" might increase the completion rates, but will our institutions still be providing solid liberal arts educations? We've already shifted from liberal arts to "professional prep" within many degree programs, but this emphasis on graduation rates concerns me.

Online programs are particularly easy targets for redefining what a degree means. I know many people have used online programs, especially the for-profit programs, to complete degrees. These students are focused on career requirements and don't necessarily ponder what is missing from a professional prep program that omits or compresses the traditional pillars of the liberal arts general education.

1. Lost in the Rush

Having taught eight-week, 12-week, 15-week, and 16-week semesters, my experience and those of many colleagues is that content has to be cut the shorter the course time. While we can argue the class time doesn't change, it is much harder to read the same content in eight weeks. Cramming 16 weeks into eight might seem possible in theory, but the reality is that the courses are "light" versions in too many instances. (If you've ever taken a summer school course, you know it is different.)

2. Less Shared Knowledge

When you move to "rolling enrollments" one of the consequences can be the loss of "prerequisites" from course to course. If any student can start at almost any time, you can't have a long list of required courses. The result is that every course has to reintroduce basic concepts: you cannot "build" on past knowledge as you can with the traditional academic model.

I've had a professor tell me that three weeks of each of his eight-week courses were review. The benefit might be that students are sure to get some concepts time and time again. Reinforcement works. But, this also causes yet more "rush" through the course content. More content ends up sacrificed to convenience.

3. Sacrificing Breadth

To rush students through programs in three years, 120-units or less, courses must be cut. It is not electives or discipline-specific courses that are cut in the unit reductions. Instead, core liberal arts requirements are sacrificed. The idea of a well-rounded education gives way to vocation-centric certification.

We have problems with our colleges and universities, but making them easier and more convenient is not an improvement. Less rigor means bachelor's degrees will suffer the same devaluation we've seen in high school diplomas.

How can we even consider less rigorous degree programs when large numbers of college students need remedial math and English courses?
May 29, 2012 (AP) - Each year, an estimated 1.7 million U.S. college students are steered to remedial classes to catch them up and prepare them for regular coursework. But a growing body of research shows the courses are eating up time and money, often leading not to degrees but student loan hangovers.
— Businessweek (http://www.businessweek.com/ap/2012-05/D9V2C75O0.htm)
These students won't be helped by higher education cutting requirements. If anything, I'm increasingly in favor of increasing the undergraduate requirements. If that means students need seven years to graduate, I don't see that as a problem. You shouldn't graduate until you have received a well-rounded liberal arts education and professional preparation. If you only want job skills, that's the role for vocational and technical institutions.

Learning should be our first, second, and third concern. Graduating "on time" is less important and not our most serious problem.

The push to graduate quickly is a response to the cost of education. That's a different issue and one we should address in other ways.

Comments

Popular posts from this blog

MarsEdit and Blogging

MarsEdit (Photo credit: Wikipedia ) Mailing posts to blogs, a practice I adopted in 2005, allows a blogger like me to store copies of draft posts within email. If Blogger , WordPress, or the blogging platform of the moment crashes or for some other reason eats my posts, at least I have the original drafts of most entries. I find having such a nicely organized archive convenient — much easier than remembering to archive posts from Blogger or WordPress to my computer. With this post, I am testing MarsEdit from Red Sweater Software based on recent reviews, including an overview on 9to5Mac . Composing posts an email offers a fast way to prepare draft blogs, but the email does not always work well if you want to include basic formatting, images, and links to online resources. Submitting to Blogger via Apple Mail often produced complex HTML with unnecessary font and paragraph formatting styles. Problems with rich text led me to convert blog entries to plaintext in Apple Mail

Learning to Program

Late last night I installed the update to Apple's OS X programming tool suite, Xcode 4. This summer, in my "free" time I intend to work my way through my old copy of Teach Yourself C and the several Objective-C books I own. While I do play with various languages and tools, from AppleScript to PHP, I've never managed to master Objective-C — which is something I want to do. As I've written several times, knowing simple coding techniques is a practical skill and one that helps learn problem solving strategies. Even my use of AppleScript and Visual Basic for Applications (VBA) on a regular basis helps remind me to tackle problems in distinct steps, with clear objectives from step to step. There are many free programming tools that students should be encouraged to try. On OS X, the first two tools I suggest to non-technical students are Automator and AppleScript. These tools allow you to automate tasks on OS X, similar to the batch files of DOS or the macros of Wor

Learning to Code: Comments Count

I like comments in computer programming source code. I've never been the programmer to claim, "My code doesn't need comments." Maybe it is because I've always worked on so many projects that I need comments  to remind me what I was thinking when I entered the source code into the text editor. Most programmers end up in a similar situation. They look at a function and wonder, "Why did I do it this way?" Tangent : I also like comments in my "human" writing projects. One of the sad consequences of moving to digital media is that we might lose all the little marginalia authors and editors leave on manuscript drafts. That thought, the desire to preserve my notes, is worthy of its own blog post — so watch for a post on writing software and notes. Here are my rules for comments: Source code files should begin with identifying comments and an update log. Functions, subroutines, and blocks of code should have at least one descriptive comment.