At the beginning of the month, Redgate sponsored Talk UX. Revathi and I went to Manchester to attend it, and we’ve been talking about it to whomever wanted to hear. These are some of the questions we have been asked, here is what you’d have heard us say if you were there too… How was […]
Being a natural pessimist I wrote recently about the terrible state of University websites aiming to attract students interested in HCI and design. With many of the academic websites there appears to be a consistent contradiction in that these institutions are purporting to be ‘centres for excellence’ on one hand while displaying anything but excellence on the other. Examining many of the examples out there I felt that these examples were a worrying indication that many of these courses and their approaches teach one thing but practice the opposite. The end user experience leaving students rather underwhelmed and providing little experience to make the student sit up and take notice.
In the ever wonderful Smashing Magazine, a magazine which often has a much more optimistic view on matters of design, they have just written about the many positive examples of University and higher education websites. There are some truly excellent examples in there and for the moment at least have reduced my pessimism a little about the state of academic websites. These examples of web design and careful construction of the information architecture lead to an end user experiences that are beacons of light in a rather dark room.
In these examples it shows that in some cases the guards are being carefully looked after with the result being an environment worthy of teaching and inspiring those who visit.
The team I work with release every Wednesday.
Why? Well, we believe in releasing frequently to give our users valuable enhancements as quickly as possible and to get timely feedback on the direction we are taking the product. We’ve believe in keeping the delta between releases small and the risk associated with an individual release low. We think practice makes perfect and that the more often you release the less frightening it is to do so.
Moreover, we want to be deliberate about releasing frequently, rather than opportunist. An opportunist frequent release process is one where you are able to deploy a given code change reliably and with little overhead, but that you choose to do this when the opportunity arises. That could be when you’ve just fixed a bug, when a feature has been completed or perhaps when ‘all the planets align’ and all your automated tests have finally passed.