We’re using jekyll on some projects at work, so I thought that I would try it out on my laptop. I found the Jekyll Quick-start guide, and it seems pretty straightforward:
The problem, of course, is that it doesn’t work:
Apparently, Jekyll wants you to install this as root. Or, perhaps, the writer is running on a different system that permits regular users to install new software without privileges. Or something else: who knows? The fact of the matter is, these simple “quick start” instructions are a complete and utter failure. At this point, I have two options:
- I can walk away, knowing that if I try to fix this, I’m going to dive into a multi-hour, multi-day fiasco of repetitive trial-and-error.
- I can try to fix it and hope for the best. And probably dive into a multi-hour, multi-day fiasco of repetitive trial-and-error.
You who develop software: is this what you want?
I use this as a simple, most recent example, but it happens all the time. People who write Java code assume that every single human being on the face of the earth has a Java development environment set up exactly like theirs. Folks who code in Python assume that you have the exact same Python version and installed libraries as they do.
Here’s a hint: before you release any documentation, ever, spin up a new, clean standard server using a common operating system like Ubuntu or Microsoft Windows. Run your code examples there. If they don’t work for you then, they won’t work for anyone else using it.
Moreover, if they do actually work, they still probably won’t work for a bunch of users.
Document your dependencies: if the writer of Jekyll’s quick start guide had added a footnote with his or her assumptions about operating system, environment, and dependencies, then I would at least have had some idea that there might be problems.
An old rule of thumb is “Under-promise and over-deliver.” Documentation like this takes the exact opposite approach, and it pisses users off.