Skip to main content

Certified Final Cut Pro Professional... Why?

Fourteen units into my MFA in Film and Digital Technology, I passed the Apple certification exam for Final Cut Pro X 10.2 (Post-Production). As a believer in digital composition and new media, having the skills to edit audio and video — and the ability to teach those skills — was important to me.

But, as a colleague noted, credentialism is fading quickly in the technology industry. Finally, people have realized passing an exam is not indicative of having essential job skills. When I was in college, Novell NetWare certification was the golden ticket to many jobs. Networking was a mix of hardware and software, with little standardization. Testing assured a minimal level of knowledge.

Today we have the return of the Builder/Maker culture that started the PC revolution. People learn to build Raspberry Pi contraptions, with Arduino controllers and Java or C code. Networks are easy, relatively speaking, compared to building a home robot.

The reason to take any exam today is to prove you have those minimum skills that hundreds of thousands without the certification also possess. It is a resume thing, especially in education. That's about all a certification is today, especially when compared to the NetWare days.

Apple has slowly ended many (most) of its exams. Few people in tech have renewed their Microsoft certifications. Does anyone obtain a Linux/Unix certification anymore? Credentialing has faded, quickly.

When will the same occur in education? When will we start to question the value of a degree that emphasizes vocational skills that can be learned and mastered outside the classroom? If credentialing starts to fade away in more fields, schools will need to prove their added value.

I have certifications, which are more important to schools where I might teach than they are to any technical employer. What does that reveal about the nature of credentials? (I've long doubted the value of teaching credentials compared to mentoring and team-teaching experience.)

I'm glad to have the Final Cut Pro credential, though I realize it is not that important compared to what I can demonstrate in a portfolio.

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.