I use WordPress. I use it a lot. I use it for most of my personal sites, business sites, I hack around with it and contort things to do what I need them to do. I’m not, however, one of those WordPress fanatics. In fact, you will hear me say a lot of nice things about Drupal, for example, even in public and even when talking to WordPress fans. I believe in using the right tool for the right job and in this case you can consider platforms of choice to be no different from any tool. One way I use WordPress is for something that nobody ever gets to really see (unless you visit my office and I happen to show you how I manage and control things): managing my vast number of systems, laptops, devices, and most of all the growing deployment of virtual machines. I used to keep track of network port diagrams via Microsoft Visio but since I am not using Windows as much these days and also don’t want to go back to keeping ASCII notes or document files I decided to put together a more proprietary and automated way to keep track of IP addresses, services provided systems and VM’s, passwords, installation and deployment notes, hardware notes, driver information, etc. And for that I decided to go with WordPress.
The result is that I am finding it very annoying and painful on the eyes. But not so much the color schemes using a dark background themselves, but rather the practical implications when using it while doing actual work. The dark background allows for better highlighting of code, no doubt about that, but in a practical situation I often have other applications running on the screens which include things like help files, CHM’s and PDF’s with developer documentation and API docs, Outlook, OneNote, Visio, and many other development tools, etc. and almost all of these applications will use a light or white background as a basis.