Earlier this week, I began looking at the code from Cyclone and the Unit Tests/Demo samples. The code is complex in arrangement, everything intertwines in a rather convoluted matter at times when you go deep. I find my biggest challenge so far to be remembering not to get caught up in the subject of the material, but rather focusing on the mechanics of it instead. I have to keep reminding myself not to get too involved in translating the Physics and Math of it, and to look at the structure and logic of the language use itself. I have to parse out those esoteric little details from that jungle of collision code. After all, we are like editors working on checking for grammar and spelling mistakes, rather than the specifics of Bengal tigers in the wild.
So far, half of my group has been active; the active half being Brian and I. Although the other members posted their contact info and made comments on their initial progress, I have not heard from them since-- this is three emails later. I hope that these guys will jump on the bandwagon soon, but if not, it's not like it's the first time I've dealt with this. Honestly, I'm not too concerned because after working in groups for so long, I have seen a full gamut of situations, from the best of the best to the best of the crazy. Tomorrow, I'll begin working on the actual tests and code the simple ones at least. Hopefully, I'll get caught up though and keep moving on through the rest.
P.S. - Something that I used a lot when looking through my allotted files was the "find all references" functionality of VS. That way, I could easily trace where my functions of interest were being called and used, giving me a better lay of the code-land.
No comments:
Post a Comment