Several years ago, I found a document called Challenges for Theoretical Computer Science. It describes a bunch of 'challenges' that haven't been solved in the computer science area. The information written in this list is 5+ years old now, and it's amazing how many items on the list are still outstanding. I don't claim to be able to understand all of the challenges (like 'Make Quantum Computing a Reality'), but there are a lot of them that apply directly to TDD methodoligies (like 'Software Specification'). It would be interesting to track this list (or one like it) over many years.
I think it's useful to take a step back every once in a while and see where we've come, and where we're headed. A couple of useful things can come out of it:
- Correction/Validataion of your current course.
- Realization that most problems have been around longer than our recognition of them, and that some smart people may have spent time thinking about them.
- Insight into a problem outside of your current vicinity can give a great new angle on your immediate problem.
- New product ideas. You may have the insight to solve some problem that nobody else has.
No comments:
Post a Comment