June 4th, 2007

Podcast episode 2

Recorded Friday evening. We discuss the IP migrations, ARIN, IPv6, Xen 3.1, office ramblings, design contest and more.

Direct download

Subscribe to the podcast feed

iTunes link

Posted by matt Filed in podcast

7 Comments

  1. March 17th, 2008 at 10:00 PM Lex Neva

    Wow, I feel famous! Especially with the deterioration of unixshell.com’s Xen hosting service, I’m really itching to move my VPS over to you guys. I’m keeping my eye on your blog and my ears on the podcast, and as soon as you get enough IPs to start selling extras, I’m so there.

  2. March 17th, 2008 at 10:00 PM Anton Dubina

    Is it just me or there’s something wrong with audio? Music in the very beginning plays in stereo, but when you guys start to talk I can hear you only in the left audio channel.

  3. March 17th, 2008 at 10:00 PM jason

    Should be fixed now.

  4. March 17th, 2008 at 10:00 PM Chad

    It would be cool to have RSS on the tumblelog.

  5. March 17th, 2008 at 10:00 PM matt

    http://tumblelog.slicehost.com/rss

  6. March 17th, 2008 at 10:00 PM Chad Skeeters

    I know a good designer that could help with the design, but after thinking about it, I realized I need to tell you that I like the way the site is designed now.

    The current design says “We spend time working on things that meet your needs.” it’s easy for anyone to understand right from the get go what you offer, how much it costs, what level up support you provide and why your offering is better than others.

    A lot of businesses have a site that says “We provide ambiguous services and hire diverse people (see stock photography). Please contact sales.” See verizon business page.

    http://www.verizonmarketing.com/bsg/?product=DATA&promo_id=998

    Viewing that page is a waste of my time. Maybe the messages are all the ignorant high level managers look for when viewing a website, but like your company because it’s obvious that you focus on details that matter and use logic to make business decisions and aren’t afraid to make those decisions on technical details when it’s called for.

    I think if you’re going to redesign the site you should consider the following limitations:
    • No flash – unless there is no text in it, but ideally none. It’s difficult for the user to copy text they may need out of it and it’s more expensive to maintain.
    • No information overload – Sites that have too much information on one page are just frustrating to use. Don’t fill up a 3 column layout with bs text just so it looks balanced.
    • No DHTML that slows down navigation. I don’t care if the Tree JavaScript plugin is free. In general anything that wastes the time of the user or increases maintenance time is bad. Most people’s web 2.0 sites are frustrating to use if not already broken due to browser updates. DHTML is hard.

    If you are going to redesign the site, and want the community to contribute, I’d recommend check the site into Mercurial, git, or bazaar and then have people submit the url to their online repository or their zipped repositories instead of their final designs. The site could be stripped of backend before it goes into this repository if complexity or intellectual property was an issue.

    This would produce the following benefits.

    • It would allow multiple groups of people the ability to post slicehost repositories on their site and pull from other people’s designs so that the maximum amount of sharing (merging) is taking place to produce the best result. Anyone using this method would have to start from a common base to be able to share changes with others.
    • Allow SliceHost to see each commit that was made and that will help you integrate changes quickly.
    • Introduce people to distributed version control.

    http://blog.mwolson.org/tech/why_i_dislike_subversion.html

    http://www.youtube.com/watch?v=4XpnKHJAok8

  7. March 17th, 2008 at 10:00 PM slicematt

    Thanks Chad – great thoughts.

Leave a Reply