Overall I learned that the Win32 API (Application Programming Interface) was annoying and ugly. Some functions take useless
parameters. Even the hailed DirectX API turned out bulky. I suppose that is just my opinion, as I happen to be 100% self taught
and I am used to rather small and spiffy code. Some "professional education" may help, but I don't like being trained to think.

I also learned that creating a game engine is much harder then it seemed. Especially without the vector's of C++'s STL (Standard
Template Library). I had to use doubly linked lists for just about everything, as I didn't want to toil with hash tables or binary
search tree's. Sadly, this probably reduces performance, but it is extremely accurate. It also allowed for easy manipulation of
the sprite's Z-Order.

The major thing I learned was how to interface a C program with the Win32 API. This will help down the road, especially when I
write actual applications (not games). I now know how to use resources, load/manipulate bitmaps, modularize code on a decent
size project, write a scripting system (albeit a bad one), how a window's coordinate plane works (its different from "standard" ones),
the inter workings of the WinMain() function and window's messages.

On a scale of 1 to 10, I would say 9. I didn't have enough time to do - Everything - that I wanted to do, but I did get a lot done.
At first I made progress by leaps and bounds, each week having something new and great. Later it ground to a halt as I had to slowly
and painfully find errors and bugs. This process, while necessary, is quite annoying. Also, the Win32 API really just made things
worse with its ugly functions and its weird parameters. Anyways, I've learned a lot, and for my first graphical project I didn't think
it was too bad.