Also, it’ll be great to be a “listener guest” on your show! I couldn’t do it before sue to being away in Belfast at the times JV suggested. I did reply to JV and tried to engage him in email-chat but alas I’ve not heard back!! Check your emails JV!

😛

.biz? Hmmm, how about .noway ?

The “launch list” was pretty strange. I can’t believe it would really target startup entrepreneurs. Especially the suggestions to write detailed specs. In my day job for a financial company that makes sense and even then you have to find a balance between reasonable minimum requirements and specs on one hand and speed of delivery of apps providing the right functionality to the business.
But for a startup? For my off the clock work on myskillsmap.com I created rendering and took some good notes on the process and design but I would have never used the same type of lifecycle.

Also remember that your target audience are developers (think command line) so are less picky than if your site was aimed towards designers, then this design would be a whole different story.

I’ll talk to Justin about the possibility of using WP ajax comment plugin or maybe it might be worth using something like Disqus. Have you tried any of the other comment systems.

Seriously though, .biz is associated with scam brands and products, so for many it’s a bad first impression.

You’d have to disinfect your brand from the .biz associated stink.

.biz is a horrible TLD. I’d never use anything other than .com unless it’s a domain hack. Non .com domains seem unprofessional and amateur.

Our Node Knockout team used Polymaps to build Killnode. We ended up having to use image tiles for the maps because iOS can’t handle the SVG maps.

If you’re working on your own or with one person it’s not a big deal to skip the specs. But if you work with a team or build something that will need to be maintained by someone else in the futures you really need good specs and tests. I maintain a few large projects that were written by other people and have no documentation. It’s a nightmare to make updates, even after working with the code for a few years now. If I had clear documentation it would be easy to figure out what needs to change instead of having to track through many different files and DB tables.

Yet to listen to the podcast, saving it for the trip into work in the morning, its always a pleasure to hear you guys.

After all my bitching about how ugly our old theme was, I think Justin decided it was worth the time to try to find and tweak a new one than to listen to anymore of my complaining. While it’s a long way from awesome, it’s definitely a step in the right direction.