97 Things Every Programmer Should Know

(Chris Devlin) #1

Collective Wisdom from the Experts 81


If your program is GUI based, then I want to do something simple and see
a result. Wizards don’t help, because they do stuff that I don’t understand.
Chances are, I want to read a file or write one. I don’t want to create projects,
import directories, or tell you my email address. If all is working, on to the
tutorial.


If your software is a library, then I carry on reading your web page looking for
a quick start guide. I want the equivalent of “Hello world” in a five-line no-
brainer with exactly the output described by your website. No big XML files
or templates to fill out, just a single script. Remember, I have also downloaded
your rival’s framework. You know, the one who always claims to be so much
better than yours in the forums? If all is working, on to the tutorial.


There is a tutorial, isn’t there? One that talks to me in language I can understand?


And if the tutorial mentions my problem, I’ll cheer up. Now that I’m reading
about the things I can do, it starts to get interesting, fun even. I’ll lean back
and sip my tea—did I mention I was from the UK?—and I’ll play with your
examples and learn to use your creation. If it solves my problem, I’ll send you
a thank-you email. I’ll send you bug reports when it crashes, and suggestions
for features, too. I’ll even tell all my friends how your software is the best, even
though I never did try your rival’s. And all because you took such care over my
first tentative steps.


How could I ever have doubted you?

Free download pdf