Yes, I think too hard. Call it force-of-habit -- six years of habit. All that computer science training made me into a coder who thinks too hard. Don't worry, I'll explain.

I've been charged with enhancing a particular function of our software product. After three days of fiddling around with a state diagram, then 2 days of fiddling around with a thread timing diagram, I finally stumbled upon an elegant solution. However, in the design two threads are joined at the elbow, which doesn't allow for proper modularization and reusability of the code. So I have to find a way to decouple the threads, which I might be able to do now.

The solution probably should have been much simpler, and probably should have been done by now. But leave it to my guru status to try to design this code properly.

<sigh/>


UPDATE: 6 Sept 2005, 16:29: And after all that, the stupid API calls don't even work right. So for all those state diagrams and thread timing diagrams, I have pretty pictures.

¶ 2:13 PM