Quote:
Originally Posted by BrianBSL
it was not a well put together system, and it was obvious that there was much more focus on how "good" the system "looked" rather than how well it functioned. (It also had a quite good looking graphic for the controls)
|
I agree 100%. It is very easy to hide horrible functionality behind something that looks very good. Looking good does not imply anything about the underlying functionality. To go along with that, looking good also implies nothing about the usability of the system.
To those of you that are pursuing a career in software, remember this fiasco ... it teaches an important lesson. When designing a software system, make sure that the functionality is complete and working, then add the touches that will make it look nice. If you design it right, you can decouple the functionality from the front end interface.
Like Brian, I will go into this year and let them prove that their system works, but I am going to keep my expectations high for week 1 as I have previously posted.