Knowing What You Know

With time, and a little luck, almost anyone can do something once. The only way to know whether you actually understand how to do it, though, is to see whether it takes you less time to do it a second time.

For example, as of 10:30 this morning, I finally have some JUnit unit tests of Hibernate running inside Eclipse on my Windows laptop. There are still a few loose ends---I haven't figured out how to add "." to the classpath for Eclipse's built-in JUnit runner, for example, so I'm using a launch configuration instead, which means that I don't get a green bar to show me when everything's working---but I can create and populate a database, fetch and update rows, and so on.

Problem is, I still can't make it work on the CDF Linux machines. I know what the problem is---again, getting "." on the classpath---but the magic spell that works for me on Windows has no effect on Linux. I therefore don't believe that I really understand yet how all the pieces fit together.

My only consolation is that a lot of other bright people (my co-instructor, the students) are having just as much grief. The fundamental problem is that what I have to specify things that I of as single pieces of information several times in order to make Eclipse happy. For example, I have to add "." to my classpath once to compile, again for each of my run configurations, and once again for Ant. This is probably a consequence of Eclipse's modular architecture, but I don't care---it's still bad.

So, while I feel I'm making progress, I won't really know until the next time I toss Eclipse onto the table in front of a dozen students. That will be when I find out how much I've actually learned.