Podcast #14

Discussion of Fox Music and DRM and Wil Shipley sticking his head up his, well, ahem. In the news, FireFox security warnings, a programming board game, the recording industry is definitely in an unreality bubble, and court rules you cannot tell the TSA that they are in such a bubble. Finishes with a rant about those called to programming and those that program anyway. Feedback to cmdln.net@gmail.com, http://cmdln.net/, or (360) 252-7284.

Download the show notes or the episode directly.

5 Replies to “Podcast #14”

  1. Enjoyed your distinction between desk jockey and vocational programmers. Agreed on all points. An addition to you comment on vocational programmers without empathy…you had suggested these types of folks could pursue things such as open source programming and hobbyist programming. I think another area these types can excel at is in writing code that doesn’t interact with the user. For example, code to process messages off queues, data access code, or batch programs would all be appropriate. This type of code typically doesn’t require much empathy as the end user is either a machine (e.g. a message queuing system) or another developer (as in the case of data access code).

    Keep up the good work. I really enjoy all the thoughful comments and reflection. 🙂

  2. If you can keep non-empathic, vocational programmers working on just such systems, sure. But I’ve found that limited resources and varyingly clueful managers mean that that sort of isolation rarely happens. Not a bad thought, though.

    API design, I would argue, the latter of your two examples, really should require a bit of empathy. I’m sure I am not the obly one to cheer a clean, clear API and curse an overly complex, impractically too theoretical, poorly documented API.

    As always, thanks for listening!

  3. A few years back, yeah, I probably would have a very stripped down, command line only setup for pod catching and pod casting. But as I get older, the geek fatigue, it flares up so easily, especially when the weather gets damp.

    Really, to me, the notion of the command line speaks more about understanding as much of the underlying principles and mechanics of any given system, not necessarily torturing yourself with minimalist tools that require constantly high expenditures of geek fu.

    May be time to re-visit or refresh the explanation of the moniker… 😉

Leave a Reply

Your email address will not be published. Required fields are marked *