My Professional Blog

It is hockey season now and so I’ve been paying attention to the local team and all things surrounding it.  So today I noticed that Mike Modano has relaunched his site.  Well, Mike has been one of my favorite players for more than a decade and since I make my living in technology its of interest to see what the site looks like.

So when you go to www.mikemodano.com, you see a nice enough site, but I am not impressed with animated GIFs or Flash animation.  These days I quickly resort to viewing the source to see just how astute the designer or design agency is.  So in this case, what do I find?  Obtrusive javascript and a tables-based design.  Yikes!  Maybe I, myself, need a reality check, but I thought we were past this kind of implementation approach.  Its just too easy to build it the right way with web standards these days.

So I had to go explore which firm put this site together.  Clicking the link at the bottom of the page takes me to Nform Interative which contains an all Flash home page with a logo that is clipped in Firefox and a page entitled “temp_home_page”.  What’s more, there’s no pages to describe the agency.  Needless to say, its completely SEO-unfriendly.  Wow!  And they got the Mike Modano gig?!

This is all relevant to me because I am embarking on a freelance career where I do contract programming and website development.  I do all this with the latest trends in technology and web standards.  So, test-driven development, CSS-based designs and lean standards-compliant markup are staples of anything I would do.  But it highlights to me that we still have a long way to go because people are still building old school sites and clients are still paying for them.

Hopefully, I can articulate why my approach is better and start winning some of these clients.  Doing so will offer them bigger bang for the buck and position them better for the future.  Its too late for Mike’s site, though.

Out of the blue yesterday, I received a request to take down a testimonial on my “hire me” site that I had received from a colleague from a past employer.  There was some question about the testimonial being a violation of that company’s policies on employee references.

As I had done on every testimonial, I cited their current company and the company where I worked with them.  These citations give the quote context and are helpful to the reader.  When I collect a quotation, I always ask how someone wants to be cited and give them the opportunity to differ from my normal method.  I even let them know when its been posted to the website.

However, in this case, the citation ran afoul of the company policy which forbids any employee from giving a reference to a past employee.

When I first got the takedown email, I was stunned and thought that they must have misunderstood the policy.  It was a positive comment, of course, and I felt like it was good for both the company and me to have positivity out there.  I had even wondered about freedom of speech issues — surely my colleague was entitled to express an individual opinion.  But alas, I took the citation down so that the person’s opinion is not blurred with the company’s opinion.

But it made me wonder if the citation really blurs the issue.  It was a personal opinion, not a corporate endorsement, otherwise I would cite the company alone.  In the end, I respect everyone’s policies and I definitely want to ensure that my past colleagues are not disadvantaged by saying something nice about me.  I will just be a lot more careful in the future, I had no idea that anyone would ever have a problem with this.

People have asked me quite a lot lately what I’m going to do now that I’m free and clear of Click Here and my pat answer has been one of two or three things:

1. Find a product-oriented company with a high-performance team building something amazing, or
2. Bootstrap my own tiny consultancy, and / or
3. Build an amazing product.

As luck would have it, I’ve already landed an interview at a company that offers the first option. I’m excited about the interview, but realistic about the possibilities. Because they appear to be a high-performance team, they are guarding the entrance quite closely. My level of intrigue is all that much higher because the interview process is anything but easy and normal. Suffice it to say that you can’t get hired by being a good guy and liberally dropping high-impact buzzwords. You may laugh, but I’ve been hired through such good-guy interviews.

This is a position which features the use of Java as their primary implementation language, so my challenge is to get back into the Java mindset after several months of Ruby development. My friend Mike once supposed that I would never return to Java. Its possible he’s wrong as I could be circling back. Working with Ruby is fun, but my talents and experience position we well for a Java shop and there is more of a job market there too.

But even as I say that, I must admit that looking at Java for the first time in a few months has surprised me. Java hasn’t changed, but it seems that my mind has started to think in Ruby. I am actually alarmed that a language I’ve worked in for years could be subject to this kind of transition. I found myself asking fundamental syntax questions. So I wondered if this had happened to anyone else. Or is this just a by-product of my being 43?

Well, I’m not worried about picking Java up again, but I am picking a problem to code to get my head back into it. I still have a series of Java projects from an interview process I went through in June (yes, I was offered the job), so I’m going to work through one of those. To make it more fun, I may try to integrate it into a JRuby on Rails project and do a local deploy. This will enable me to prepare for the interview and explore the integration possibilities for JRuby and Java.

What happens if I don’t get the job? Well, that’s a real possibility, so I’m planning my bootstrapping activities for my consultancy. Having done recent work for a medium-sized consultancy, I know there is work out there and I know that I can provide high-quality work for a portion of the price that bigger companies are charging. But as every entrepreneur knows, you cannot be successful without customers, so my biggest challenge will be to construct a marketing machine capable of producing a sustainable pipeline of work. For technicians, this is not an intrinsic skill, so I’ve been thinking more about marketing than my technical skills — the latter is the easy part.

In some ways this takes me back a great many years ago when I created a small software company, SportSoft Systems, which created and marketed Fantasy Football software and a few other things. This was back 20 years ago and my product was just about the best out there. Had I only known that the fantasy sports craze was to explode, I would have stuck with it. I did actually make decent money, but the pressures of supporting the product and building in new features every year while being an ethical employee at my primary job caused me to discontinue my efforts.

So for now, I’m circling back — either to the Java world or to a world where I build my own company. Should be fun wherever things lead.

I have been making my living for the last 20+ years following processes.  Unfortunately, I have not seen that processes have been maintained, evaluated, and evolved as they should be.  My theory is this: no one collects any metrics anymore, so no one knows how well their processes really work.

There are two adages that I believe apply:

You cannot manage what you do not measure.

What gets measured, gets done.

All too often, processes go stale or drift so far from their intent that it becomes a disadvantage to be process-driven.  If you work for such a company or even if you have your own personal processes, consider putting into place a layer where you measure parts of the process.  I don’t know what those measurements would concern, just start measuring something.

Once you have a reasonable set of data points, attempt to perform some analysis to see if you can draw any conclusions.  At a company I worked for in the past, we measured the effectiveness of peer reviews by tabulating documentation defects and code defects detected by the group and by person.  In a separate activity, we measured defects detected by our QA group and ultimately by the customer community.  My point being, we could take all this data and eventually determine our effectiveness and even predict our future performance.  Being able to predict our performance enabled us to estimate and plan much better and thus be more competitive.
If you are a company that suffers from this, you need to swallow the Red Pill and see the truth.  Measured and analyzed processes can become your Morpheus.  If you swallow the Blue Pill, you will almost certainly continue to languish within old, non-value-added processes that lead you into an uncertain future.

You should now be conjuring up an image of Laurence Fishburne gesturing you to come and get some.

Many people tend to place logic within a method named for the callback (e.g. after_destroy).  This works fine, but tends to be less maintainable, in my opinion.

You basically have a method called after_destroy (or whatever), but you don’t readily know what its doing.  A better approach is to write an intention-revealing named method and reference that in the reference to your callback method.  You then can see through the method name what is happening in response to the event.  Further, the method can be used at other times.  This approach restores a bit of maintainability to your code.

I have included an example of this approach below.  You’ll have to visualize the before version — I don’t like posting less maintainable code because sometimes people skim it without reading and take it as good code.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

class Rating < ActiveRecord::Base
  
  # —- Associations —-
  
  # The rateable that was rated.
  belongs_to :rateable
  
  
  # —- Callbacks —-
  
  after_destroy :update_ratings
  
  
  # —- Calculations —-
  
  # Updates the parent’s rating count and average rating.
  def update_ratings
    rateable.update_ratings
  end
end

One of my pet peeves in code is the absence of constants and thus the prevalence of “magic numbers” in their place. Constants add a touch of readability and semantic meaning and magnify the maintainability of the code.

As a simple example, here’s a partial model featuring constants to aid in clear validation specifications:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

class Email < ActiveRecord::Base
  
  MAX_FROM_LENGTH   = 30
  MAX_TO_LENGTH     = 100
  FROM_LENGTH_RANGE = 1..MAX_FROM_LENGTH
  TO_LENGTH_RANGE   = 1..MAX_TO_LENGTH
  TO_FORMAT         = /^[_a-z0-9+.-]+@[_a-z0-9-]+.[_a-z0-9.-]+$/i
  NOTE_LENGTH_RANGE = 1..DB_TEXT_MAX_LENGTH
  
  # —- Attributes —-
  
  # Attributes protected from mass-assignment (as through forms) 
  attr_protected :sent_at
  
  
  # —- Validations —-
  
  validates_length_of   :from, :within => FROM_LENGTH_RANGE
  validates_length_of   :to,   :within => TO_LENGTH_RANGE
  validates_format_of   :to,   :with   => TO_FORMAT
  validates_length_of   :note, :within => NOTE_LENGTH_RANGE

As you can see the model defines constants to enforce length maximums and in turn the ranges. You could argue that the range constants are less useful since you have to refer back to the constants section to see them, but that’s a matter of taste. I like having them.

With constants like these properly placed in your model, you can take advantage of them in your migration. Here’s a partial example:

1
2
3
4
5
6
7
8
9
10

class CreateEmails < ActiveRecord::Migration
  def self.up
    create_table :emails do |t|
      t.column :emailable_id, :integer, :null => false
      t.column :to,         :string,  :null => false, :limit => Email::MAX_TO_LENGTH
      t.column :from,       :string,  :null => false, :limit => Email::MAX_FROM_LENGTH
      t.column :note,       :text,    :null => false
      t.column :sent_at,    :datetime
    end
  end

The advantage here is that your model and your migration are now in synch for field maximums. If that’s not enough, then consider what you can now do in your test code:

1
2
3

def test_invalid_with_long_to
    assert_value_for_attribute_invalid(Email.new, :to, filled_str(“X“, Email::MAX_TO_LENGTH + 1))
  end

So now, if you change your mind and decide you need to lengthen your fields, you need only change your model constants. Your migration could be rerun or you could add an additional migration which applies the new field length. And lastly, your test code doesn’t have to change.

I think this is simple, yet very much worth doing.

I have added a few features and made a few bug fixes to GeoKit. These are as follows:

• [FEATURE] Added timeout support for geocoder web service calls
• [FEATURE] Added proxy support for geocoder web service calls
• [FEATURE] Added support for SQL count queries — they work like the finders
• [BUG FIX] Fixed range finders to support exclusive ranges
• [BUG FIX] Fixed configuration to use class accessors instead of constants (that were being reinitialized)
• [BUG FIX] Eliminated bogus IP address returned from IP geocoder when the request IP is 127.0.0.1
• [BUG FIX] Fixed GeoLoc’s hash method and added an alias to_hash
• [REFACTOR] Require statements to be cleaner all the way around

Thanks to the following who reported bugs that got fixed or who submitted patches that were used in part or in their entirety:

• Norbert Crombach
• Justin French
• Hoan Ton-That
• Jason Seifer

Thanks to everyone for your feedback, patches, and compliments. If I didn’t name you explicitly, it means that your thanks by name will come later.

Since I am in a GeoKit development mode right now, let me or Andre know if there are other features, bug fixes, or patches I should be aware of. I know that we had been planning to modify our configuration approach to be compatible with YM4R, but that’s been delayed indefinitely. They use a YAML file and we use the environment configs — and there really wasn’t a compelling reason to mess with it. Also, no UK geocoding yet — didn’t receive too much demand.

Please review the README for updates and take a look at the new environment config template under the plugin’s assets directory to see how you should config GeoKit. And by all means, let me know if there are issues that I’ve inadvertently created for you.

Anyone tried to get a good domain name lately?  If you have, its likely you’ve been frustrated with the options that you have left.  Of course, that is the case only if you wish to have a domain name that matches the name of your site.  However, there may be a creative solution available to you.

Consider taking the Google or Yahoo approach whereby your sites are “properties” and are named at the subdomain level.  For example, http://maps.google.com or http://local.yahoo.com.  Taking their examples, you can see that their primary domain name has nothing to do with either of their properties.  So basically, you simplify your problem down to finding one good domain name.  Thereafter, you can use any subdomain name that you want.

With most of the good domain names taken, this may be your best option.  I’m not sure why we aren’t seeing more of this.  Given how easy it is to put up a website these days, its likely that people will start to have multiple websites and this would be a perfect strategy.  However, you may have to Think Two Products Ahead and have thought about the brand behind your properties.

I had this thought many months ago and searched for a domain name to use.  Even finding one was difficult, but I was able to do it — I’m sure you can too.  The domain name that I chose is neatoidea.com (nothing there yet), which has a sort of quirky retro feel and could be used for any of my properties.  So now I can create http://.neatoidea.com and I’m all set.

Of course, you will have to decide whether you want coordinated accounts for your properties or whether they each stand on their own, so a little planning is in order.

Here’s hoping this is a helpful, if not neato idea for you…

I read somewhere that Bill Gates retreats for a few weeks to read whitepapers and books in order to strategize for the future.  I know there are fewer Bill Gates fans out there these days, but idea has definite merit.  So as I embark on another vacation, I usually spend a couple of weeks trying to decide what readings I’m going to take along with me.  Of course, I never work through every book I take, I just want to have the variety around me just in case I stall on a book or just am in a different mood on a particular day.

So what am I taking this year?  In no particular order:

• Made to Stick by Chip and Dan Heath.
• Mavericks at Work by William C. Taylor and Polly G. LaBarre
• Wikinomics by Don Tapscott and Anthony D. Williams
• The Wisdom of Crowds by James Surowiecki
• Dreaming in Code by Scott Rosenberg

You’ll note that none of these books is technical in nature — well, you could make a case for Dreaming in Code, but its certainly a different sort of book about technology.  I get a full dose of technology during the other 50 weeks of the year.  I treat these two weeks as an opportunity to read about business strategy, marketing, innovation, or human behavior.

So why this mix of books.  Made to Stick is about the science of memorable ideas and appears to be incredibly well-written.  I am guessing I’ll power through this book and maybe even complete it on the plane.  Who among us does not need to know how to sell their ideas?  You need this skill every day, though admittedly some ideas are bigger and deserve more attention in their craftsmanship.

I have already read over half of Mavericks at Work, so this one will get finished fast as well.  I enjoy reading about creativity in the workplace.  If you’ve been in a culture where you feel somewhat suppressed, reading a book like this gives you hope and inspiration for the future.  I’m particularly enjoying the sections that talk about Southwest Airlines since they are a local company.  Their culture seems to be remarkable.

Wikinomics and The Wisdom of Crowds are two books that center are on group behavior in the online and offline worlds.  Though the perspectives are different, I’m very interested to read about each.  I’m reading these two for insight into the growing popularity for social websites.  And who knows, maybe I have an idea rolling around in my head that needs to be nourished.

And finally, Dreaming in Code.  This looks like an interesting book, though I can see myself stalling out on it as it might remind me too much of the other 50 weeks in my life.  I’m not sure when I’ll start this one, but it will get read at some point.  At any rate, I would really like to see what others’ experiences are.

Not making the trip is Release It which is a book about properly architecting systems for their life in a production environment.  You say that every system eventually goes to production, eh?  This would be true, but you’d be surprised how little thought goes into the post-development landscape.  I have read the first part of this book and many of the anecdotes are ringing very true and familiar.  But of course, as I say that, don’t think that I design crappy systems.  All I can say is that sometimes constraints beyond your control lead you down a sub-optimal path.  The trick is to minimize risks in the face of the constraints you will surely have.  Obviously, this book doesn’t make the trip because this is the life I lead outside of Think Weeks.

A few people have asked about my “hire me” site, so I thought I’d answer them here for everyone.
The first question was how did what I put together differ or distinguish me from what anyone could do with a Linkedin profile? Good question. A Linkedin profile probably will get more visits based upon Linkedin’s popularity. However, I would not be able to provide PDF and Word versions of my resume, work samples, and tinker with my SEO. At present, if you enter “Bill Eisenhauer” into Google, you’ll see a Linkedin profile under that name as the 5th choice — unfortunately, that’s not my profile.

The next question is: would you consider productizing it to enable others to have online resumes? The answer is: maybe. If I was convinced that I could find enough paying customers, I would. However, I’m not sure I could do that. I will say that it is nice to be able to point recruiters and potential employers to the site for resumes, samples, and testimonials.

Another question is: what’s up with the odd classes in some of the markup? Well, that’s microformats. I am tinkering with hResume, hReview, and hCard. You can download a Firefox extension which alerts you when microformats are present on a page and on my site you can see microformats on about half the pages. For now, I’m probably about the only one who thinks this is cool, but such is the life of an early-adopter.

Lastly, I’ve had a couple of recruiters ask about the effects found on the site (e.g. samples, about - tag cloud). That’s some Javascript and AJAX just for the heck of it. Its kinda cool to refer a recruiter to my site when they are asking if I’ve ever done any AJAX. So, not hugely useful, but mildly demonstrative of my skills.

I have surmised that my ability to code in Ruby is not of much value to the Java community. There’s just not much crossover between the two. So while I like coding in Ruby and Rails, it would appear that I won’t be paid to do so anytime soon.