Paul Dix Explains Nothing

On the mundane act of writing about programming

Zed's post about his RubyFringe presentation and Reg Braithwaite's post about his retirement from Ruby and blogging carry a similar message: be subversive. Don't do something ordinary and boring. While I agree with part of the message, I have to disagree with the idea that blogging about ordinary programming isn't subversive.

Taken by itself, a post about FakeWeb for mocking web requests isn't subversive or game changing. But when millions of programmers create posts about seemingly ordinary and mundane topics, things get interesting. Pair that with a decent search engine and a good community site and you're putting O'Reilly out of business.

Now that's subversive.

Not only that, you're spreading free knowledge. You're enabling countless newbies to become a bad ass programmers without having to spend thousands on college.

That's game changing.

Links to Nerd Stuff

I swear I haven't forgotten about this blog!  I've just been busy and haven't bothered to write anything.  Since I've been ignoring you I'll just toss up some links to things that have been distracting me lately.

First, have a look at my latest Codesnipers post on AJAX/DHTML widgets and Rails.  This is something that will be occupying my time and thought for a little while.  If all goes according to plan I'll be posting some detailed how-tos about creating and/or using different kinds of DHTML widgets in Rails.

I linked all of these in the Codesnipers post, but I'll do it again in case you didn't feel like reading.  Go check out the AJAXy Outlook/Exchange killer Zimbra if you haven't already.  It's slick and I'd like to use their AjaxTK, but it doesn't seem suited for my needs.  I may be playing around with that over the next couple of weeks.  Also check out Dojo and their Rich Text Widget.  It's choice!  I really like their model of declaring widgets with additional HTML attributes.  Finally check out qooxdoo.  It looks like something you'd use to develop a thin client application in the browser.  I may be playing around with any one of those three over the coming weeks.  All open source goodness!

Now for a few random things.  Check out the Liquid Template Engine for Rails.  I haven't had a chance to play with it yet, but it's on my list.

I've been toying with the idea of using a hosted virtual private server for my Rails development adventures.  That way I can share out demos of code I'm slinging.  I'm wondering if it's well suited for my needs.  Here's a provider I found that is pretty well priced.

If you want to keep up on the random things that I have in my list to get around to checking out/reading keep an eye on my delicious.

Another Scam

I just received an interesting phone call.  It came from 866-656-8182.  The guy on the other end of the line had a thick Indian accent and there was a bunch of telemarketing office noise in the background.  He informed me that he was calling to send out $450 worth of free movie tickets as part of an anti-piracy effort by the movie studios.  He just wanted to confirm my information.  He then listed what he thought was my street address (but was actually the old one) and asked me to confirm.  I asked "what's the catch?  what do you want from me?".  He then informed me that he'd just need to collect $5.95 and verify some information to ensure shipment of the movie tickets.
I told him I'd pass and promptly hung up without giving him so much as my name (much less a street address or any kind of billing info).  This is obviously bogus.  I wonder what kind of information he was going to request of me.  $5.95 doesn't seem like enough to make the scam very profitable so there must be some other angle.  A quick Google of the number brings up this thread.  Seems a number of different stories are coming from these guys.  I guess you have to keep your guard up 24/7.

Bomb, Schmomb...

I've noticed in the past month or so that people are starting to get scared that we're entering a new tech bubble named Web 2.0.  Everything has been heating up in the past couple of weeks with the Web 2.0 conference along with a number of buyouts (and more, and more) .  Kevin Burton stated as much yesterday in "Dot Bomb All Over Again?".  I guess I understand how VCs and day-traders would be afraid of another dot bomb, but for the rest of us it should be a party!  Let's look at some of the good things the last one brought.

At the start of the first bubble (~95-98 depending on your PoV) broadband was scarce (or nonexistent), information was largely inaccessible, and and stuff was hard to find.  At the end of it all we had much better and faster infrastructure, a heaping truckload of information to sift through, and some decent ways to get at it.  The bubble was great for people (like me) who were just getting started professionally and had the chance to work on some interesting stuff.

If we are indeed going into another bubble, what can we expect out of it this time?  Some of the things I think will be good:  More bandwidth!  Much much more bandwidth!  More information with more ways to organize it!  Accessible instantly (within reason) from anywhere and on demand!

I'm guessing the bad stuff will probably be similar to before.  Stupid ideas with absolutely no revenue.  VCs dropping gobs of cash on the previously mentioned ideas and loosing their asses.  Day-traders loosing their asses.  People loosing their jobs in the fallout.

Want to avoid it?  Don't day-trade, don't fund anything, don't try to start anything and keep your cushy government job.  I really don't understand the fear behind all this.  I'm excited!  I think it'll be fun!  Since I don't plan on day-trading, I'm not a VC, and I don't have a cushy government job (nor would I want one), I have nothing to worry about!  I plan on starting something, but what's the worst that can happen?  I spend too much time working on nerdy stuff and it isn't a success?  Hell, I've been spending my time working on nerdy stuff for years, dot-bomb or not.

My advice to everyone who's afraid we're pulling into another bomb is this:  Don't worry so much.  Just sit back and enjoy the ride.

Where Are The NYC Hackfests?

Against my better judgement, this weekend I actively sought out more blogs to add to my list of feeds.  In my travels I find this post about SuperHappyDevHouse IV.  I'm obviously not in the know since this is the fourth event and it's my first time hearing about it.  Combine that with BarCamp and I'm noticing a pattern.  The devs in the bay area get to have all the fun hackfests!  Where in the hell are all the fun NYC hackfests?  Do we just lack the space to put one on?  Are they going on as I write this but I'm just too clueless to know about it?  I'm tired of those bay area hackers doing all the cool nerdy stuff.
This be my east coast vs. west coast nerd challenge, yo!  We east coast nerds gotta represent!  For real kid!
But really, where are the east coast hackfests?

Technical books need this

Creating Passionate Users has an interesting post titled Conversational writing kicks formal writing's ass.  Sounds about right to me.  Yesterday I mentioned my initial thoughts about the book Agile Web Development with Rails.  I stated simply that I liked the writing style.  I think it's because so far this book seems to have that conversational style that Kathy Sierra was talking about.

BCP, DRP, and Usability for Airlines

This may be mostly a rant since it's inspired by a recent flying experience gone bad I had with Delta.  What follows are some observations on how Delta and probably any other airline can benefit from better BCP (Business Continuity Planning), DRP (Disaster Recovery Planning), and Usability Testing.
The Situation:
On Sunday I was all set to fly from Portland back home to NYC with a connection in Atlanta.  My flight from Portland was to leave at 12:48 PM Pacific and arrive at 8:05 PM Eastern in Atlanta.  My Atlanta flight was to depart at 10:00 PM Eastern and get me into NYC just after midnight.  Everyone boarded the plane and everything was progressing normally until we got out to the runway.  We sat there for a little while until the pilot came over the radio and informed us that the plane was broken, probably due to a starter malfunction.  We taxied back to the gate and were informed that they were asking other airlines if they happened to have the part on hand which could get us underway in about an hour.  We waited for a little while until the captain came over the radio delivering more bad news.  The part was unavailable in Portland so we'd have to wait for it to be flown up from LA getting us out of Portland around 5 PM and completely blowing my connection.  Everyone was deplaned and that's where Delta's process fell apart.
Upon deplaning, everyone immediately got into line to speak with the gate agents.  The agents were not prepared for this volume and the line really didn't move.  After 30 minutes of waiting in line they started informing us over the gate PA system that there was no use waiting in line since all flights out of Portland were booked.  Everyone continued to wait in line anyway.  After about an hour and  a half of waiting they announced that the plane had been fixed by a part from another airline and we were ready go.  They started boarding the plane again.  Once the plane was about 80% boarded they announced that they were mistaken and the plane was in fact still broken.  We would now have to wait for that part from LA which would now take even longer so we wouldn't depart until just after 7 PM.
Everyone immediately jumped back into line to see if there were other flights to be taken or any other information to be gained.   Of course there was nothing to be done and everyone waited until it was time to board the plane again.  During that time we found out that Delta was now flying a completely different plane up from Cincinatti to take us into Atlanta.  We boarded the plane and flew off to Atlanta with a promise that people with connections had all been booked on the earliest flight out and that we would have hotels to stay in.
Upon arriving in Atlanta at 3 AM Eastern the pilot informed us that we were at the gate right next to the terminal.  We were also told that agents would be waiting at the gate to give us hotel vouchers and answer any questions like "where the hell is my luggage going to be?"  After getting off the plane we were redirected to the agents back at the terminal.  We also found the gate was on the wrong end of the concourse.  We then had to walk the entire length of the concourse, walk to the terminal since it was so late the train wasn't running, and then walk the entire length of the terminal since the agents were on the opposite end.  We then proceeded to wait in line again to get our vouchers and ask any questions.
Well we stayed in the hotel and caught a morning flight to LaGuardia.  We arrived weary and thoroughly pissed at Delta.  What went wrong and how could this be improved?
My Analysis:
I understand that you can't predict when a mechanical failure will occur, but what you can do is set how you will deal with such a problem.  Another thing is that mechanical failures are as certain as death and taxes, so plan accordingly.  Enter BCP and DRP.
My first problem was with the gate service in Portland after deplaning.  Why was everyone in line?  Atlanta is a very large hub for Delta so I'd say about 75% of the people flying had connections.  Everyone needed to know if they'd make their connection and if not, what could be done.  The same can be applied to the second time waiting in line.  Both of these scenarios could have been anticipated and planned for.  Here’s a simple idea to streamline the process.  When you check into a Delta flight at the terminal you may notice that they have a bank of phones next to the check in counter.  If you pick one of those up it immediately connects you with someone who can change or check reservations.  Why not put a bank of those near the gates as well?  That way your angry deplaned customers can take advantage of the speed of your call center as opposed to overwhelming your gate agents.
Note: If this should happen to you, pick up your cell phone and call the reservation desk yourself while in line.  You'll probably be helped much quicker than by the gate agents.
My second problem was with our treatment on arriving in Atlanta.  Why were we told that we were at the closest gate to the terminal when that was in fact not true?  Why were we told that agents just outside the gate would help us when that was in fact not true?  Misinforming tired pissed off customers who have to stay overnight in Atlanta is no way to improve their mood.  Again we have things that can be anticipated and planned for.  None of the other gates had planes at them so put us at the closest gate possible.  The Delta ticket counters run the entire length of the terminal so put the agents at the counters closest to where your passengers will be coming from.  I call this my Usability Testing for airlines.  Make that walk at 3 AM after a six hour delay and you’ll quickly realize what needs to be changed.  This is a variation on paving the cowpath.
My third problem was with waiting in line to get travel vouchers, information about morning flights and how to reconnect with our luggage.  It's 3 AM and we're in no mood to wait in line.  Get us to the hotel as quickly as possible so we can sleep.  We were just on your plane for 4 hours and 15 minutes!  You had a captive audience!  During that time the flight crew could have talked to every passenger to answer questions and hand out hotel vouchers to those that needed them.

Somehow I find that whenever something like this happens, the airline is completely unprepared.  The situation is almost always handled in an amateurish fashion and as though it were the first time an unplanned event has occurred.  This is a surprise to me since I would think that airlines would be the foremost experts on BCP and DRP.  Maybe I’m just a little too critical.  At least they were able to get us put up in hotels and on flights the next day…

Frat-tastic!

For your reading pleasure:  Meet the Brads.  Sound like someone living at 1600 Pennsylvania Avenue?

Update: I forgot to give David St. Lawrence his due so here it is.  I found the link through this post where he talks a little bit about the author of Meet the Brads.

JoS Forums Down!

I just tried to visit the Joel on Software forums and they're down!  I'm sure it will be fixed by the time anyone reads this post but it does bring up an interesting subject.  Here's what I saw when I tried to go to the forums:

The FogBugz database is down or could not be found.

For security reasons, this cannot be fixed over the web.

Please edit the registry on the FogBugz server. The setting you want is HKEY_LOCAL_MACHINE\SOFTWARE\Fog Creek Software\FogBugz\c:/Program Files/FogBugz/discuss.joelonsoftware.com/website\sConnectionString.   
Common connection strings can be found at connectionstrings.com.  (Also please note that if your SQL machine is on a different server than your web server, you may have to use SQL Server Authentication, and not Integrated Authentication.)

To use SQL Server, set this to Provider=sqloledb;Data Source=server;Initial Catalog=database;Integrated Security=SSPI; for Integrated Authentication
or Provider=sqloledb;Data Source=server;Initial Catalog=database;User Id=sqlserveruser;Password=sqlserverpassword; for SQL Server Authentication

To use Access, set this to Provider=Microsoft.Jet.OLEDB.4.0;Data Source=filename

Or, you can always use an ODBC data source name, which you establish using the Data Sources (ODBC) control panel.

Error: -2147467259: Unspecified error

Now that's a bunch of information.  However, is it appropriate for an outside user like myself to see such an error?  I'm a fan of good error messages, but a regular user has no idea what to do with this.  I think that there should be a separation of standard user error messages and debug error messages that give someone troubleshooting the problem more to go on.

Something to read

Well I've been slacking off on this here blog thingie.  I've been too damn busy at work but, there is some light at the end of the tunnel.  Since I'm too busy to write stuff, I'll just link to a few things that are fun or interesting.
A blog I just found that is pretty well written:
http://bigpicturesmalloffice.blogs.com/
And just in case you haven't seen this one yet:
http://www.overheardinnewyork.com/

That's it for now.  Hopefully I'll have time to write a real post this weekend...