I assume this means linking to it on your site. But if your server goes down, your users won't be able to get to it anyways, unless they have your blog address memorized or bookmarked.
Your site should never be allowed to go down for long, unless something major happens, in which case a backup plan is ideal. I would host my own blog, and if my server does go down, redirect the domain to a stable site with a brief explanation of what's going on, and then when every thing's back to normal post about it in the company blog.
I would just keep the blog somewhere like wordpress because they will have a more fully functional blogging engine. Don't spend your time managing your blog software, spend it making your product better.
Would you disagree that plenty of smart developers create and plenty of good developers reuse?
Maybe a more encompassing way of stating the saw would be "while a good developer can create what is required, a smart developer will use what is provided"
Use what's available when you can, as it will save you time and money. Make what is not available already.
Wordpress is so easy to setup that it's probably taking me longer to write this comment than it would be for him to setup Wordpress.
Not to mention, with the large user base it has, you can get things like plugins and themes to customize your site without doing a lot of work. Plus, the template system is easy enough that writing your own custom theme should be a piece of cake.
Throw together a template to match your company website if you want.
For a great example, read http://blogs.smugmug.com/don/ (one of my favorite blogs in terms of technical and personal communication)
I'm going to roll my own semi-blog that will be a bit different style.
With comments by disqus, almost any home brewed site can act like a blog.
Extensibility of other platforms means little to me, as the more interesting features I'd need to implement myself.
The only problem I've with blogger is their template system, I simply don't like it.