XML sitemaps are a default for Web development at this point, yet I’m amazed about how many sitemaps are done improperly because developers use sitemap generators which either return partial or inaccurate coding. For the longest time we used http://www.xml-sitemaps.com/ and repeatedly ran into formatting issues with Google Webmaster Tools.

After trying a slew of various editors I think we’ve found a winner. XMLEcho isn’t the quickest option in the World but it certainly produces clean and accurate sitemaps. Creating an account is simple and quick, plus the service gives you the option to create sitemaps of unlimited size… best of all, it’s free!

Nice job XMLEcho!

Tonight Jason Fried from 37signals spoke at the Oriental Theater in east Denver. He discussed everything from client deliverables to the 37signals four-day workweek. In essence, Jason’s talk boiled down to three key points:

1. Don’t work on hard problems. Break them down and keep things simple.
2. Avoid distractions (open office environments, meetings, e-mail, etc.) get a site or product out of your head and into production ASAP.
3. Deliverables are bullshit, clients don’t care, the end product is what matters.

First off, I want to say I have great respect for 37signals and their impact on the industry. Having the chance to talk with Jason about issues such as: stopping IE6 support, disregarding Photoshop in the design process, and scaling with growth, was an absolute treat. Clearly the team at 37signals is one of the most innovative and talented in the industry.

However, I think 37signals dominance in the web products field has distorted their ability to critique the client-based approach. And while I don’t have knowledge to speculate specifically on day to day client interaction, I do have a few things to offer from a developer perspective.

Team chemistry is important.

First, people working from home all the time can be harmful to the group chemistry. Jason and team do a huge amount of work via telecommuting. Relying on campfire, screen sharing, and video chat interactions for the bulk of their communication. They feel this helps minimize distractions and keep people productive.

I’m not sold this is the way to go. I think it’s hard to truly feel connected and dedicated to your team if you don’t spend real time with them. When’s the last time you became really good friends with someone without spending some serious face-to-face time with them? For me it’s never happened, not once. And as great as chatting online is, it’s not the same as being in the same room and hashing things out. You miss the subtle face gestures, the inside jokes, the bantering, and the all around comradery that happens in the workplace. Part of the reason Imulus does great work is because we have dedication to one another. Even on days when I’m completely out of wack mentally I still find myself focused on helping the team. Why? Because I’m relied on to help create the great stuff we build. And I trust those I work with to do the same. As ridiculous as our office gets sometimes in the end we get shit done and we do it for each other and ourselves.

Deliverables have a purpose, it just needs to be refined sometimes.

Second, I don’t buy that all deliverables are bullshit. Just as some companies like to skip Photoshop (37signals) and go straight to coding, and others (Apple) like to make mockups pixel perfect it’s impossible to say that one solution is better than the other. Yet, we can agree that certain processes work better for certain people as well as certain projects.

Let’s talk about the way we work. Imulus’ basic approach is to offer the client a timeline, design brief, wire frame, and mockup of the final interface. Now, it’s important to realize that we haven’t always done it this way. In fact, for some time before I came to Imulus the wireframe process was basically nixed. What was the result? Instead of 5 hours spent reworking things in the wire frame process, 25 hours was spent reworking things in the development process. Look, we aren’t naïve, we recognize that clients change their mind and get new ideas all the time. However, we’ve found that most of this re-thinking takes place in the wire frame stage. And therefore we save hours of coding changes by altering the approach up front. In essence, if you’re building a car and the frame is faulty, why wait until the upholstery’s getting put on the seats to fix it?

Still, we know it’s a strong possibility that some of our deliverables are blown out of proportion. And as most firms do we will continue to collaborate and narrow down our inefficiencies. However, we have found that some deliverables are an extremely important step, and just because some projects or companies don’t require them doesn’t mean they aren’t important.

In conclusion

Clearly 37signals has clout and track record to support the way they work. And regardless of how that alters the Imulus process we love hearing about it. It’s phenomenal that they have so much passion behind what they do. I hope over time we can refine our own process to the point they have. Until then it’s great hearing a second opinion about things.

Over the past few weeks we’ve had our lead developer here at Imulus on vacation in Mexico. Initially there was some concern around the office that with him gone his day to day tasks would be a major time sink for the rest of us.

However, as the past few weeks have gone by I’ve come to the conclusion that missing a big piece of the puzzle every now and then is more of a positive than a negative. Not that we don’t want John to come back, or that we won’t be faster as a team once he returns. But more that the best way to force people to learn is to throw them into the water and make them swim. I.E. having John out may make us slower in the interim, but in the long run it will make us faster because each developer will be even more capable than before.

This trial by fire attitude is what makes people better all around, and consequently worth more in the long run.

So here’s my advice: if you’re used to having someone around that can help you get through tasks or problems stop asking them for help once in a while. Sacrifice some time, lose a few hours to the problem, and have faith that learning it on your own will be worth it in the long run. Both for your self value and the company’s. Having a tutor is great, and having a cohesive team is even better. But realizing the value in self growth is essential. It makes the process faster and less distracting for everyone in the end.

Just when I was starting to knock Google’s track record of innovation they roll out GrandCentral. While it isn’t truly a Google “innovation” what they will be doing with it sure is innovative. I’m not a user of it - yet, but it sounds like an awesome idea and I’m very excited about getting into the application.

If you never heard of GrandCentral, it’s a phone aggregator…. in a nutshell it will allow all your phones and voicemails to be managed under 1 account.

Here are just a few of the features I’m excited about:

• One number, rings everything
• Let people call you from a Web pageClick2call from your keyboard
• Call Record. Yep… record your calls… this will be fun to see the lawyers debate
• Voicemail notifications via SMS
• Mobile Access, similar to the iPhone visual voicemail

I can just hear the telecos whining about this latest invention by Google. But why are they doing this, I’m only guessing at this point but let’s follow the money for some clues.

• Phone based ads using AdWords
• Click to Call, perfect for tracking AdWords conversions over the phone
• Planting the seeds for the Google Phone
• Searchable Voicemail

OK, I’ve drank the juice and I haven’t even used this yet. I encourage you to visit the site and sign-up as well.

Today I tried Microsoft Visual Web Developer Express as a change to Visual Studio, hoping that it had less bloat and would be a good alternative or upgrade from previous Visual Studio IDEs, even as an Express version.

This was the popup it presented to me when I opened my first site.

What the f*ck!

I respect that Microsoft wants to promote version 3.5 of the framework but this is f*cking stupid, and arguably irresponsible, too.