jemjabella

Your Tutorials Aren't Helping

The success of rev.iew.me's launch has opened my eyes to a multitude of websites I never knew existed. Unfortunately, it has also made me realise that the age of the dodgy tutorial is not over, and now more than ever younger webmasters are "educating" each other with terrible code for the sake of scraping in a few extra visitors.

If you have a tutorial section, you could be one of many hundreds of people negatively affecting the websites of those who don't know any better!

How do I know if my tutorials are bad?

Open up your tutorials page, look for "Basic HTML". Is it there? Does it contain instructions on how to code "<b>" and "<u>", using <textarea>s to display the code? Your tutorials are bad.

Now look for "Changing font colour", or "Changing text colour" tutorials. Are you recommending the <font> tag — a tag that was deprecated in HTML 4.01 no less — or the color attribute? Your tutorials are bad.

Do you have a section for JavaScript tutorials, all of which are formed using code from Dynamic Drive, and you don't really have a clue how it works? Your tutorials are bad.

If you have a tutorial on "Bulleted lists" that tells people to use <li> without an <ol> or <ul>; if you have a "CSS beginner's guide" that doesn't explain the different between a selector, property and value; if you have a PHP includes tutorial but don't know the difference between include(), include_once(), require() and require_once(): your tutorials are bad!

How do I fix them?

Unless you plan on spending precious time learning about deprecated tags, semantics, why you shouldn't use presentational tags, and the value of validation and optimised code, there is only one answer: get rid of your bad tutorials. Delete them, remove them, eradicate them. They offer no meaningful value! They're useless to your visitors, Google doesn't care enough about your site to rank you higher than real tutorial sites, and you're only damaging other people's chances at learning proper code by keeping them. Stick to a subject on which you clearly know best, preferably one that isn't HTML or PHP.

CAPTCHAs

A CAPTCHA is “a type of challenge-response test used in computing to determine whether or not the user is human” (source). More specifically this little rant is aimed at the variety of images containing letters and/or numbers which may be distorted, placed on a background or otherwise messed with to supposedly prevent non-humans from getting past a certain point. I hate them.

You may think it odd that someone who has two public scripts both with CAPTCHA capability should hate them, but it is true. I only implemented the bloody things into my scripts because it was what ‘the people’ wanted.

Generally, I can see the point of CAPTCHAs. They do help to reduce spam at some sites, but at what cost? If I, a fully able human being with perfect eyesight and a decent browser, have problems seeing captchas or getting the letter combinations right, what hope do those with poor eyesight or other reading/visual disabilities? Must they be relegated to a silent corner, never allowed to join a website or post a comment again, for fear of angering the giant CAPTCHA making machine monster thingy?

I wish that people would think before inserting CAPTCHAs on parts of their website that simply do not need it (for there are other tools which can help prevent spam which do not require visual confirmation). I also wish that people would clearly mark where CAPTCHAs are being used so as not to catch people out — if you’re going to put a captcha on your weblog, put it on the page with the rest of the comment form. By placing it on a confirmation page, it is very likely that I’m going to have browsed away in a separate tab and closed the page assuming that my comment has gone through without even looking.

Simply put: before adding a CAPTCHA, make sure you have exhausted all other options. For my sake (think of my blood pressure), for the sake of your poor-sighted victims and those with reading difficulties. Remember, if spammers can get past Hotmail and Yahoo’s complex CAPTCHAs, there’s no way in Hell that your freebie WordPress plugin is going to stop them in the long run. You’ll be the one losing out in the end.