Categories
Writing

Grammar God

Recovered from the Wayback Machine.

Today it got close to 80 degrees (it’s still 70, at 9pm at night), and this is only the beginning of April. So many plants blooming that the air is perpetually perfumed.

I took the grammar test. I hate to break it to the neighborhood but…

You are a GRAMMAR GOD!

If your mission in life is not already to
preserve the English tongue, it should be.
Congratulations and thank you!

How grammatically sound are you?
brought to you by Quizilla

Me smart. Me talk good. Me rite gould, two.

Categories
Writing

Apps behaving badly

I have had a strong writer’s block this last month, which has manifested itself as writing to the weblog. As contrary as this seems, what this means is that instead of focusing on the writing I need to do to make a living, I’ve been puttering around here. Unless ya’ll decide to chip in and pay me a salary, I must be more disciplined with my time.

Luckily, reviewing the O’Reilly books helped me get a better understanding of both my audience and the writing style I want to follow, something I’ve been having some trouble with recently. They’ve also confirmed my impression that there is a good audience for books on technical topics that are not directed at geeks.

Clay Shirky’s new essay has also confirmed my preferred audience. He uses the term situation software to describe the quickly built, purposed, not meant to scale applications that power most small organizations Internet (and not) software needs. One aspect of this, and a growing aspect at that, is that programming is seen more as a secondary skill, rather than the primary skill:

So with programming; though all the attention is going to outsourcing, there’s also a lot of downsourcing going on, the movement of programming from a job description to a more widely practiced skill. If by programmer we mean “people who write code” instead of “people who are paid to write code”, the number of programmers is going to go up, way up, by 2015, even though many of the people using perl and JavaScript and Flash don’t think of themselves as programmers

In my opinion, this started in the days when professionals were scarce and we could command big bucks. Tools allowing smaller organizations to do their own development suddenly started to get more popular, and as they became more accessible, more and more people thought to themselves, “Hey! I can do this!”

Though the programmer-as-secondary-skill market has been around for some time, it has been powered primarily by Visual Basic, ASP, Java Applets, and Access in the past. Now, though, we’re seeing strong movement towards Flash/ActionScript, PHP, and MySQL, especially MySQL. On this database Clay writes:

You can of course build these kind of features in other ways, but MySQL makes the job much easier, so much easier in fact that after MySQL, it becomes a different kind of job. There are complicated technical arguments for and against using MySQL vs. other databases, but none of those arguments matter anymore. For whatever reason, MySQL seems to be a core tool for this particular crop of new applications.

I agree.

As for scripting, the use of JavaScript continues to be popular, but sites aren’t building in the dependency on it they used to. There is much less use of DHTML, but I think that’s due to the influence of Flash. Unfortunately both have been and are still used improperly at times, which I’ll demonstrate later.

Returning to Clay’s situated software, one challenge with these niche or communal applications, especially those created by non-traditional programmers, is that they they don’t always take advantage of existing components to do some functions that overlap between applications. The reason is either because they have someone who wants to ‘try it out’ themselves (and though that’s comendable, I’d rather incorporate code that’s been tested by hundreds of users), or they don’t know about the concepts of reusable components, and that these types of scripts exist.

The main reason I recommend PHP for most web sites is that there are thousands of pre-built and thoroughly tested open source PHP components (or codelets if you prefer) on the Internet just free for the download. Not only that but there are forms generators and various other tools that do three-quarters of whatever you need doing for a site–including interface with MySQL.

There is no need to code a mail handler application, or hand write a form that uploads data to a MySQL database. You don’t have to create your own user management system, or worry about how to upload photos. The only problem you might have is choosing among all the variations of any of these codelets that are online.

(To find, Google on “PHP scripts” and be prepared to be overwhelmed.)

In addition to not making use of existing code, inexperienced web site developers can also get caught up in the ‘cool stuff’, and make some serious mistakes in fundamental site design. A demonstration of how this can happen can be found in the web sites for the two library systems I use to get all my books and movies.

The first site is for the St. Louis Public Library. It’s not particularly polished looking, or pretty; however, it works, and it works rather well. Key elements in the design of this site are: good clean use of web forms for catalog searching; easy to read results pages from the searches; a front page that directs new users directly to the information they’re most likely to want; and good navigation between the site pages. The page that covers all the branches is based on a graphic, but the library also lists all of the branches below using plain hypertext links.

The only point I have to pick on the site is that they don’t have a direct link to a person’s account from the main page. You have to go into Catalog to find the link to “My Account”. What this does is make a person more apt to bookmark the Catalog page than the Main page and doing so they’re not as likely to see new events the library is promoting (which could be more prominantly displayed, themselves). Main pages aren’t just for newbies–they should have something for everyone.

(Under no circumstances should a main page have a Flash demonstration that has a “skip this” button to click. Not unless the site is selling Flash. )

The other library system I use is the St. Louis County Library, which looks more polished than the city library system, but right on the first page, it has a major strike against it: a Java applet based navigational menu.

Never, ever, under any circumstances, whatsoever, do you use anything other than a hypertext link to handle site navigation. You do not use DHTML. You do not use Flash. You do not use JavaScript in anyway. You do not use Java Applets. Slap, slap, slap! Bad!

(I once wrote a tutorial on this, writing that site developers should never make the navigation hard to find or use, forcing the reader to wave their mouse over the page like a magic wand, hoping to uncover an actual working link. To prove the point, I coded the tutorial to use graphical buttons for navigation, but when the person’s mouse was over the button, I would use DHTML to move it before they could click on it. They’d have to chase the navigation buttons around the page and hope they could click it faster than the DHTML could move it. It was fun.)

Chances are with the County library, you probably don’t even see the Applet menu (it doesn’t work with most of my browsers), and the site does provide a text-based menu, but that just forces a person to have to go to another page immediately. This doesn’t even mention the havoc that a bad Applet or DHTML menu can have on the many different browsers that people use. As for accessibility issues–forget it.

If you must have a pretty, pretty for your navigation, incorporate it as a secondary page. Or use CSS and set the hover value to change the hypertext link font.

The site also has some other errors, including the hated “You should be using…” specific browser notices. I used these once a long time ago before slapping myself upside the head, reminding myself that I want people to visit, not go away until they’re properly equipped.

Other than these issues, the County library’s main page does have nice features, including prominant mention of special events, and highlighting services the institution wants people notice. As for the secondary pages, the library does have some very fancy search engines, as well as other interesting tools. The search results are very comprehensive, including providing thumbnails of the book (or other object), and availability at each branch. It also provides one click requesting of the item, which I frequently use. Additionally, you can filter results based on age or year of publication or any of a number of factors–something you don’t think about until you have it and then you go, ‘Wow. This is handy.”

It is a feature like this, handy but not essental that can make niche or community software, or Clay’s situated software, grow and grow unless scope is set and ruthlessly enforced. In fact, the two major factors that lead to escalating costs on any software project, big or small, are analysis paralysis (trying to meet all needs for all people for all time), and scope creep (“Ooo. That’s nice. But can we make it also do this and this and this…”)

Categories
Writing

Unbelievable

Recovered from the Wayback Machine.

Today it got close to 80 degrees (it’s still 70, at 9pm at night), and this is only the beginning of April. So many plants blooming that the air is perpetually perfumed.

I took the grammar test. I hate to break it to the neighborhood but…

You are a GRAMMAR GOD!

If your mission in life is not already to
preserve the English tongue, it should be.
Congratulations and thank you!

How grammatically sound are you?
brought to you by Quizilla

Me smart. Me talk good. Me rite gould, two.

See purty flower. Purty flower is good smelling.

area449.jpg

Categories
Books

Extreme O’Reilly

Last of the O’Reilly book review, and I’m going to cover three different brands: the traditional ‘animal’ books, the Missing Manual series, and the Head First series.

The RELAX NG book from the animal series is what you’d expect for one of these books. It is a comprehensive coverage of the topic, with relevant examples, lots of text, and few graphics. Animal books get to the point and are, for the most part, geared to the geeks – or the geek at heart.

This isn’t to say that the coverage of the topic is cryptic or difficult to follow, or dry. After all, I’ve written a few animal books myself and I hope my books don’t fit that description. But they aren’t fluffy books, and make little use of graphics as an aid to understanding. The aid in these books tends to be the examples.

The Head First series is completely the opposite, and about as far as you can get from the animal books. There is still comprehensive coverage of the material, but how it’s covered is completely different. If the animal books are text, the Head First books rely on graphics. A great deal of graphics.

I’ve looked at both members of the series, Head First Java and Head First EJB, and my initial reaction to the Java book, was lukewarm. Part of that can be that I’m used to more traditional computer books to learn a programming language; part of it could be that, like many people, I prefer learning programming languages by example.

The Head First into EJB book, though was different. EJB – Enterprise Java Beans – is a framework and a set of related behaviors, and the graphic nature of the book captured this very nicely. In fact, it was the first time I’ve ever enjoyed reading a book on EJBs. I didn’t think it was possible to be entertained by a book on EJBs, but this book did.

(I think what won me over was the two page behind the EJB scenes graphics on pages 8 and 9. Any book that make me laugh about EJB is some kind of miracle.)

It could be me, but I see a Head First book being better suited toa framework than a programming language; the former is hard to get your head around sometimes, but the latter is easily broken into sample code and with some text to explain what’s happening, you get what’s going on without having to rely on the pictures.

However, if you’re a heavily visual person, you’re going to like this series.

missing.gifThe last book is the Mac OS X Missing Manual (Panther Edition), and this book fits about right in the middle between the animal books and the Head First series, in the ratio between use of graphics and text.

These purpose of this series is to provide more comprehensive information about a specific product than usually comes with the manuals (if any manuals are even provided). Visually, the Missing Manual makes more use of graphics and graphical breaks in the text than the animal series, but far, far less use of graphics than the Head First series. This makes for a book that’s less intense than the animal books, and more comfortable to read, especially if you don’t see yourself as particularly ‘geek like’. Additionally, it is more business like than the Head First series, though again, that doesn’t mean that the writing is dull or uninteresting – it’s just not quite as otherwordly.

I found the Mac OS X one to be very helpful, and I discovered all sorts of new and intersting things about the Mac OS X environment that I hadn’t taken the time, previously, to learn. And since Mac OS X manuals are not what one would call particularly helpful, I can definitely recommend this book for new or intermediate Mac OS X users.

Now the question: Would I write a book in these series

Well, I have written books in the animal series, and would do so again. However, my emphasis lately has been directed more to the non-geeks than the geeks, and that’s not necessarily a good fit for an animal book.

I would not do a Head First book. I wouldn’t know how to do a Head First book. Having to incorporate all those graphics in and around the text, and having to find the appropriate graphics – it would drive me nuts. It would take a special person to do a Head First book.

I would be comfortable doing a Missing Manual style of book. It fits the direction I’m going, which is more towards the interested or engaged or adventurous person rather than intensely directed towards the geek.

You know: someone who drinks lattes rather than Mountain Dew.

Categories
Photography Writing

Walker Evans: I am a writer

I am not a Walker Evans expert, but from my recent readings about him, I sensed there were three significant events in his life that shaped the man, and subsequently, the photographs we’ve come to cherish.

One of the events I briefly mentioned in the last Walker Evans writing, and that was his search for a particular style of photography. Rejecting the existing photographic styles of the time– which either disregarded the strengths of the camera in favor of artificially created scenes, or sought to tug emotion from the viewer–Evans sat in a library looking through all 50 issues of a the photographic journal, Camera Work until finding what he was looking for: Paul Strand’s photograph of a blind woman, shown below.

strand_blind.jpg

In this picture, Evans saw an uncompromising realism unfettered by any emotional hooks. There was no attempt to make the woman into something either to be admired or pitied; nor was there an attempt to make a ‘pretty’ picture, or a noble one. Combined, this realism and lack of emotionality formed the basis for Evans’ own style of photography: unsentimental, realistic, and unstaged. In other words: objective.

A search for objective truth in art wasn’t unique to Evans–many of the creative people of that time shared this philosophy about their work. But objectivity was almost an obsession with Evans, and we can trace the roots of this to his upbringing and the second pivotal event in his life: the separation of his parents when he was in his teens.

Evans came from a relatively affluent family, and his father was a prominent marketing and advertising man, a profession Evans was later to term one of the bastard professions. His mother was from a wealthy family, and liked nothing more than to be a figure in society.

Evans had an relatively happy childhood until they moved from his home near Chicago to Ohio, when his father got a new job. It was in Ohio that his father began an affair and subsequently left his mother. Evans, already lonely from the loss of his childhood friends was left confused and unsure, and the previously outgoing boy began to draw inwards, away from his contentious family.

His mother, whose world was drastically upset, begin to live vicariously through her children, determined that they were going to have happy, prosperous lives (with her a central part in each). She was, in many ways, an outwardly sentimental woman, but at the same time, she was not demonstrative or terribly affectionate.

Within the Evans family, before and after the separation, sentiment was both an artificial promise and a means to an end. Through his father, Evans saw sentiment used as a tool to lure people into buying a product or service: after all, what better way to build a successful advertising campaign then to incorporate images of cute babies, small puppies, and happy American families. From his mother, Evans perceived sentiment woven into a complex fabric consisting partially of denied security and affection, a great deal of manipulative guilt, and even some frustrated sexuality.

Though it’s not as fashionable to lay praise for a person on their early childhood experiences, it’s difficult to deny the impact Evans’ parent’s separation, and their behavior both before and after, had on his search for both objectivity, and anonymity, in his work.

walker1.jpg

To get a better understanding of Evans’ objectivity, compare his photographs of sharecroppers during the Great Depression with those of another very famous photographer of the time: Margaret Bourke-White.

A month before James Agee and Walker Evans took off on their trip that would result in the book, Now Let Us Praise Famous Men, Bourke-White took off for similar reasons with the well known writer, Erksine Caldwell.

Margaret Bourke-White was not a person who waited for a photograph to happen. Whenever they arrived at a potential scene, she would direct the people, telling them not only where to stand but what type of emotion to display on their faces. From Belinda Rathbone’s biography of Walker Evans:

White relied on Caldwell to guide her to the people she wanted to photograph, but once there she went to work “like a motion picture director”, remembered Caldwell, telling people where to sit, where to stand, and waiting for a look of worry or despair to cross their faces. Under her direction, passive, weather-beaten, and cross-eyed sharecroppers were turned into characters in a play, playing themselves.

Bourke-White even went so far as to arrange objects in a scene, for which she was scolded by her co-author (and husband), Caldwell. Unusual behavior considering the following quote:

I feel that utter truth is essential,” Bourke-White said of her work, “and to get that truth may take a lot of searching and long hours

peddler.jpg

Bourke-White would enter churches during services and start taking pictures, once going so far as to climb in through a window one time when she found the door locked during a service.

Evans, on the other hand, was reluctant to intrude. Rather than ask to enter a church, he would take photos of the outside. He wouldn’t touch any objects within a scene, and when taking pictures of people, he would allow them to pose themselves, or he would wait to take the picture until their initial stiffness from being in front of the camera wore off.

More importantly, he refused to make the people into objects of pity, which, after all, would imply sentimentality. If Bourke-White’s photos inspired one to want to change the fate of the people, Evans inspired no such humanitarian impulses. One never feels guilt, when looking at an Evans’ photo. Or pity, or humor, or desire. All one feels is interest, admiration, sometimes astonishment…and a little envy, but that doesn’t arise from the subject.

walker2.jpg

So what was the third event that was so significant in Evans life? Well, in actuality it was a non-event.

When Evans was a young man, he convinced his family to send him to Paris to study the language and literature. At that time, photography was only a hobby for him, he wanted to be a writer. And there was no better time for an aspiring writer to be in Paris, with the likes Ernest Hemingway, T. S. Eliot, Dorothy Parker, Ezra Pound, and someone whom Evans admired above all others, James Joyce, living there.

Evans would hang out at the book shop where Joyce would appear every day, watching other young men and women seek Joyce’s company, to shake his hand and try to engage him in conversation–an impossible task with the monosyllabic Joyce. The shop owner offered an introduction between Evans and Joyce, but Evans shied away from his chance to meet his hero, something that he’d talk about for many years into the future.

When Evans returned to New York at the end of the year, photography gradually overcame his interest in writing, inspired in part, I believe, by James Joyce. After all, what could Evans write that had not been written by others such as Joyce? And how could he shine in a field as luminous as this? All those who write experience these moments of doubt when we read another’s writing that is so brilliant that we are left feeling humbled and inadequate. Humility, not to mention being second, third, or even tenth best, is not something that Evans would have lived with, comfortably.

But the camera, the camera now, that was fresh territory. And with the camera he could grab his quick sketches of life, in pictures rather than words. Whatever interest he had in writing, could not sustained with his growing passion for photography.

Evans would later say:

Oh yes, I was a passionate photographer, and for a while somewhat guiltily, because I thought that this is a substitute for something else—well for writing, for one thing. But I got very engaged and I was compulsive about it too. It was a real drive. Particularly when the lighting was right. You couldn’t keep me in.

I can agree with Evans, that photography can quickly become a substitute for writing. One image can so easily convey information that may take thousands of words to do, and less eloquently.

A few weeks ago, when I started digging more deeply into Walker Evans’ life, I was asked by a magazine to provide a portfolio of photos, including any better quality digital ones. I asked Charles, a photographer who has worked with magazines in the past to give me advice on printing the photos, which he was very generous to provide. He also shared with me anecdotal stories about photography students preparing their portfolios, each professionally printed and bound

But I looked at my little digital images, all of them at 72 DPI, and my slides, and my nice, but not great inkjet printer and asked myself, “What the hell are you doing, Shelley?” just about the same time I read, …I was a passionate photographer, and for a while somewhat guiltily, because I thought that this is a substitute for something else—well for writing, for one thing….

And it is thankfully, and with relief that I gave up the nonsense about being a stock photographer for magazines, or an art photographer, or any kind of professional photographer, and return to what I love: writing. Because I am a writer.