Objects sent towards an event horizon never appear to cross it from the sending observer's point of view and anything that passes through the horizon from the observer's side appears to freeze in place.
As web technology moves ahead, from a web developers point of view, everything appears to freeze in place. As computers become more powerful, web browsers confirm to web standards, and development frameworks standardize programming techniques, we find that we are still responsible for catering to 800x600 resolutions and dial-up connection speeds.
800x600?
Okay, not 800x600, but we're still coding for the lowest common denominator, while trying to throw in every bell and whistle to make the web 2.0
Here are a few points to consider if you are developing a website or website content aimed at a worldwide audience:
Non-Intrusive Javascript. Keep in mind that not everyone has javascript enabled. This could be a security restriction, or an old browser. Make sure that your site will still function without the cool rollovers and hover menus
Flash. It should be obvious that not every browser has a Flash plugin installed. If they don't, how are you delivering your content? Are you coding the same information twice? Once in Flash, and once in HTML?
1024x768. I think it is fair to consider this a standard resolution now. Make sure that you don't design a site that doesn't fit into this resolution. Also consider what your site might look like on an iPhone or Netbook.
These points might seem obvious to many developers, so how about using the best of these technologies:
Javascript framework. If you are going to use a framework, like jQuery, only use jQuery. Don't combine every javascript framework you can find and utilise a feature from each. There are many plugins or extensions to most popular frameworks. Stick to one, learn how to use it and extend it and save yourself a debugging headache when you try to figure out why something strange happens in IE when everything works fine in Firefox
CSS framework. For any type of framework, you should become familiar with it's best qualities, but don't rely on it as a magic wand. You can sometimes start fighting against the framework if you have a change to make and don't understand how the original framework was intended to work.
CSS Reset. Sometimes good and exact when developing a site to be absolutely cross browser compatible, but it doesn't eliminate every bug while developing. Sometimes it introduces a whole lot more work when you consider you have to style margins and padding now that you've gone and reset everything.
Flash. Useful for ads, games and video. Not a complete website.
Every client is different and their requirements change for each job. You need to be flexible and experimental, and try new things. A few last general tips:
Keep it simple. Have a look at examples of other work when you are trying to achieve an effect or technique. Most often the solution using the least amount of code is the most efficient, easiest to learn, and a good starting point for you to begin altering and customising.
Be consistent. Try to approach every new piece of work building on techniques you've found work best. Each time you do, alter a little bit and see how well it works with the code you've found to be stable.
Ask for feedback from friends. Ask friends and colleagues with different browsers and operating systems to try out your work and report any bugs.
"Each new hour holds new chances for new beginnings, the horizon leans forward, offering you space to place new steps of change"
Horizons - LTJ Bukem