In fact, when I started the site in 2004, there was no such thing as the Google Maps API. And I’ve given many mapping talks where I go a little bit grandpa on the audience, telling them how hard it was to translate addresses to latitude and longitude points (geocode) in those days.

The WifiPDX of 2005-2011 was showing its age, both technically and visually. In late 2008 I started working on a new version, but writing a mapping book got in the way of creating a mapping site. Finally, last August I decided to pick up the project again.

When I look at the progression of the site, I’m really happy with the updates. But, working in fits and starts over the last few months, I had a much longer list of things to do. These weren’t even major features, just ways to polish what’s there. Then I realized I needed to listen to my own advice and release early rather than release ready.

Some of the non-technical updates I particularly want to point out:

• Every hotspot page can be edited by anyone–WifiPDX is a sorta-Wiki
• The home page is mapified, complete with closest WiFi searching
• The closest WiFi feature tries to guess your location
• The WiFi map can show both neighborhoods and types of places

There’s plenty more going on, but those are the big ones. I could also do plenty more to it–and perhaps I will. But for now it’s nice to be at a state of completion on my first side project in two years.

It’s called unrut and I think it’s a good example of a version one product. I included only basic functionality–there’s a lot of room for improvement. But instead of spinning my wheels as I attempted to finish a marathon list of features, I kept things simple. Users can search for places and then mark them as visited. What remains is a nice little organized list of places to try.

Using only cookies, the site remembers what you’ve marked as visited. So, if a place comes up in a subsequent search, you won’t have to mark it visited again. Would it make more sense to include user accounts, so that the site would work no matter what computer you are on? Yes. However, I trimmed this from the feature list for two reasons:

1. It is not a necessary feature in order to get feedback from people on the concept
2. Every site should let you sample, registration optional, so the cookie functionality will remain even after I include user accounts

And how about incorporating location-sharing sites to automatically determine where you’ve been? Yep, that’s a good idea. But creating a first version is about pointing your ship in the right direction, not necessarily sailing it all the way to your destination. Use the two simplicity paths to figure out the core and just launch that. You can always add stuff later.

Since posting a message about it on my Twitter feed this morning, I received good feedback. Some people asked for the things I already knew I needed. Others have said things that didn’t occur to me. That’s the power of getting a side project out there.

We all have side projects and I’ve written about many of mine on this site. I’d love to hear about your side project. And if you want help getting it done in six weeks, let me coach you.

There is something else I see often–side projects that don’t get finished and languish in a half-complete state. Or worse, they become trapped as unexecuted ideas. It’s nobody’s fault. Life takes over, priorities are forcibly skewed. Side projects, which are often passions, hit the back burner.

That makes me sad. And I’d like to help change it by starting my own side project as a side project coach.

This is part of my continuing campaign to help others create on the web. I’ve written tutorials, a book and over 100 articles on Programmable Web. These are passive methods. While rewarding, they don’t provide much connection with those I am helping. Side project coaching, working one on one, will help me work toward my goal much more actively.

It’s a new year and it seems like a perfect time to pounce on those cobwebbed projects. If you have a side project, resolve to finish it in six weeks. If you know someone I can help, send them my way.

What follows are the lessons I’ve learned so far getting to the first complete draft.

Write Every Day

The most common writer’s maxim turns out to be true. Writing every day makes it a habit. Once writing became part of my routine, I ensured that I could take advantage of a powerful force: the large accomplishments that come from the compound effects of daily progress.

I was also greatly helped by continuing other writing. My productivity spiked once I had daily posts to log with Programmable Web. The outcome was contrary to my initial thinking, but daily accountability helped cement my routine. Plus, blogging works the writer’s sprinter muscles. I was able to write more, faster.

Don’t Quit Your Day Job

My original schedule had me finished with the book by May. Like most estimates, it was overly optimistic. But I had yet to learn an important lesson about my brain. It wouldn’t let me write for more than three hours per day, maximum.

Truthfully, some of my most productive writing days were over within 90 minutes. Writing a book is both a marathon and a sprint. It requires a series of short bursts of energy over a long period of time. The best part is that when my writing was done for the day, there was time for other projects. And whatever part of my brain controlled writing wasn’t used in programming or event organizing.

I wish I’d realized writing did not require a full day sooner, because I could have been easier on myself. If I write another book, I’ll do it alongside other projects. You do not need to clear your schedule or quit your job to write a book. To start, you don’t even need a publisher (remember, that’s not the hard part). Just write it.

Make Time For What’s Important

You can accomplish any large task if you consistently make small amounts of time for it. In The War of Art, Steven Pressfield described the things that keep you from forward progress:

“The secret that real writers know that wannabe writers don’t, and the secret is this: It’s not the writing part that’s hard. What’s hard is sitting down to write. What keeps us from sitting down is Resistance.”

I read Pressfield’s book, on my friend Kareem’s recommendation, in the middle of my writing process. Because many examples involve Pressfield’s life as a writer, it resonated on that level. It also reminded me of side projects that gather dust un-launched. We all have them. I believe writing a book is an excellent practice and can give you the encouragement to execute any idea.

My friend Tom recently begged readers to stop talking and start doing. “Just decide what you want to do and work your ass off doing it,” he says. It’s easy advice to give, but it’s even easier to ignore.

It turns out that writing a book–or finishing whatever project you have–isn’t hard to do. Just follow this simple list: 1. Start working on it. 2. Keep working until it’s done. If it really is important to you, the continued effort will be well worth it.

Now when you search for hotspots, you’re automatically taken to your list of nearby locations if you have one of the following:

• Firefox 3+ with Geode add-on
• Google Gears
• Firefox 3.5
• iPhone OS 3.0

I explained iPhone geolocation in a post on my book blog.

The book’s focus is creating web maps and location-based applications. I’ll be covering several mapping APIs in a cookbook style that will allow even non-programmers to be able to embed interactive maps into their web pages.

I’m excited to have the opportunity and thrilled to be published by No Starch Press, who do the Wicked Cool series, among other great technical books.

Looking back, this topic makes a lot of sense for me. For years I worked with location data at BestPlaces. In 2004 I started my Portland hotspot finder. I had to roll my own geocoder, because this was nearly a year before Google Maps was released.

When I started writing for Webmonkey again, I wrote up tutorials on mapping APIs. I covered WhereCamp Portland. I wrote up other location-based services and libraries. So, bringing my experience to a book seems natural.

There’s a lot of hard work ahead, but I’ve found the writer’s groove and am well on my way. If you’d like to follow my progress, I’m writing at the book’s blog.

Check out my 2008 Web Innovators year in review to see what this group I co-founded has been up to.

I want to help others create on the Web. There are designers with great skills who want to learn to program. And there are bright business owners who can’t execute on their ideas. I believe anyone can learn to program. I’m looking forward to proving that.

Right now you can see my first steps at Webmonkey. I’ve written for the site since 2000, but now I’m joining as a contributor on the Monkeybites blog and writing about a tutorial per week.

The move from BestPlaces is tough. I believe in the aim of the site and the people behind it. In fact, I’ll be helping them out a bit here and there.

I’m excited about my next steps and look forward to hearing your ideas. Many thanks to those who’ve already given me such wonderful advice. I hope to receive more of it soon.

Sticky note pic by striatic

For those who don’t know the backstory, Webmonkey was mothballed almost two years ago. Before that, it was revived from a previous death. This time looks for real because Wired owns the site and did some work to re-architect it.

What makes me happiest about Webmonkey’s return is that it received a lot of attention before launch this time. The site, now mostly a Wiki, looks like it belongs in 2008. Readers can rate articles, comment, and edit them when they get out-dated. Major props to Mike Calore and his team for their effort to bring the ‘monkey back in such a big way.

Since 2000, I’m proud to have been a Webmonkey author. Over the last couple months, I’ve been writing a few more how-tos that will make their way online in the next few weeks. I’m proud to be part of it again. Welcome back, Webmonkey!

The site takes a city name or zip code as input and spits back a score, based on 100 being normal. For example, Portland is 107.2, mild drought.

DroughtScore is a microsite, which I’ve in the past called
one trick ponies. I mean it as a compliment. By focusing on a single purpose, it helps communicate only what is important to the user. With DroughtScore, I hope we found the sticky substance.

Try it out with your town.