Five For Friday

Months ago, Rick Mahn asked me to list 5 things I was thankful for. Friday seems like an appropriate day to respond:

  1. Red Stag‘s Mac & Cheese for lunch.
  2. Re-arranging my office making both a cozy reading corner and a usable coffee-making corner. (Finally)
  3. Ruby.1
  4. You.
  5. Checking one more thing off the To-Do list calendar.

1. There’s a longer post in here about being productive in 2 hours. Ruby is the second language I’ve written in (the first was RealBasic, years ago) where I can solve a problem and start a new problem in the course of just 2 hours. Add a few well structured Google searches and the number of solved problems increases dramatically. Happiness.

My Cable Access Prediction Coming True

“A provision of a law passed by the [California] Legislature in 2006, which took effect Thursday, allows cable television providers the option of dropping their long-standing obligation of providing free studios, equipment and training to the public.” – Reed Johnson , LA Times

Three years ago, I wrote: “Add Cable Public Access to the Endangered Species List”

Personally, I’ve been a cable-free household for at least 5 years – and community access programming isn’t broadcast over the air (a much bigger issue – from my perspective). Thankfully, there are ways to receive my community-created media without purchasing a $100/mn Triple Play package….I can just load up MNstories or any number of reading lists in Cullect.

It feels ironic that as cable companies shed their obligations to support community access, the relevance and proliferation of community media is increasing. While the inverse is true of cable.

What Have You Deployed Today?

Some of you have been around web design long enough to remember the 4Ds (Discover, Plan, Design/Develop, and Deploy) that were so popular in agency marketing materials in the late 90s.

At the time, I once asked my CEO about them (he wrote the marketing copy)

“Well, we don’t do them on all the projects. Clients actually only care about the last one.”

Um.

So, the rest are for showing how unfamiliar with the client’s domain we are?

A while back, Jason Fried recounted those days:

“In 3 weeks we managed to tell them exactly what they already knew while also burning through 15% of the budget.”

blah.

He continues in the comments

“…you don’t really know if something is right until you do the real thing.” – Jason Fried

On my internal projects (the ones that lead to interesting clients), here’s my process

  1. Sketch out the primary screen on a 3×5 notecard.
  2. Draw out the database schema (I understand more about an app via its DB schema than a wireframe or UI).
  3. Build the smallest functioning app possible.
  4. Deploy. Public or not, deploying makes it real.
  5. Build the app better.
  6. Repeat 4-5 indefinitely.

Related:
Eating your own dog food

“We starting doing release cycles that were only a few hours apart, re-releasing every time we fixed a significant problem. ” – Andy Hertzfeld on making the original Macintosh OS.

“So. We all know we should ship early, ship often. That small, achievable goals are the best. That having something useful and publishable within a day or two or three trumps planning everything perfectly to the nth degree.” – Amy Hoy