Why Dont You Blog?

Normally, I would be quicker off the mark with some choice criticisms of the latest .net magazine, but now that I live on the cultural equivalent of Pluto, it takes a while for the magazine to get to me. That said, by page 10 (ironically first full page of content) there is enough to make me want to choke the lives out of the editorial team.

For background, .net is a webdesign magazine and regularly has articles about how important it is to make sure your web sites are accessible - and meet the requirements of the DDA - as well as a monthly “agony aunt” style column which gives out best practice advice. In the last two years, I don’t think a single issue has had less than two pages worth of accessibility advice. Quite rightly this advice emphasises how people should aim for broad audiences and go out of their way to not exclude one category or another.

Now, keeping that in mind, this months “Mail of the Month” is from “Ann Thulin” who describes herselve as “a woman and old” and feels that .net discriminates against her. She points out that in previous months there have been complaints about the insane choice of tiny fonts and colours which are so un-contrasting as to be almost invisible. Ms Thulin puts forward a well written rant, basically saying that as an older person, her eyes are not strong enough to read the text properly and that despite the previous excuses used by .net team (”not our fault - technical problems”, the accessibility issues are actually the result of a human making the (ill)informed choice that 6pt pale grey goes well against off-white paper. I am not old, and I am not disabled and I find it hard to read the articles sometimes - especially as the magazine team seem obsessed with geometric shapes which draw the eye away from already badly contrasted text. The layout is, from an accessibility point of view, almost criminally bad.

You would think, given the monthly obsession about accessibility, that .net would take this seriously. If this was about a website (as previous months “Access all areas” will attest), then the ranting about ensuring the content was accessible and available to all would be almost non-stop. If the .net team were reviewing a corporate website with such bad accessibility issues it would be crucified.

In reality, this is the response (in full):

Wow, that’s some indictment. It’s a little unfair to call us lazy, as we’re still looking at improving areas of low contrast n the magazine. Buy you’re right about one thing: we don’t plan to increase our font size. Our average reader is 31 years old, and it’s with this age group in mind that we design the magazine. Lastly, we’re not sure what Bill Gates has to do with the price of fish, but definitely wouldn’t change our font size for him.

Strikes me as that is a long winded way of telling Ms Thulin to “f**k off, we don’t care about you old farts.” I am amazed that any editorial staff allowed such a blatant dismissal of their readership be printed. Before I go on, the Gates reference is because Ms Thulin said that if she was Uncle Bill, she thought .net would change - I assume implying that if she was rich and male, she would have more impact on their policies. It strikes me, that despite the “witty” response, she is right here.

.net editorial team are lazy. They have had months to pick up on this accessibility issue but still haven’t bothered their arses. The think which infuriated me was the dismissive “we cater for 31 year olds” remark.  If I was Ms Thulin, I would seriously consider getting legal advice on this - it strikes me as being both discriminatory towards people for age and disability. Everything about the response is wrong. Annoyingly wrong.

For example, it implies that 31 year olds have perfect eyesight and colour perception. This is not the case by any stretch of the imagination. I very much doubt that what ever research .net carried out looked into eyesight of their readers. It is not dissimilar to saying “our average reader wears size 8 shoes so we don’t care about your problems reading the text.” They have committed the cardinal discrimination sin and made assumptions about eyesight based solely on age.

Saying the average reader is 31 is pretty meaningless as well. Is the circulation of .net amongst 31 year olds so prevalent that no other age group is important? What about all the 14 and 15 year olds who read the magazine - based against that there will be dozens of people in their 40s, 50s, and sixties or beyond. When you factor in the increased incidence of eyesight problems amongst people who work day in, day out on IT, you see that if anything, .net should be obsessive about accommodating for visual disabilities. If there were any doubt, 20% of the regular contributors and 40% of the “Ask the Experts” panel are shown wearing glasses. Do these people not count? Obviously not.

Given that there is a legal and moral obligation to accommodate people with disabilities (and not discriminate against people on the grounds of age) it is breathtaking that .net magazine feel the integrity of their layout is so important that they can ignore genuine complaints. Does the DDA not apply to web design magazines?

With this blinding disregard for their readership (disabilities or otherwise), it will amuse me no end to read their continued articles going on about how important “accessibility” is…

[tags].net, hypocrites, Accessibility, DDA, Disability, Discrimination, Disability Discrimination Act, Web Design, Magazines, Technolog[/tags]

Popularity: 34% [?]

Popularity: 34% [?]

Do they pay their article writers by the word? That is the only reason I can think for some of the worse abuse of the English language I have seen in print for quite a while.

The new layout of .net has split the old “web designer” sections and now you have technique/* sections (obviously trying to increase the web-feel for the style). These come in different forms ranging from what appears to be CSS for the retarded to “pro_tips.”

Most of these are fairly well written. The new style of the magazine appears to have improved the writing style of some of the feature writers. There is definitely a less patronising tone being used - especially in the “beginners guides.” (I will not mention the errors for now…). When they are talking about the more technical aspects, the writers do very well and actually get their point across.

However (always a however), when given the chance to “reflect” on some aspect of design (which, as opposed to the coding, is where the magazine seems firmly heading) the writers can go for three paragraphs without actually saying anything. Every other page is crammed full of meaningless prose which looks like it is there for a joke. Words like “leverage” are abused to within an inch of their lives. When ever one analogy gets used (and often a tenuous one at best), there are normally another three or four thrown in for good measure. Dont even think about letting me start on the mixed metaphors… It is truly educational reading - if only for how a “clique” magazine can butcher the English language…..

As always, as soon as “Web 2.0″ and “Agile” programming becomes the topic, no one actually knows what it means, so the writer has to make up words to fill the copy. Sentence after sentence saying the same (non-)thing.

One of my favourites:

Use abstracted code so that you can make changes quickly and easily. This almost goes without saying, but the key to developing in a flexible way is to make sure that you’re not building something that has no room for manoeuvre.

Fantastic - and that is one of the more readable ones…. The really painful ones are too much hassle to type in! When the write starts to wax lyrical about making sure all your staff take ownership of the agile development rather than viewing it as a job, you know it is going to be pure word soup.

Sadly, the Web Design “industry” is entirely to blame for all this. The seemingly constant desire for new “buzzwords” means web design has spawned a language of its own. Strangely, no one actually understands the words they throw around, so every article has to spend the first ten pages explaining what the author thinks the word means. If people would just use the language properly, instead of trying to blind people with word-bluff, this wouldnt be required. Agile is word in the English language. It has a meaning which pretty much every English speaker can work out. Using it to refer to software code is simply wrong. This is why page after page have to explain what it means.

Will the madness ever end?

Popularity: 23% [?]

Popularity: 23% [?]

Well, doesn’t time fly. It only seems like yesterday I “commented” on a new issue of .NET, yet here is another one. Last month I resisted the urge to rant on about the magazine - unfortunately I dont think I can do the same this time round. There are good and bad points, possibly one of the major good points is the fact that this month the magazine is actually inspiring enough to rant about.

Sadly, some raging lunatic at .NET has decided to go for a major overhaul of the magazine. The sections are renamed, the writing style has drastically changed (and not for the better in most cases) and the sequencing has been altered. Now, I appreciate people often reject change but this really is change for changes sake. I cant for the life of me think they consulted their customers before this re-design (I subscribe and they never asked me).

The old layout, while re-assuringly familiar, did need a change. However it needed a change for the better. It seems that at the moment, .NET has hired the crazy horse who designs Computer Arts and gone for the same look and feel. Sadly, this seriously diminishes the “uniqueness” that .NET used to have regards structure, content and style. Now the magazine looks a bit like a poor copy of an arty style magazine and, strange though this is to admit, it actually takes away from the “authority” the advice it gives carries.

Some bits of it are good - the letters are at the very start now for example. There seems to be more advertising, but I dont know if that is actually the case or an effect caused by the way every article seems to be surrounded by ads. One other positive thing - the crazy editor who oversaw all manner of bad advice, typos, misprints and other assorted lunacy is leaving now. (I can only assume she is moving to Computer Arts…).

Well, that is enough on the style - I will think about polite things to say about the articles and return to this topic.

Popularity: 23% [?]

Popularity: 23% [?]

Ok, the rants about magazines doesnt seem like it will ever go away. After a brief hiatus last month (more down to lack of time than quality of magazines) we can return to the proper ranting about how terrible they all are.

This website already has a littany of articles about specific sections of the mainstream magazines, often based on when they (mainstream mags) decide to try and cover what is still (especially in the UK) a niche product - namely Linux.

Now, given that the title of this rant is “Linux Format Magazine,” you may have already guessed which journal is about to come in for the good news… Based on our “sister site” Linux Convert, you can also guess we are fairly on-side regarding linux and feel that it really should be more mainstream. That said, it is not yet there (despite hype to the contrary), and as such needs as much support, development and promotion as possible.

Popularity: 30% [?]

Popularity: 30% [?]

Well, this is potentially a short rant - simply because this months copy of .net is pretty uninspiring. Normally each issue is a combination of random, idiotic, reporting which inflames people enough to rant about it and a massive serving of inspriation - which encourages people to jump on their PCs and try something new.

Sadly, July 2006 does not follow the normal pattern.

Often the web builder section (especially “tricks of the trade” has good, helpful, advice on how to do cool tricks which then inspire people to try them out on their own sites (even worked on Why Dont You which is why there is a Google Maps mashup at http://www.compuskills.co.uk/demo/). Sadly this month expands on the recent trends for each article to be heavily aimed at a particular peice of software (Joomla for example) so it fails to provide the same inspiration.

Overall, this was a lame issue which provided a total of about two hours reading time before it was consigned to the shelf, possibly until the end of time.

Popularity: 24% [?]

Popularity: 24% [?]

Well, as the month draws to a close a new copy of .net magazine appears. Always good for some ranting and this month carries on the traditions. I haven’t had the magazine for long so this is an “early stage” rant and that should be borne in mind. Remember, despite my misgivings about some of the crap they vomit out publish I am still a subscriber so it cant be all that bad!

Things do get off to a bad start this month though. Page 11 (first page of content) is where the hits begin. Now I am aware that as journalists the “reporters” for .net should be excused somewhat when it comes to understanding the mechanisms of surveys but even so…

Under the headline “No site, no sales” they have a three column article about how recent “research” shows 85% of people polled would have doubts about buying from a company that didn’t have a website. It goes on to produce dire proclamations backed up with “hard figures” (for example: “67% of small businesses believe it would take ten times longer to create a site than the average” - what does that even mean???) and finishes with the amazing proclamation that “a shop should sell stuff, a club should have membership info and a hotel should have online booking.” Fantastic.

Now the problem with this: The survey was comissioned by 1&1 and surveyed 1848 people. The number of people is acceptable but very low to make a comparison nationally. The big warning sign is the fact the survey was comissioned by a web host which sells online site creators and small business tools. Without going into this too much, from what I can gather the survey was carried out online which increases the disparity.

It seems a reasonable assumption that people confident enough about the web to take part in these sort of online surveys (lightspeed is a good example) would also have a higher threshold for requiring a shop to have an online presence. If I carried out this survey in the local villages where I live, I very much doubt if 10% of people would expect a shop to have a website before they would buy. You dont go online to check out your local newsagent before you buy the paper for example.

The article appears to imply that for small businesses to succeed they need a website. This, while good for business, is not really true. Most small businesses are aimed at selling goods to the local community, and in this situation the website is pointless. No one goes on line to check if the shop 200m away has a website before they buy. I agree that any business wishing to trade on a larger scale should have a website, but even then it is hard to think that 85% of their customers require one.

Ask yourself, when was the last time you saw an offline advert for a company and checked to see if they had a website before you bought. I have never done it. I have checked websites of online companies (eBuyer for a recent example), but they are online so of course they have a website.

To add scorn to their shoddy standards, in the sidebar of the article they “Name and shame” three sites which have “dismal” websites. Apparently SiteMorse looked at the websites for the FTSE100 companies and graded them. As always, Tesco.com gets slated - “zero for functionality” - yet even in the article it says they get hundreds of thousands of online customers. Oddly, the disparity of this escapes the .net journalists.

Instead of slating the site - visions of over paid designers sitting around in berets tutting about the site spring to mind - surely this implies the industry needs to overhaul its “testing” procedures (if there are any… I suspect it is just on a whim). Saying “bad design costs customers” seems true and is logically sound - however then saying the top online sellers have bad design lessens the point drastically. Tescos has an excellent website which hoards of people use for online shopping. I have used it and like it. I find it very functional and easy to use. What are the testers criteria if this real world example of a success is graded a failure?

Can anyone tell me?

Popularity: 28% [?]

Popularity: 28% [?]