Anthony Panozzo's Blog

Was writing some code the other day, and then wanted to have similar functionality in a different area of the codebase. I did not want to directly copy and paste, as I consider this to be a very recognizable code smell. Basically, copying and pasting is a clear indicator that there is similar structure that is not being realized. It is similar to making up really complicated equations and models for why planets in the sky do loop-de-loops, and then understanding that they all revolve around the sun. That understanding simplifies things.

However, it was tough to think about what needed to be abstracted out of the solution that I was going to use. What I did was to copy the original to another area, change it to work in that context, and then factor out the common parts as best as possible to a library function. I expect to use this function a few times, so this seems to make the most sense from a flexibility and maintenance perspective.

I recently watched Randy Pausch's lecture on time management (1 hour). It's a good reminder of things to consider when dealing with people and simultaneously trying to accomplish great things. Inspired, here are some of my communication management hacks.

Generally, I subscribe to Paul Graham's Maker's Schedule, Manager's Schedule. I attempt to identify large blocks of uninterrupted time using the fold calendar and then avoid interruptions while I get stuff done.

Sometimes I'm not looking to get that much done, so I disregard these concepts. But they have served me well in times of need.

Communication notification philosophy

Basically, turn off real-time automatic notifications of communication while leaving some channel for messages of critical importance.

I like Tim Ferriss's adage of "sometimes you need to let small bad things happen to get large good things done."

Email is simply not the correct medium for anything time-sensitive because it is asynchronous. You should not expect a response in less than three days to email you send, and you should not need to respond to emails in less than a day. No email should be important enough to warrant blocking the most important thing you should be doing. If the concern truly is pressing, the person will just have to call you. Set the communication guidelines clearly, and help others understand how you can best be reached.

I have an existing Rails repo that is trying to run Ruby 1.9.2. I attempted to check out the code and get things running, but had a small problem.

$ rake spec
(in ...)
rake aborted!
no such file to load -- net/https. Try running apt-get install libopenssl-ruby
(See full trace by running task with --trace)

Although I tried sudo apt-get installing the various libopenssl-ruby and libopenssl-dev and whatnot, I kept getting the same error message.

It's fairly easy to do with some Rails libraries, although it's different from the way that most people have suggested online due to Rails 3 changing the way that some things are laid out. If you want to use IRB or something else to pretty-print XML with Ruby, try the following:

require 'rubygems'
require 'ap'
include ActiveModel::Serializers::Xml

raw = File.read(filename)
parsed = Hash.from_xml(raw)
ap parsed

The ap is the awesome-print gem. It prints out the resultant structure in an easy-to-read format. I like the output of ap better than pp, and I like using RoR's from_xml better than, say, REXML, Nokogiri, or XmlSimple. For the first two, you basically have to roll your own pretty-printer (from what I understand). XmlSimple works, but the output seems to be a bit funky (too many arrays for keys, etc.)

If you're wondering what the right shebang line is when you're using RVM, it's:

#!/usr/bin/env ruby

For searchers, it's also called a hashbang, hashpling, pound bang, or crunchbang.