Category Archives: documentation

One of the arts of any craft is learning how to deal with colleagues. And part of this is learning the give-and-take nature of relationships. I love the passion that comes from advocating a position strongly held. It’s good not … Continue reading →

In jazz, there’s a common method to get from one place in a progression to another. It’s called the two-five device (really it’s ii-V, but I want to convey that that it’s pronounced “two-five”). In music theory, the five chord wants … Continue reading →

In the spirit of wabi-sabi, I’m thinking about using “ba-dee-ya” as a placeholder for my unfinished content. I have some deadlines that I won’t make and, rather than commenting out entire sections of text, I think I’ll include what I … Continue reading →

As a writer working in the software field, I often hear a lot of ideas that aren’t expressed very well. Well, they’re expressed in specifications or in code. They’re just not expressed in actual communication that someone who doesn’t read … Continue reading →

This week I started my new gig at Cloudera. I’m quite excited about the opportunity. Although, I already miss my colleagues and friends at Eucalyptus. It’s a big change for me. For the first time in seven years, I won’t … Continue reading →

I love Amazon. I used to work there for years. Most of their documentation is really good. However, I found the following help for downloading Kindle for Mac to be . . . well . . . please refer to … Continue reading →

Well, it looks like I’ll be an employee of Hewlett Packard soon. HP bought the company I work for, Eucalyptus. We’ll be joining the cloud org. I find change a bit more difficult as I age. However, I still have … Continue reading →

I’m a few days out from the Write the Docs conference. Once again, the conference planners did an amazing job. I’d like to blog more about it, but I’m under a deadline. I have 17 days to finish about eight … Continue reading →

After 16 years using XML, I’ve been tempted to switch to Sphinx. My new colleague at Eucalyptus, Kushal Das (http://kushaldas.in/) , has asked me to think about switching our DITA content to reStructuredText (reST). I tried Sphinx last year at … Continue reading →