Joel Spolsky, a prominent blogger and CEO of a small software company, wrote an article on a 12 steps for better software development. The article is from the year 2000, but still relevant today.
The Joel Test: 12 Steps to Better Code
While a University's main purpose isn't exactly software development, computer scientist researchers do frequently have to do programming. Here's how my research group rates based on Joel's criteria:
# Do you use source control?
- Yes (well, half the time, at least for the main project)
# Can you make a build in one step?
- No
# Do you make daily builds?
- No
# Do you have a bug database?
- Yes (finally)
# Do you fix bugs before writing new code?
- No
# Do you have an up-to-date schedule?
- What's a schedule?
# Do you have a spec?
- What's a spec?
# Do programmers have quiet working conditions?
- Hell no.
# Do you use the best tools money can buy?
- No way (our PCs don't even have CD-burners)
# Do you have testers?
- The users are the testers, aren't they?
# Do new candidates write code during their interview?
- No
# Do you do hallway usability testing?
- Kind of
So: 2.5 / 12.
Not the greatest of scores. Now, I could try to revolutionize the University: transform the stale, old practices into a new high-tech, high-productivity environment that students and researchers love to work in. March into the dean's office demanding that he break down the establishment, write essays, post flyers, complain to everyone in the department ...
Or I could just tolerate and leave the country as soon as possible ...