Episode 142 – The Barbed Wire on the Nuts

San Jose Tea Cups

Download the episode directly or listen above.

See if you can’t leave me an inch from where the zipper (burps) ends, round, under my, back to my bunghole, so I can let it out there if I need to.

In this well documented episode, Charles and I talk about:

  • Do you flush the toilet when someone is talking on the cellphone in the bathroom?
  • We discuss Charles “professional” uses of video conferencing.
  • How bit torrenting works, like, if you want to watch Heross.
  • XBox Live and Charles ordered and Android G1 dev phone.
  • Google Native.
  • KirinDave’s post on ruby.
  • I solicits advice for what type of content you, the dear reader, would like to see more of.
  • Why not be like LBJ and call people every morning? (Not exactly like this, though.)

0 thoughts on “Episode 142 – The Barbed Wire on the Nuts

  1. Was that really the voice of LBJ? I just loved that burb – it almost sounded like he was taking a dump while talking on some special phone to the tailor.

    As for all the extra “content” that you could churn out on drunk and retired – all in the aid of a Cote Beer Fund (a noble goal – we should all aim to have a passive income that can buy us a bottle of burbon a month) – the problem I have with a blog, is that it now takes me forever to get around to openening up a feed reader, and when I do, a million things demand my attention. the Feed readers are the new inbox overload.

    Friendfeed kind of does this anyway – a nice lite stream of turdlets of knowlegde from the internets all through the day. And twitter, for a smaller circle of friends and contacts.

    Perhaps just do it on the blog – put push it out via FF/twitter etc so folks like me will glance in passing ?

  2. Regarding your plea for new blog content suggestions, I would recommend considering the creation of consistent topics that will entice users (i.e., readers) to not only anticipate the availability of specific content on certain days of the week, but to increasingly look to you as expert analysts in the indie, open source, and related development and technology fields.

    Since too many sources of information (i.e., “noise”) already exist within The Internet, it would be interesting to see your content minimized to well-defined, predictable constraints. Additionally, the content should be mostly timeless, such that you could package up a year’s worth of blog entries and publish it as a book later on — see Lifehacker and Grammar Girl as successful examples of this approach. Some ideas for content are as follows:

    Monday: The Most Important News — An essay inspired by the most important developer or industry-related news article, podcast, or screencast from last week. It should explain why the news matters to developers, and it should include succinct, one or two paragraph-long commentaries from a panel of “celebrity” developers recognized as experts in their respective technologies (e.g., Charles the Ruby expert, Dick Wall the Java expert, Douglas Crockford the JavaScript expert, Mr. COBOL the COBOL expert). The conflicting personalities and philosophies of the experts is the twist that would make the content unique and entertaining for developers. These blog entries could be made “timeless” by examining general concepts and trends, and the series could be marketed as a “Web 3.0 Readiness Guide” and later sold as a book before Amazon is inevitably flooded with “Web 3.0” offerings.

    Tuesday: The Most Important Line of Code — Charles and other developers reflect back on the most significant piece of code that they wrote in the past week, minimizing the discussion to a liberal “line” of code. They could describe their motivations and inspirations for writing the code, then they could explain the code’s impact on their lives and the world. This would be a not-too-serious series of entries that speaks to the joy of coding (i.e., an uplifting, inspirational “Chicken Soup” series for developers) that would have the side effect of introducing your audience to new techniques, languages, and technologies. Alternatively, Charles could write about the use of developer productivity techniques such as “The Chess Clock” or review development tools such as “The Command Line.”

    Wednesday: The Most Important Image — A random image (perhaps one captured using an iPhone) is posted, and developers are asked to provide a caption for the image using code. This series could eventually be turned into a coffee table book, “How Developers See the World.”

    Thursday: The Code Doctor — “The Code Doctor” analyzes and critiques code submitted by readers seeking help with their programming problems (with careless disregard for the feelings of the authors). Of course, the submitted code could be artificially created by “The Code Doctor” without the readers suspecting a thing. This series of entries would be very entertaining if “The Code Doctor” was intentionally trying to gain a notorious reputation for being cruel and sardonic in his or her code reviews, and it would probably attract a cult following amongst junior and senior developers alike.

    Friday: The Most Insignificant News — A “fun” article featuring recurring, monthly topics such as the following:

    Week One: Best/Worst Developer Beverage (or Food) of the Month — Review food or drinks (e.g., bourbon), but instead of describing the food in terms of “mouthfeel” and “bouquet,” try to creatively map your food experiences back to developer-related topics (e.g., “This beer tastes like ActiveX.”).

    Week Two: Best/Worst Developer Film of the Month — Review films that are significant for developers, with a heavy bias toward zombie films and B-movies to avoid. Perhaps explain how the movie would have benefitted if the lead character were a programmer.

    Week Three: Best/Worst Developer Game of the Month — Review games that are important for developers, with a heavy bias towards zombie games (and/or M.U.L.E.).

    Week Four: Non-Developer Challenge — Approach and film non-developers in public places (e.g., intoxicated people leaving bars, college students leaving Computer Science classes), and ask them to interpret or debug lines of code from well-known open source projects.

    In summary, there are many subject areas that can be included as new blog content, however setting up a distinct, Drunk and Retired flavored “program schedule” might be the key to attracting and retaining an audience that translates into substantial page views (i.e., cash).

  3. Michael Neale: yup, that is LBJ. I bet he was taking a dump. The “hold one” part must have been when he had to “cut a deal.” Thanks for the comments on blog stuff. This blog should show up in FF, so you should be cool. I suppose I could auto-Tweat posts here to, or manually.

    Bender Rodriguez (excellent alias!): man! thanks for the extensive write-up. I think you’re narrowed down topics are they way to go.

    Arley: as always, we appreciate you Googling for our lazy asses. Google take over the desktop: check!

  4. Content I like… your Skote stuff is my favorite, an Austin daily living thing, helps me keep up on the hood. Java updates. Beer anticts. The trademark Cote “what’s up with that?” Cheeseburger reviews. Fat Uncle.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s