Thursday, March 29, 2012

Scorched Earth Temporary Twitter Purge

If I've unfollowed you, it's not personal. I decided to take a drastic step and completely eliminate all hacking content from my Twitter feed.

The sheer amount of time I waste on Internet drama, especially Rails drama, is absolutely staggering. I'm basically quarrantining my attention.

Obviously, this involves cutting myself off from friends, which kinda sucks. However, this probably won't be permanent, so for now I feel fine about throwing the baby out with the bath water. I'll probably refollow you all again soon.

Saturday, March 10, 2012

Using iMovie For Camcorder Capture: Export Raw Video

If you don't fuck around with iMovie's ridiculous "projects" horseshit, and you just want to get your shit from a camcorder and onto your Mac, use iMovie to import the video, and then just quit out of that useless piece of fucking garbage and go to the "iMovie Events" folder on whichever drive you chose to use (I recommend a dedicated video drive, or several). The raw .mov files are right there.

Thursday, March 8, 2012

Simple Error, Simple Solution

I recently stumbled across a class on music marketing and experienced an epiphany which will probably strike anybody else as obvious. I have three main interests: acting, music, and code. I'm sometimes frustrated by how much easier it is for me to make money by writing code than by making music or acting.

Part of this, of course, is that acting and music are fields where supply outstrips demand, while programming is a field where demand outweighs supply by a phenomenal margin. But the not-so-shocking revelation I experienced is that I spend huge amounts of time marketing myself as a programmer via conferences and social media. Given the nebulous border between goofing around on Twitter and social media marketing, it's difficult to calculate, but it's probably an utterly gigantic amount of time.

Likewise, I hit Hacker Newspaper much more frequently than Create Digital Music, Motionographer, or Deadline Hollywood, and I share my creations on GitHub but not on SoundCloud and only somewhat on YouTube.

It should be pretty obvious what I'm going to do to change this.

This Is Why Node Beats Rails

Me, a few weeks ago:

I think listening to Node.js hype at all is foolish. It's just not worth having an opinion about. It leads to a foolish brattiness in those who believe it and an equally foolish hostility in those who harp on its flaws. Hype is hype. It's bullshit. Let it go. Node will change course to accomodate all its critics sooner or later, just like Rails did, and in the meantime there's a lot of exciting work going on. People are building very interesting things, and the browser landscape is changing so fast that by the time Node grows up a little, web development will be an entirely different world.

Liam Kaufman, today:

I always found it odd that accessing DOM elements with Ruby, or Python, wasn’t as easy as it was with jQuery...I was pleasantly surprised to discover that it’s possible to use jQuery to parse web pages with Node.js.

Monday, March 5, 2012

Real Talk And Real Action

Real Talk:

Real Action:

I don't know why this band doesn't have ads on this video, but if they did, YouTube would be paying them every single time somebody saw it. As it is, iTunes is paying them every time somebody buys their song -- which still puts them ahead of nearly everybody who's dealt with the entertainment industry before iTunes launched.

Sunday, March 4, 2012

Ruby: Public/Private Distinction Belongs In Comments, Not Code

Had a minor blog/Twitter skirmish about this a year ago with Loren Segal. Realized why I was right when I revisited TomDoc and took a look at how it handles the public/private distinction.

# Public: Duplicate some text an arbitrary number of times.
# text  - The String to be duplicated.
# count - The Integer number of times to duplicate the text.
# Examples
#   multiplex('Tom', 4)
#   # => 'TomTomTomTom'
# Returns the duplicated String.
def multiplex(text, count)
  text * count

I'm not out to put words into the mouth of TomDoc's author -- he might disagree -- but I believe TomDoc gets it exactly right, putting that distinction into comments. I firmly believe putting that distinction anywhere except comments is rude and disrespectful to your fellow developers. It goes in the comments because it's opinion.

First, anyone who's done non-trivial stuff with Rails has seen "private" APIs turn effectively public, even if only for brief periods, due to the proliferation of hacks. Second, I think it's presumptuous and inappropriate for developers to set up little obstacles to creative misappropriation. Both these problems stem from one common root: You really can't tell, when you write the code, which parts of it are going to be most useful for other people. Partly because people will do things you hadn't expected, and partly because your code may contain subtle bugs they need to work around.