I do miss all the crew at Vizioncore. There are just too many awesome people there. Happy new year and best wishes mate.

I’ve noticed that you’ve been video blogging as well as writing recently – you’re not the only one, and it’s also not just restricted to IT blogs – it’s everywhere! Some of my favourite bloggers now do many video posts (e.g. http://www.fourhourworkweek.com/blog/). I love the content, but just find I watch videos less than I read text. Especially in a public environment or an office. RSS feeds can be set up to syndicate the entire content (e.g. with FeedBurner), and I prefer that setup as well. Having to click through to a website can be a pain.

Yes, I have noticed the added summaries you’ve been doing on the Networkers videos over the VMworld ones. Please don’t forget us that prefer to read over watching .

Thanks for the comment,
JK.

My annoyance is RSS feeds that only send a snippet and force you to visit the site to read the whole thing.

But you make a good point my friend. Use video when it adds value. I use it for events, where you want to show the VIBE through imagery and audio.

I have also been pondering that a good textual summary of video key elements is really important, you should not have to go through a few minutes to see if you are interested in something.

Great post, be patient while a few of use video bloggers work it out. If I look at my video blogs from VMworld to Networkers there is a huge difference. Lets see what improvements can be made for vForum.

Rodos

Great point. I agree with you there. There are cases where writing it yourself can be cheaper and easier to use. You do still need to keep in mind ongoing support – hopefully it would be easy enough for someone else to pick up and run with when you leave.

Thanks for the comment!

#5 – When it is cost-effective to do so.

Take your German bloke you referenced in your previous post. He said that he could use cron and rsync, plus a little bit of magic with the .vmx file, to replicate VMs. Whilst he might have been impressed with the additional functions of vReplicator, if he only had two ESX hosts and a few VMs, then he mightn’t really be that interested in vCenter awareness or pretty reports.

This might be a bad example as vReplicator is hardly an expensive package, but the principle applies to other things too. If you can do a job yourself, and have it perform the functions you require it to perform, for less than the cost of going out and buying a comparable package, then writing your own makes sense. The same principle also applies to ease of use and suitability; if, by using your own custom software, you or your staff can do a job quicker and more efficiently, then – again – it makes sense to invest the time and effort in custom-writing something.

Just a thought…

Predicting the next big thing is always hard – predicting the next little thing should be easier.

Thanks for the comment dude .

If we could all predict the next big thing, we could be on a beach. See you there!

Great post!

Rodos