Very old coder…

Have you noticed the high degrees of appropriated terminology that technologies and developers continue to borrow from the music industry? Seeing a conference called mix that had nothing to do with audio technology or bartending was the spark for me. I am getting on the “band” wagon.

Some examples:

Mash-ups: Used to define when a DJ takes tracks from the seventies or eighties, roughs them up a bit, gives the bassline a little more substance and suddenly you have Pat Benatar humming along to a Digweed track. Wait, now it also means slamming technologies together (not too many from the seventies and eighties) with no bassline and producing an app where none existed before.

Mixing: Used to mean when a sound engineer (like Daniel Lanois) puts his hands on the sliders and ensures that the background vocals are not popping out in front of the svelte tones of some surfer dude. Also means data from many sources all rendered in the same UI. With Flex you can build apps that let users work the UI with sliders, which could make users feel like they are in the booth.

There are more examples of this, but rather than “harp” on these, I thought it would be fun to keep the spirit of things moving along and generate some new ones. After all, who can argue the usefulness of digital rights management for documents and files, and that was clearly driven by the music and video industry need for piracy reduction.

B-Side: Beta version developer tools being used in production applications.

Classics: 4GL

Click track: The passing of billable time.

Dub: Changing the UI without changing the app logic.

Fade in: What developers do with new tools and languages.

Fade out: What developers do during sales presentations.

Detune: Removing clustering, connection pooling, etc to point out performance bottlenecks in applications.

Karaoke: Blogging about what someone else said and quoting them verbatim and freely while doing it.

Key: Seemingly necessary adjective before the word “differentiator”

Re-mix: Changing the perception of emerging technology to match what your boss says you need.

Payola: Free hockey tickets and baseball caps given to developers in exchange for their sworn loyalty, and hopefully a customer reference story.

Top 10: Bug list.

Vocoder: Very old coder.

Voiceover: What you have to do to make sense of marketecture regardless of the audience.

Got more?

3 Responses to Vocoder

  1. Nice, Ben! Here’s a few from my music days, rejuggled for the new economy:Patch Bay – a download page, usually found in the Tech Support section of most software companies’ websites.Room Tone – The faint hum of hard drives you only REALLY notice while waiting in abject boredom for your build to complete.Static – An effect occasionally witnessed by input sockets, when specifying the wrong character set or encoding type in your output stream.and an old favorite…Producer – The person in the suit screaming that your project needs to be more polished, sexier, and of course- finished yesterday. 😉

  2. Excellent!As a former DJ I suggest the follwing two:BPM – “Blogs per Minute” new counter on Google tracking the creation of new Blogs.Pitch Control – Have a Product Manager join the Account Manager on a customer visit to ensure the sales pitch does not get out of hand.

  3. Riel says:

    I guess following the DJ line I’d have to add:Squelch: the act of burying client feedbackRed Lining:Coding that’s done to satisfy a clients request that are over and above the orriginal project spec… usually to ensure a positive feedback rating despite the client simply being fussy rather than providing valid structural feedback.Field Monitor:Watching the signup rates and other web stats live as they are happening.:) Riel