I personally think that helping web developers to produce sites that are friendly to what Google is trying to do is good for all parties including customers.
It is good for Google because:
It is good for web developers because:
It is good for customers because
Google states in its company overview that its goal is to ‘organize the world’s information and make it universally accessible and useful.’ My theory is that for that really to happen you have to tell people submitting the information how information is being organised. Once both sides are transparent (it will not work otherwise) it becomes a case of letting user choice and the information do the work. Of course the process will be dynamic and both sides will need to adapt over time but simply speaking transparency is key.
Google Sitemaps is a good step forward to get away from the cat and mouse game that has been going on between web developers and Google. I hope too that in the strategic corridors at Google HQ they are coming round to the idea that transparency is good for business. It would make everyone’s lives a lot easier.
Have an update or suggestion for this article? You can edit it here and send me a pull request.
Linux and Unix watch command tutorial with examples
Tutorial on using watch, a UNIX and Linux command for executing a program periodically and showing a fullscreen output. Examples of watching a file download, a network interface come up, and showing the five most CPU intensive processes.
Build your own Vim statusline
Statuslines in Vim are not hard to create. Making your own means one less dependency in your life.
Custom Vim Bindings in tmux 2.4
tmux 2.4 made a significant change to key bindings. Here is how to support custom keybindings for versions before and after tmux 2.4