Skip to main content

Preparing for New Ratings System

In January we will start in earnest on rewriting the "Student Ratings" system. The system is to allow students to rate their professors and the courses they are taking. (I am hoping we can change the name of the system to better reflect what it does. We aren't rating the students, after all. That is what grades are for.)

Gene and I had a good conversation with Nate W. and Tom M. today about the general design principles of the system. This is a project where we are going to try out our model of having separate teams work on the UI and the web services and treat them as parallel projects. Our hope is that we can get better and more reliable web services if they are ONLY way to talk to a system rather than just the tack-on way that the main programmers don't use because direct-to-database is faster.

Comments

Popular posts from this blog

Making People Feel Stupid: A Cardinal Sin in Design

People will go to great lengths and inconvenience to avoid appearing or feeling stupid. A great example of when design makes a user feel stupid comes from Alan Coopers 1999 book The Inmates are Running the Asylum on page 24. Cooper is talking about the keyless entry system on his car keys.
"The large button locks the car and simultaneously arms the alarm. Pressing the button a second time disarms the alarm and unlocks the car. There is also a second smaller button labeled 'Panic.' When you press it, the car emits a quiet warble for a few seconds. If you hold it down longer, the quiet warble is replaced by the full 100-decibel blasting of the car alarm, whooping, tweeting, yowling, and declaring to everyone within a half-mile that some dolt--me--has just done something execrably stupid. What's worse, after the alarm has been triggered, the little plastic device becomes functionally inert, and further pressing of either button does nothing. The only way to stop that hon…

Strategy: Efficient or Innovative

We haven't had a refresh on our strategy direction in my office for a few years. It seems like we are frequently torn between being efficient and being innovative.

Efficient

Lower costspeed to productionminimal failuresmaximum uptime Innovative Higher costlots of failuresfreedom to pursue non-"approved" activitiesshorter attention span I'm part of an IT shop with nearly 200 services that we offer to campus and internally. I love the feeling of being innovative, but I'm concerned that our current push is to be innovative at the expense of being efficient. The result is that we can't accomplish as much near-term good for the campus because our focus is on the longer term.