rtow
02-16-2005, 05:05 PM
As a web developer, I find it funny how we spend an amazing amount of time getting stuff to work without evaluating why it should work. It's the eternal preserve of the programmer. I mean, how many of us start straight into developing a page or a function without stopping ourselves and carrying out a detailed design about why we are designing, for who and the constraints that the development environment places on us?
I've just started my Master's thesis in website pedagogy & e-learning and as part of it, I have develop a site that has a defined purpose, teaching 1st yr ICT college students how empirical sets of data can be manipulated into meaningful views (such as graphs and real-time gauge widgets).
How many times have you found yourself on a web-site that you would love to bin. Simple things like stopping the back button from reloading a previous page, flashing graphics (a pet hate of mine) and having to trawl more than 3 clicks to the information you want. Microsoft, believe or not, pioneered the principle of 'If I can't the information I want in 3 clicks or less then the design goes back to the drawing board.'
I'm not suggesting that ppl go overboard, but as a web developer you know that knowing you audience and target them with some sound design insights and useful content is king. With the explosion in the amt of websites, browsers have become increasingly picky and you really only have 10 seconds (at most) to impress them.
I think HM does a great job on encouraging peeps top swap tech tips and programming tutorials, but a discussion on design principles is just as important.
I'd like to recommend to anyone who wants to brush up usability their site. It's called 'Homepage Usability: 50 Websites Deconstructed' by
Jakob Nielsen & Marie Tahir. Basically, it tears apart 50 of the most used popular web-sites, in terms of design and purpose, pointing out design flaws and inconsistencies.
rtow
I've just started my Master's thesis in website pedagogy & e-learning and as part of it, I have develop a site that has a defined purpose, teaching 1st yr ICT college students how empirical sets of data can be manipulated into meaningful views (such as graphs and real-time gauge widgets).
How many times have you found yourself on a web-site that you would love to bin. Simple things like stopping the back button from reloading a previous page, flashing graphics (a pet hate of mine) and having to trawl more than 3 clicks to the information you want. Microsoft, believe or not, pioneered the principle of 'If I can't the information I want in 3 clicks or less then the design goes back to the drawing board.'
I'm not suggesting that ppl go overboard, but as a web developer you know that knowing you audience and target them with some sound design insights and useful content is king. With the explosion in the amt of websites, browsers have become increasingly picky and you really only have 10 seconds (at most) to impress them.
I think HM does a great job on encouraging peeps top swap tech tips and programming tutorials, but a discussion on design principles is just as important.
I'd like to recommend to anyone who wants to brush up usability their site. It's called 'Homepage Usability: 50 Websites Deconstructed' by
Jakob Nielsen & Marie Tahir. Basically, it tears apart 50 of the most used popular web-sites, in terms of design and purpose, pointing out design flaws and inconsistencies.
rtow