To be a hack or, just perpetrate one
Or, how to save the world one website at a time…
Last week while jotting down notes, talking with a client about redeveloping his photography site I lose conversational focus for a minute and look out my office window. It’s an atypical, bright blue Florida spring morning outside while inside, I’m still on the phone, trying to explain in understandable lo-tech terms why we/I felt obligated to burn down his pre-web2.0 website and build a beautiful thing in its place for free and then… I catch myself drifting off, again…Driving a cab would be fun, there’s the tips and travel and new faces… Umph!, sorry…
Good sites gone bad…
Back on the phone with the client, I rattled off a half dozen reasons why his three year old site needed to sleep the long sleep. Beyond just the pragmatics of never being as easy for him to use/update and maintain, it had recently started to occasionally break stuff which is not a good sign. I thought about, and then chose not to mention that -our- underlying motivation behind the site makeover, was to bring his project up to our standards *(which would probably sound like we’d -not- built the original to standards) which was wrong but, easier to accept than explaining the whole “internet infancy, bleeding edge technology, things change pretty quickly analogies”.
