All You Should Read

Open Source Development Times

So I’ve pretty much given up on developing an ASP CMS, simply because ASP is severely lacking in certain options (Yes, I could use ASP.Net, but where do I find the time to study that crap?)

The most important reason for me to develop something like this was work - to generate something our Morale Committee and HR could use to issue communications - and our server uses IIS and MSSQL.

Screw it. I’m the administrator of the box, and I installed Apache and PHP… and thankfully, there’s an MSSQL port available for PHP. Saves me a lot of hassle.

But it looks like I still have to develop the CMS, myself, as the one CMS that looks promising has been waiting for a PHP/MSSQL port for over two years, with no solution in sight.

Shame.

This is the first of a series regarding the abuse of what otherwise would be an at least somewhat enjoyable medium (the interwebs, duh). Each part will address an often-made mistake, and go into detail about why certain things should be avoided like the plague.

We’ll start with perhaps the most evil of ‘em all:

THE BLINK TAG

Never include page elements that move incessantly. Moving images have an overpowering effect on the human peripheral vision. A web page should not emulate Times Square in New York City in its constant attack on the human senses: give your user some peace and quiet to actually read the text!

Of course, <BLINK> is simply evil. Enough said.

Jacob Nielsen, 1996

MySpace. Fundie sites (both the religious and political varieties). Knock-off product sites. What do they all have in common?

An incessant assault on the optic nerves, by means of animated GIFs, flash banners… and the <blink> tag.

An often asked question on Yahoo! Answers is about “how to make text blink”. Sadly, there’s always some ignorant dimwit that, instead of rightly berating the questioner, answers the question.

Read the rest of this entry »

Done.

Finally. Only took me a week.

Let me know if I missed a beat or have my facts all crookeded and incorrective, and such. Thanks.

First episode (contains links to all five parts) can be found here.

Working on an extended tutorial, the beginnings of which can be admired here:

http://tutorials.allyoushouldknow.com/web/startawebsite_one/

It’s still in progress, so don’t be surprised of links that lead nowhere yet.

I could not possibly say it any better than a guy named Doug Vanderweide, right here: Stupid Web Site Tricks.

There are times when I just want to reach through my monitor, and grab some ignoramus by his or her collar and just… shake them, all the while simply yelling NO! NO! NOOOOOOOOOO!!!!! at the top of my lungs, and in their face.

Yes, the design of my main pages is a straight copy of a ready-made WordPress template, mea culpa. I started working on my own CMS, but life (as it does) got in the way so I abandoned that idea for now. Anything outside the realm of the read subdomain, though, is hand-written and hand-coded and hand-designed.

And I’m not using any fancy stuff to detract from what I have to say.

Mister Vanderweide, sir - I tip my hat to you.